Windows Forum

Ask something
Discussion Locked

Dial-Up ISP use kills gateway router use

0 helpful
6 replies

by brepp

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a W2K Pro workstation connected to a local net via static tcp in city A. This wks gets to our City B servers via a router and it's ip address entered into our default gateway. This works fine and I can ping away between City A and B. Thissame wks has a modem dial-up connection to a local isp. Once the dial-up connection is used, we lose our connection to the City B servers via the router. We can use isp dial-up connection again but not the gateway access to the router. We cannot ping City B anymore but we can ping and connect to wks and server that our in City A. If we reboot, all is ok again unless we use dial-up access. It's like the use of the dial-up access makes the wks forget about it's gateway to the router. This only happens on the W2K station. Win/98 is ok.

6 replies

by jaystar

This is strange that it works in windows 98, but here is thge problem...
Your gateway address is really just a routing rule added to your workstation. The route 0.0.0.0 will point to an address (your router) on your local network. When you connect to the internet, you get another default gateway address, so another 0.0.0.0 route goes in, you should be able to see both via the route print command.
The solution is to add a static route to your client via the route command. since you are using windows 2000 you can make it a persistent route and it will always stay with the client. Here is the command to do that from a command line:
route add MASK -p

The -p makes it persisent.

for example if city A has subnet of 192.168.1.0/24 and city B has a subnet of 192.168.2.0/24 and the routers are on .1 you would use this command:
route add 192.168.1.0 mask 255.255.255.0 192.168.2.1 -p

Hope this helps

Jay Starling

by jaystar

In the above example I mistakenly put your workstation in city B. Since you are saying your workstation was in city A the correct command line should have been this:

route add 192.168.2.0 mask 255.255.255.0 192.168.1.1 -p

Sorry for any confusion...

Jay Starling

This discussion is closed to new replies.