![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sobriqueThis is _really_ weird.
Since yesterday we've had network problems.
But not of the 'nothing can communicate on the network'. Nor 'machines plugged into a particular network segment are unreachable'.
Nope. We've had a _few_ machines unable to reach _some_ parts of the network.
Most noticable when these are servers of course.
First incident, was on our vmware server - workstations couldn't communicate with the DHCP server that's running on there. Either to get DHCP addresses, or to just ping it or whatever.
Another machine though, on the SAME network, sharing the SAME interface was fine. And this machine could also communicate freely with our DHCP server.
As far as we could tell, packets to/from this machine weren't leaving the network switch it was plugged into. Where an almost identical machine, on the same physical hardware had no problems.
Ok, we sorted that by re-cabling that port into another switch. Only to come in this morning, and find that that wasn't the only culprit. Several machines, on COMPLETELY DIFFERENT network switches were exhibiting the same problem. One or two workstations in different areas of the site, and a couple of servers.
Very wierd. Reconnecting them to another physical switch in the same logical unit seemed to resolve the problem though.
Still don't know what the problem is mind you, but at least we now know what's happening, and how to stop it from doing so.
Damn, I'm looking forward to the pub tonight.
(incidentally: PUB TONIGHT. BEER ENGINE. 7ish. Don't bring a supersoaker)
Since yesterday we've had network problems.
But not of the 'nothing can communicate on the network'. Nor 'machines plugged into a particular network segment are unreachable'.
Nope. We've had a _few_ machines unable to reach _some_ parts of the network.
Most noticable when these are servers of course.
First incident, was on our vmware server - workstations couldn't communicate with the DHCP server that's running on there. Either to get DHCP addresses, or to just ping it or whatever.
Another machine though, on the SAME network, sharing the SAME interface was fine. And this machine could also communicate freely with our DHCP server.
As far as we could tell, packets to/from this machine weren't leaving the network switch it was plugged into. Where an almost identical machine, on the same physical hardware had no problems.
Ok, we sorted that by re-cabling that port into another switch. Only to come in this morning, and find that that wasn't the only culprit. Several machines, on COMPLETELY DIFFERENT network switches were exhibiting the same problem. One or two workstations in different areas of the site, and a couple of servers.
Very wierd. Reconnecting them to another physical switch in the same logical unit seemed to resolve the problem though.
Still don't know what the problem is mind you, but at least we now know what's happening, and how to stop it from doing so.
Damn, I'm looking forward to the pub tonight.
(incidentally: PUB TONIGHT. BEER ENGINE. 7ish. Don't bring a supersoaker)
