Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a computer with two nics and one nic connects to hub sharing internet connection on home network. The other nic connects to another computer. I have been trying to troubleshoot the connection on the crossover cable. The one machine without the 2 nics can boot into win2000 and RH Linux 7.2. My real Question is when testing my machine with 2 nics I try pinging itself by loopback, but want to specify which card the ping should come from. Because a simple ping works, but I am pretty positive its coming from the card connected to the internet, not the card connected to the other computer. Thus I need to specify card 1 or card 2, when testing localhost loopback?
Thanks

Instead of pinging the localhost, try pinging the actual IP of the NIC. Localhost is more of a stack check, IP is the NIC to the tranceivers. I've seen localhost work when the IP ping failed (bad IRQ setting for the ISA NIC).

This is my setup right now I have that computer with 2 NICs running WIN2000(Computer1). 1st nic connected to internet, 2nd connected to another computer by CrossOver cable currently booted into WIN2000(Computer2). They both can access each other by means of Microsoft Networking so I can share files and stuff works fine. The IP of Computer1 2nd NIC is set to 192.168.0.1, Computer2 is set to 192.168.0.2 both on same subnet mask! But they cannot ping each other. Or themselves for that matter. Computer1 has internet connection sharing enabled (that by default is what set the 2nd nics ip address), I manually changed Computer2 ip. My goal is to share that internet connection for when Computer2 boots into WIN2000 or RH linux 7.2, so far both aren't working.
THANK YOU ALL!

Generally speaking, when you ping a NIC by it's IP address and you get no reply it means a problem with the NIC. If you have another working NIC to test with, replace the one that's in there now with a working NIC and see if that doesn't cure the problem.

TO: Curt R
Yes but remember that I can Access through microsoft networking, which means all my NICs are working. Positive of that!

If you changed the 2nd PC's IP manually, does that mean you changed from dynamic addressing to static? I though I read where ICS didn't liked that and needed to DHCP the systems accessing the internet. That's part of why I use something like AnalogX's Proxy (its free). I perfer to call the shots (IPs and some ports) on my network.
I've also seen where having a dedicated default gateway on that 2nd NIC can cause that ping problem. Don't think that's the case here though.
If you have a firewall, that too could be a cause. I had to configure ZoneAlarm to allow for my internal network. Can't receive ping responses back from the internet or renew my internet DHCP address though.

Michael Thank You, Thank You, Thank You!!!
After no success using Windows ICS I took your advice and it worked practically perfect. Had to read the ReadMe File accompanied by AnalogX and reconfig everything and through some trial and error...
SUCCESS!

Your welcome.
Just point the Linux browser to the IP and port used by AnalogX's proxy. Should work no problem.
BTW, you can change the ports via this key:
HK_CU\software\analogx\proxy\

I was searching around came across this thread. I have a similar problem to the first issue you were discussing on the two nic ping.
I am able to ping the internet NIC IP address when the interface cable is connected successfully, but unable to when the cable is disconnected.
I have limited experience, is it a basic requirement that the interface cable be installed to be able to ping the NIC's IP address.
Thanks

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |