Hi, again :)
Following on from the issue I had with the DHCP server [http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/78c207a4-f16c-462d-8c73-35e357d9eaaf/] I am now having issues with Routing and Remote Access on the same Windows Server 2008 R2 domain controller. This is occurring at an office I am helping to set up with remote access.
The problem:
When I look at Network Policy Access Server > Routing and Remote Access > IPv4 > General, under the list of interfaces the internal interface's IP address is reported as 'Not available'.
Under Roles > NPAS, if I right-click RRA and choose Properties the IPv4 tab has 'Enable IP4 forwarding' checked and the option to obtain addresses via DHCP is also checked.
Ports comprise SSTP, PPTP, and IKEv2 entries.
DHCP is working fine and is distributing addresses to LAN clients.
I have tried removing the Network and Policy Access Server role but when I add the role again I am not given the opportunity to configure it, and the original settings are restored, and the internal interface's IP is again listed as not available.
I assume that the Internal interface is not picking up its IP address from the DHCP scope.
I have *exactly* the same configuration at the office that I work in where the same roles are installed on a Windows 2008 Server that is also a domain controller. The internal interface under IPv4 on this server has a DHCP assigned address and remote access works fine. I have compared both servers' settings side-by-side and there is no difference between them.
Can someone offer any advice on how I should fix this, please? Is it possible to wipe the RRAS configuration and force the wizard to start so that I can set it up from scratch in case the previous issue I had with DHCP is still affecting it? Or, is there some setting that I am missing.
Thanks!
[edit]
I have just discovered that disabling/enabling will wipe the configuration and allow me to reconfigure the service from scratch (thank you Trainsignal!).
I'm sorry, but WTF?
Disabling usually stops/pauses a service/application and enabling usually allows it to resume.
Uninstalling, for the most part, wipes the application and its settings so that when you reinstall you can start again and fix any misconfiguration errors that could not be fixed before.
Why has Microsoft turned this on its head??
You guys do sterling work and your products are excellent, but this is the first time that I have been 100% flummoxed by a product.
Grrrr! I have wasted so much time with this.
[edit 2 Jan 18]
@max
Open RRA. Right-click the server name and choose Properties. Click the IPv4 tab. Choose to assign a static IP address range that uses addresses in the same subnet as that used by your office. The remote clients will pick up an address that puts them on the same subnet and they will then have access to the resources.
The forum won't let me post replies to my thread(!) so I hope you see this