Windows 2000 Server - IP Routing Question

  • Thread starter Thread starter Chris Smowton
  • Start date Start date
C

Chris Smowton

I apologise in advance for my ignorance.

Is there a way to manually configure Win2000's routing behaviour?

Specifically, I find that when my server is connected to a VPN (over
TCP/IP, not directly dialled in), the Internet Connection Sharing
clients, as well as the host system, can no longer access the internet
proper, as all queries are routed through the VPN connection. Is there
a way to dictate that only packets destined for 137.12.x.x should be
sent via the VPN, and everything else should go through my ISP's
default gateway? (obviously this happens for VPN packets too, but
thanks to their being encapsulated it appears from an application
level to have jumped straight from 192.168.0.1 (local) to 137.21.2.12
(the VPN server).)
 
Hi Chris,

It is not recommended to run ICS on a server. How many nics do you have in
the server? How are you connecting to the internet?

Marina
 
I had the same problem but with a windows 2000 station. As soon has i
started my vpn connection i no longer could use the internet.
The solution for me was to remove the flag Use default gateway on remote
network.
You can find this on the properties of your vpn connection
Righ click vpn connection
select properties
select networking
select properties of internet protocol(TCP/IP)
press advanced button
remove the flag

RikkieV
 
Marina Roos said:
Hi Chris,

It is not recommended to run ICS on a server. How many nics do you have in
the server? How are you connecting to the internet?

Marina
One NIC, and one ISDN TA. Three clients (win98 machines) use the 2000
server as an internet gateway.
 
Hi,

On the server, go to the VPN connection properties and uncheck the box that
says "Use default gateway on remote network".


--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Don't run ICS on a server if you can avoid it. And re RRAS, why turn your
server into a router? Get a cheap and cheerful hardware firewall/router
appliance and use it as the default gateway - and if your server needs to
connect to another network via VPN, consider putting in a VPN site to site
connection between routers/firewalls. Much less overhead on the server, much
tidier. :-)
 
Back
Top