NT'ers:
We had a system failure on an NT 4.0 workstation and we had to replace the system. We used a disk image program to copy the original disk to a new disk assuming all but the drivers would be the same.
The system has an on-board LAN adapter and a PCI LAN adapter, each plugged into a switch but each on a different subnet talking to two different networks.
One each adapter's properties we defined the appropriate gateway and we can ping various points on each network. We can make connections to devices on each network and devices on those networks can connect to the NT system OK. We can even map a drive to a system on one of the subnets.
However, when we use IE to access the Internet through the gateway of one of the subnets it won't go -- it just times out. There is no "unreachable" message, just a timeout.
I noticed that the DNS seems to be defined in a central TCP/IP area not specific to either adapter.
When I display the routes with route print or netstat -rn it appears that the route 0.0.0.0 0.0.0.0 has a default gateway of 192.168.0.1 which is the correct gateway for the Internet.
Based on this explanation can anyone think of what else I could check to make this work as before? Thanks in advance.
Bob
We had a system failure on an NT 4.0 workstation and we had to replace the system. We used a disk image program to copy the original disk to a new disk assuming all but the drivers would be the same.
The system has an on-board LAN adapter and a PCI LAN adapter, each plugged into a switch but each on a different subnet talking to two different networks.
One each adapter's properties we defined the appropriate gateway and we can ping various points on each network. We can make connections to devices on each network and devices on those networks can connect to the NT system OK. We can even map a drive to a system on one of the subnets.
However, when we use IE to access the Internet through the gateway of one of the subnets it won't go -- it just times out. There is no "unreachable" message, just a timeout.
I noticed that the DNS seems to be defined in a central TCP/IP area not specific to either adapter.
When I display the routes with route print or netstat -rn it appears that the route 0.0.0.0 0.0.0.0 has a default gateway of 192.168.0.1 which is the correct gateway for the Internet.
Based on this explanation can anyone think of what else I could check to make this work as before? Thanks in advance.
Bob