Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multihomed, with connection sharing on win2k

Status
Not open for further replies.

nottuk

Technical User
Mar 6, 2003
2
GB
Hi,
I have a cable modem attatched via usb with internet connection sharing enabled, a five port switch connected to a NIC. All the ports on the hub are used so to add another computer I bought a cheap NIC.

After putting the NIC into the computer and connecting it to another PC with crossover cable, there is no recognition by either computer, there is a connection present but I can't seem to find either computer from one another.

Please can you offer any advice... Do I need to assign IP's or something?

Kind Regards

Gabriel
 
Gabriel,

By default, windows try to get IP from a DHCP server when you install a new network card. If he cann´t locate a dhcp server, he takes an auto IP (169.x.y.z). This IP´s dynamic.

In your case, both PCs stay with default config.

Try to enable ICS again, when you do this, Windows changes the config of your other NIC putting an ip (192.168.0.y), and the PC will be now a DHCP server.

good luck
 
I have, the DHCP now with IP 192.168.0.1
The thing is that while the NIC connected to the hub works fine, the other NIC senses there is a connection i.e. system tray monitor, shows there is a cable connected in network connections, but just cant find either computer from one another i.e. run \\CPU1 gives "cannot find CPU1". Is this anything to do with the workgroup set up or IP settings.

I have tried setting a different IP for the second NIC with a default gateway on the second machine but there is no joy...

Thanks
 
Gabriel,

Try this:

1.Set the second NIC to auto IP, without gateway and reboot;
2.After reboot, click Start / Run / and type CMD;
3.At DOS window, type IPCONFIG;
4.Look Ethernet Address, if he´s 169.x.y.z abort this proccess. If he´s 192.168.0.2 or like this, continue.
5.Still in DOS, type 'PING 192.168.0.1', look the response: if is "reply from..." that´s OK! if is 'time out'.. ouch! we have a problem.

If Ping is OK, try to access shares via \\192.168.0.1, and you can test navigate Web.

If Ping is TimedOut, cross cable can be bad!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top