Turning on Routing and Remote Access kills my network
Posted on 2004-10-04
I am attempting to get my win 2k server to act as a VPN server by turning on Routing and Remote Access. I beleive that I have followed all the instructions in a number of books but I still get the same result. Whenever I turn on the service, the rest of the network drops off.
What the network looks like:
My network has a firewall (ip-cop) that acts as the DHCP server and gateway, win 2k server is doing DNS and I am trying initially to VPN connect internally (LAN) so the firewall isn't my problem. What I seem to have is a DNS issue because as soon as I switch on Routing and Remote Access, I can't reach my server through Terminal services and I lose my network drive mappings etc....
The Win2k Server doesn't need to do any other routing tasks and it seems that it tries to become one whenever Routing and Remote Access is on.
Any help is greatly appreciated.