Really need help with Networking in Win2K...help appreciated!

[Rhombuss]

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

 

[Nevo]

It does sound like a bad hub or bad cabling.

You don't have either computer plugged into the hub's uplink port, do you?

Try putting a crossover cable between the two computers and eliminating the hub.

BTW, your software settings do appears to be correct to me.

 

[Rhombuss]

I'm pretty sure the hub is sound - as I have been using it for quite a few months. And I've hooked up the cables to port 1 and 2, not port 8 which is the uplink. I'll try to get a hold of a cross-link cable (or attempt to wire one myself hehe) but I think the problem is software, not hardware.

 

[bozo1]

.

 

[Rainsford]

Take a look at your hub when you are pinging. There are two places that could be problems. First of all, the pinging computer could not be sending information out for some reason. In this case, the light for that computer would just stay lit and not blink. Or, maybe the second computer isn't replying. If that's the case, the first computer's light on the hub will blink and the second computers light will not blink. Let me know what the lights do when you're pinging, try this for both computers. Oh, and if your hub isn't by the computers and you want to make them ping continuously, just type 'ping "IP Address" -t' and 'ctrl C' to stop the ping. This will help determine where the problem lies. My guess is that none of the lights will blink, because I've had a similar problem. Sometimes the computers don't know that the other computer is on the network, so they don't even try to ping them. Well, anyways, let me know what you find.

 

[Rhombuss]

Just did what you suggested Rainsford, the light for the pinging computer on the hub is blinking, but the light for the computer that I'm trying to ping is not. Tried it both ways, same result just flipped. So I'm positive the nics are able to send out, they're just not receiving, and I dunno how to fix that, argh!

 

[Rainsford]

Hmm, guess it wasn't the problem I thought it was. Ok, let's take it from the top. First of all, are you using Internet Connection Sharing? If not, turn off all of the gateway stuff, you don't need it. Also, if you don't have ICS, neither computer is a DNS or WINS server, so don't make either on a server in either computers configuration. Maybe this will help.

My also question is, are you sure that the Netgear card you put in the former D-Link computer works? You said that computer #1 with a Netgear worked with computer #2 and a D-Link, but did you ever try the second Netgear card, maybe it doesn't work. I'd test it by running the second Netgear in computer #1 and the D-Link that you know works in computer #2 (if you still have it). Also, did you remember to uninstall the D-Link card from the second computer before installing the Netgear? I've had lots of problems with D-Link cards causing problems after they have been removed. D-Link stuff is kinda crappy IMHO. Maybe one of these will work.

 

[Rhombuss]

Funny thing too...after I installed the 2nd Netgear and found out it didn't work, I plugged the DLink back in (after uninstalling the Netgear of course), and the network still didn't work. So I plugged the Netgear back and uninstalled EVERYTHING network related, still no luck. I got pretty frustrated so I formated the system and reinstalled Win2K (I had just reinstalled 2 days prior to this incident, so no loss). So I'm starting fresh now with the 2nd Netgear card. I'll uninstall the Netgear and plug back the DLink and see if the network works, then I'll replace Netgear #1 with #2 and see how it goes from there.

Be back with an update soon .

 

[datallah]

Just because you can ping yourself doesn't mean your network setup is ok. When you ping yourself you are not necessarily actually using the network card at all. In my experience, problems like this tend to be one of 2 things: Crappy Wiring or PLBCK (Problem Lies Between Chair and Keyboard). First of all i assume that you made sure that your net cards are getting a link light (both on the hub and on the cards themselves). If this is the case, then it is likely a software problem (although it is still possible that your cables are somehow FECD, if you have access to a net cable tester, test them).

If you are using some sort of firewall software on the PCs, ICMP packet response could be disabled, which would prevent you from getting ping replies from remote machines (but u still could potentially receive responses from yourself because it isn't really pinging you).

 

[Rhombuss]

No luck, installed the DLink card, but still won't ping properly. So at least I know it's not the network cards.

 

[Rainsford]

So you reinstalled Windows and the D-Link on the computer that had the D-Link in the first place and it still doesn't work? Are you sure that you're using the same configuration for the network settings you were using when it all worked? That's the only thing I can think of that's left. I'd reinstall both network cards and make sure you do every step of the configuration correctly (like it was when everything worked). I have to get back to work, but I'll be back in about 3 hours, so let me know how everything's working out. If this doesn't work, there's got to be something else to try (there always is).

 

[Rhombuss]

Well, installed both DLinks back in the system - and everything works fine now. Still don't understand, something wrong with the FA310TX's driver support under Win2000? Because the Netgear site says the default windows drivers are official. I did notice when I took out the Netgear cards that the top layer PCB seems to look a little degraded, like it has been left in the sun and the heat toasted a small portion. Would this actually be a problem? Since the card detected fine, and was 'working' on a stand-a-lone basis. I would hate for these cards to be defective...

 

[Rainsford]

I don't know, that would be a question for an electrical engineer. But I might suspect Netgear's Win2k drivers. Did Windows 2000 detect and install drivers, or did you have to do it youself manually?

 

[Rhombuss]

Win2K did it automatically - also suggested the Linksys LNE-100TX as another suitable driver, which I found odd.

 

[Rainsford]

Hmm, that's kinda confusing. You would think Windows 2000 would have drivers which would work. It seems to me like a driver problem, I haven't used any Netgear stuff personally, so I don't know how their stuff works, but I like Linksys if you're looking for an alternative.

 

[datallah]

It is the same chipset as the linksys (the netgear is a bit better board). I have the same Netgear and it works just fine with the Linksys driver.

 

[TunaBoo]

You cant set you IP to 192.168.0.1, thats the IP of your router.

 

[rmblam]

Go into the NIC properties and check the duplex settings and all that jazz. I had a similar problem once and I found something wacky in there. Give er a look.

 

[Rainsford]

Um, I don't think Rhombuss has a router (at least not that he mentioned), so that's probably not the problem.