can ping one way, but not the other, lost packets

[ouchhhhh]

Setting up 3 win2k machines on a nexland switch.

2 of the machines receive the internet fine. The 3rd one will not.

All have the same workgroup name. The switch is 192.168.0.1, which I can ping from all 3 machines.

The problem is when I try and ping the 3rd machine from the other 2. All requests are timed out. Sometimes one packet will make it through. 5% of the time. Sometimes a website will BEGIN to appear on 3rd machine. So the packets are getting lost before reaching it.

On 3rd machine, I've released ipconfig, disabled the network card, taken out all services, clients, protocols. rebooted. ipconfig /all shows the gateway as 192.168.0.1 and its ip address as 192.168.0.4. looks ok. Also, all 3 machines show up on each machine in "network places".

3rd machine originally was a standalone unit. It received internet and worked fine, BEFORE I placed into new configuration w/ internet routed to all 3. btw the 2 that work have netgear cards. the 3rd a 3com. think thats it. thanks

 

[bcastner]

Apply the utility I discuss in faq779-4625
It sounds like a case of Winsock or Winsock2 service corruption, which has odd consequences to resolving TCP/IP addressing, and other issues.

Best,
Bill Castner

 

[ouchhhhh]

It didn't work.

I tried the utility, and I also tried manually removing both winsock and winsock2, and replacing w/ good ones. Also typed in.. "netsh int ip reset resetlog.txt" in command window. That gave me.. the command was not found: int ip reset resetlog.txt.

I actually used this fix on machine 2 earlier and it worked. Even though I received that bad command message.

Any other ideas?

I'm going to unplug the thing tonight and let it sit.

 

[bcastner]

. Tell me about any firewalls involved. (Including "hidden" firewalls with antivirus programs) PC-Illan does this with a default install;

. Tell me what if any AV or firewall software you have removed from a client. A good exampled:

http://www.bl.com/moshe/text/quiddities/norton_errors.html_Text_Archives/

. Did you adjust the network adapter (NIC) properties? It is safest to leave at "Auto" for speed and Duplex. But manually test at 10, 1/2 Duplex and see if the issue resolves.

 

[ouchhhhh]

It is a new hard drive w/ a fresh install of win2k. No firewall or antivirus programs on it. I don't have any restrictions set on my access filters on the router.

I tried changing the duplex settings. No change.

 

[bcastner]

As a next step, use the utility discussed in faq779-4625

 

[ouchhhhh]

Bill,

Did you mean to reference the same article/utility? I tried it w/ no success. thanx for the help.

 

[bcastner]

I was not very clear. See the two MS KB articles linked at the bottom of the FAQ.

. Use the WinsockFix utility first, as it will rebuild the registry;

. Then apply the MS KB suggestions to re-install TCP/IP:

http://support.microsoft.com/?kbid=811259

. then use the WinsockFix utility again.

 

[ouchhhhh]

finally had time to work on this...

I looked at that article and ran the netdiag test. Looked ok. I've reinstalled the 3com driver. Tried a different cable too. It's still not working correctly. I just pinged that computer from this one. 4 Packets made it through. then tried again. 1 made it. again.. none made it. then again.. all 4 made it. again.. 3 made it. again.. none made it.

Yet ping the other way... never a lost packet.

Any more ideas? thanks.

 

[krr]

It could be an auto-negotiation problem between the 3Com card and the switch, resulting in a full/half-duplex mismatch.

If the switch is manageable try setting the port to 100half. If not, try to set the 3Com card to 100half (you'll need the driver and diagnostic utility from 3Com, not the driver that comes with Windows!).

Hmm, just wondering: Are you using the driver that comes with Windows? In any case, you should use the latest driver from 3Com. Perhaps this will solve the problem without configuring anything.

Cheers *Rob

 

[ouchhhhh]

I ran the 3com diag kit. Network connectivity was successful, and the card came out ok too. I've tried a few different drivers.

I again tried a cable from this computer i'm on now in the one next to me w/ problems. Won't work, so its not the cable or ports.

Still, its losing packets when I ping it. Ihave no clue here. Try a new card I guess.

 

[ouchhhhh]

I'VE NARROWED IT DOWN SOME. I'm running a dual wan switch. I have comcast and dsl. I disconnected the comcast connection through the setup interface. The computer 3 NOW works fine. So, what I've done and found out so far...

started w/ computer 3. which had comcast directly into it. Then setup switch. Other 3 comps had dsl and software routing using sygate.

1 dual wan router: 192.168.0.1
comp 1: 192.168.0.2
comp 2: 192.168.0.3
comp 3: 192.168.0.4 <-- wasn't working and originally had comcast on it before I setup the switch w/ all 4 computers.
comp 4: 192.168.0.5

disconnected comcast in switch interface. Everything works fine. dsl still connected. I reboot comps, switch, etc.

Now 2 of my lan addresses switch, so...

1 dual wan router: 192.168.0.1
comp 1: 192.168.0.4
comp 2: 192.168.0.3
comp 3: 192.168.0.2 <-- was machine not working.
comp 4: 192.168.0.5

I connect comcast back up through my switch interface setup screen so dsl and comcast are shared, and the same computer 3 (now w/ different lan address) has the problem of losing packets, and not receiving web pages.

So it doesn't matter which lan address comp 3 has. It still has the problem.

 

[ouchhhhh]

***
When I setup the switch I used the physical address given in ipconfig /all on comp 3 and entered that in as my mac address on my switch interface setup screen.

I just did an ipconfig /all on all 4 comps. comp 3's physical address still matches the mac address I entered into my switch. Is there a conflict?

 

[ouchhhhh]

swapped the nic... worked

 

[WolverineTek]

Hey Ouch,

Did you swap it with the same NIC model, or a different model?



Wolverine
Compuware Corp.