asked on

Routing and Remote Access assign IP address to server

I have found that Routing and remote access is assigning a 2nd IP address to the server. This is causing issues internally in that the workstations are seeing the new IP address.

The Reason for RRAS to be installed is for VPN which is working fine.

John Easton

Normally the second IP Address is only visible to the VPN client. However, as you using ISA / TMG as your firewall. If so there is a issue with this product where internal clients try to use this second IP Address for web access.

Have a look at the following article on technet forums: http://social.technet.microsoft.com/Forums/forefront/en-US/2c4e342f-0ab7-4cd7-b007-0f2b0c559704/tmg-vpn-connection-causes-wpaddat-file-to-have-wrong-ip-address-for-proxy-server?forum=ForefrontedgeIA

Cyber_Junkie

ASKER

I did a search for wpad.dat and it was not found.

I am using Windows server 2008 R2 with the normal Windows Firewall, not TMG.

Everything else in the article pertains to this issue, restarting RRAS resolves the issue until a VPN is established.

ASKER CERTIFIED SOLUTION

John Easton

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Rob Williams

The common issue is in the DNS management console. Right click on the server name and choose properties. Under the Interfaces tab uncheck the VPN adapter IP. If you are using the windows VPN it has to assign the server an IP, but it should not be tagged in the DNS console.

You may need to flush DNS on the server and workstations if still having problems, either by rebooting or running ipconfig /flushdns

Cyber_Junkie

ASKER

Currently testing