Jump to content

Recommended Posts

Posted

Hello,

 

Recently I cannot seem to ping ~ half of our computers (yes they are on! :p), which also brings with it the fact they cannot print or access the internet.

 

Now when I'm pinging one of our switches I'm not getting consistent results, one set of pings will give me a 10ms response, while another set will give me upwards of ~400ms whilst pinging another switch will always give me ~4 - 10ms ping every time.

 

Made even harder by the fact that when these were installed the guys didn't bother to label any of the ports :rolleyes:

 

Any suggestions?

Posted
That doesn't sound right at all. You should get 1ms or close to within a LAN. Have you tried rebooting the switch(es)? Do you have any VLANs setup? Have you tried resetting to factory default and if necessary upgrading the firmware?
Posted

Are the machines all on the same switch or different ones?

 

What does their ipconfig report? Are they getting a DHCP address? Are they set to the wrong static address...

Posted (edited)

LAN storm? or has some eejit looped a cable?

 

Check your switches - are any of them going mad?

 

Edit:

Nobody's running a ghost multicast are they? that can wipe out whole chunks of network (especially wireless APs)

Edited by BatchFile
Just thought of another
Posted

Thanks for the suggestions guys.

 

I rebooted them both after managing to get to them and everything seems to be working fine now apart from the pings...

 

When I ping -t the offending switch I can see it slowly rise to nearly 800ms and then back down to around 9ms over about 6 seconds (even did this when I was plugged directly into port 1 on the switch... weird).

Posted
When I ping -t the offending switch I can see it slowly rise to nearly 800ms and then back down to around 9ms over about 6 seconds (even did this when I was plugged directly into port 1 on the switch... weird).

 

What sort of switch is it?

Posted
Is it possible to isolate that switch (disconnect the uplink) without bringing the network crashing down? if so, try it, see if the ping time returns to normal. If it does, I'm going for a loop.
Posted
That explains everything. :troll:

 

Ha! I didn't pick it, im innocent I swear! :p

 

Is it possible to isolate that switch (disconnect the uplink) without bringing the network crashing down? if so, try it, see if the ping time returns to normal. If it does, I'm going for a loop.

 

Will give it a go.

Posted
That explains everything.

 

I don't see why. I've only had one problem with Netgear's pro range, and it didn't affect link quality. If you've had a bad experience, do please be less vague.

Posted
I had trouble imaging a bunch of laptops that had Marvell Yukon ethernet on them using a 48 port netgear switch. It worked fine with a 3com we had lying around, but we pinned that down to a configuration problem. We had to increase the max packet size on something somewhere and then it all worked. It turned out not to be the switch that was at fault.
Posted

I haven't been able to get at the switches yet, but I ran Wireshark and when it happens I'm getting results from two different computers, with the broadcast address as the destination.

 

The protocol is NBNS and the Info says "Name query NB M41N.ATH.CX<00>"

 

Any ideas?

Posted

I would try and reset the switch to factory default to wipe any configuration settings. If there was a loop it would affect the whole network, not just one switch.

 

If resetting to factory default and isolating the switch makes no difference I would contact Netgear themselves for a replacement.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...