Gateway Problem

[chepex]

Gateway Problem
Here's the scenerio, We have a computer running win2k, and is running a program that needs SQL in order to access data, this program is called AG/Star32. The computers ip address is 192.168.0.2. We have a server that is running Win2k Server and Active directory and the SQL Database.
We have recently installed a router to provide our dsl access to the entire network. The dsl routers address is 192.168.0.100. The DNS address for the router is 206.13.30.12 and 206.13.29.12.

Before we installed the router the icon on Ag/Star32 was working extremely fast, you just double click and your there. When we installed the router you double click on it and it takes about 1-2 minutes to start. We figured out that if you take the gateway address out of the network config on the workstation that icon gets really fast again. but there is no internet becuase there is no gateway. So either we have a fast icon and no internet. Or if we put the gateway back on we have a extremely slow icon and internet. NOW this is only on this computer the rest of the other computers are working great. With the gateway!! and all the same configurations. It's only this computer that has this problem. We know it's a gateway problem with this computer can anyone help us on how to fix this problem without redoing the whole entire system, but if thats what we have to do then thats what we have to do. Anyone any suggestions.

 

[RichardCorbett]

Is the Win2K PC and the server on the same subnet? If not then I would guess that the router (gateway) doesn't know how to send the data packets to the server. However, because it works OK from other computers then you could try adding a static route to the PC and making it permanent.

At a command (CMD) prompt:

ROUTE ADD 192.168.1.100 MASK 255.255.255.255 192.168.0.2 [CR]

You will need to swap the '192.168.1.100' to the address of your server. This should prevent the PC from attempting to use the gateway address to make the connection. (Removing the GW from the NIC settings would make the PC always route through it's own IP address.)

If your PC and server are on the same subnet (both 192.168.0.x) then I'd suggest doing a TRACERT from both machines to determine how the data packets will travel between them. If working correctly they should give the same responses but in reverese, and never hit your router.

Hope this helps.

 

[RichardCorbett]

Sorry, forgot to add:

-P

to the command line, after the '0.2' but before the carriage return.

(The route should work as is, but the -P makes it permanent and will survive a reboot.)

If you subsequently wish to delete the route use the command:

ROUTE DELETE 192.168.1.100 [CR]

Again you'll need to substitute your own server IP.