Networking problem with Netgear products

Rhombuss

Golden Member
Nov 22, 2000
1,544
0
0
Here's a rundown of the situation, using a Netgear DS108 10/100 8 port hub, with a Netgear FA310TX in each of my 2 computers. I'm running Win2K and just let the OS determine the driver set, using the Microsoft certified FA310TX drivers, since I couldn't find any Win2K drivers for this card on Netgear's site.

I have the Microsoft Networks Client setup with file/printer sharing and the TCP/IP protocol installed. I did not install IPX/SPX or NetBIOS. Both computers on the same default WORKGROUP.

I set one comp to IP 192.168.0.1, with subnet mask at the default 255.255.255.0 - no DNS or WINs entries, and I set the WINs option to 'Disabled NetBIOS over IPX'. On the second comp, I set IP to 192.168.0.2 with same subnet mask, and make the default gateway 192.168.0.1, which is the IP of the first comp. Now here I have tried 2 things, the first being no DNS/WINS entries for the second comp, and the second being using the IP of 192.168.0.1 for both DNS/WINS entries.

Once both comps are on, I them ping themselves first - so on the first comp I would go to command prompt and 'ping 192.168.0.1', and I get 100% response with 32 bytes, no loss. Same for second comp, it can ping itself. So I assume if the network adapters are able to ping themselves, then they are operating normally correct? But when I try to make them ping each other, I get timeouts.

I can't understand why this is happening - and I know it's not my hub, as it worked just 2 days ago when I had 2 DLink cards installed.

I also tried using just one of the Netgear adapters before I installed both - and it worked perfectly. The setup then was the Netgear hub, the FA310TX Netgear adapter, and a DLink 530TX adapter. Everything worked fine. But once I installed the other FA310TX adapter in the previously DLink comp, the network stopped working. I doubt it is a hardware problem - most likely some software gimmick.

Any advice on this would be very much appreciated.
Thanks!
-Phillip
 

reicherb

Platinum Member
Nov 22, 2000
2,122
0
0
I'd try reinstalling that second Netgear card. Obviosly the first one is ok if you could access the network with it. Also try removing all the protocals when you remove the card and then reinstall them.
 

mgpaulus

Golden Member
Dec 19, 2000
1,112
0
0
Does Netgear have any configuration/testing utilites available? 3COM has a small dos-based test routine for each of their cards, which comes on the install/setup floppy. It's nice, because you can usually boot up the floppy, configure the card, and then run this "echo test back" set of tests to check that
everything is working, which can quickly tell you whether the problem is hardware or software based.
The 3COM suite requires 2 machines. One you boot up into echo back server mode, and then all other machines can boot up into test mode, and they just bounce packets to each other. But it works independant of any software or other system drivers that might interfere.

Anyway, I was just wondering if you have truly eliminated hardware problems. Have you tried switching hub ports? Maybe the DLink cards can recognize a "uplink" port input, and switch signals, but the Netgear cards can't? (I think some HP cards can make that assessment).
 

Rhombuss

Golden Member
Nov 22, 2000
1,544
0
0
Yeah, I've switched the ports around - but I've never had them hooked up to the uplink port. Not sure if Netgear has some diagnostic program - I'll look into that.