Discussion Locked

Network / Internet Problem

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a Windows 2000 Server with 5 windows 98 workstations. Were networking with TCP/IP and the workstations are assigned IP from the server. We installed a best data cable modem and added a second NIC to one of the workstations. The NIC that is attached to the cable modem obtains an IP from the cable company (which is actually static) and we assigned the IP of 192.168.0.1 to the NIC the we use for the network. (The server?s IP is 192.168.0.10) We set up ICS and all was well. Then we started upgrading the machines to Windows 2000 Pro. (Clean install not an upgrade). When we tried to install the machine with both NIC?s and the cable modem we had a problem. We can?t get the machine to see the server (Domain name CORPORATE) but the Internetworks fine. If we disconnect the cable modem we can connect to the server but we can?t get the Internet. If we reboot with bot connected, we loose connectivity to the server but we have the Internet. Can someone tell me what?s wrong and how we can make both work at the same time.

Thanks
Bob Wiggins

5 replies

by 4u21der

Have you made sure that the IP address that you are assigning to the multihomed workstation are outside of your DHCP scope?

Try to assign the cable modem IP as static on the external nic.

It sounds like the 2 DHCP servers are confusing the routing on the interfaces. I would assign both address as static. And then verify that the routing tables are correct. ( c:\netstat -r );(route print)

Check the default gateway for the workstation. It should only have the cable modems IP as a gateway.

I am a bit confused as to why the cable modem is installed on a workstation and not shared through the server?

I hope this is helpful.

Good Luck!

by stillatit

As I understand your setup, you have this:

modem--enet--BoxWithICS--enet--RestOfNetwork

and the BoxWithICS has two NIC cards, with one connected to each ethernet.

If you have the same address range on both ethernet segments, you are going to confuse that poor machine something fierce. Change the IP range on one side or the other to 192.168.1.xxx and the problem should go away.

A better choice, by the way, would be to replace the computer with ICS with a low-cost router which includes NAT and DHCP. Linksys, Dlink, and others make these, and they are typically under $200. The Dlink model will even spoof the cable modem so that it thinks it is talking to the computer it was originally installed on.

Good luck.

This discussion is closed to new replies.