next »

[Hijpo]

While in on work experience in a factory i was connecting a new pc to the network. When i booted it, it was saying limited or no connectivity. NIC checked out ok, so i connected it to a diffrent socket on the wall and it connected fine. I put a fluke on the origional socket and it checked out fine.

So both machine and socket check out fine, but when both are connected theres no connectivity.

 

[Wooster]

It could be the other socket is connected to a switchport on a different VLAN, or the port might be set up to use a static IP (i.e. a network printer) and the other uses DHCP.

[Hijpo]

im in there again tuesday, so ill ask if they sorted it.

[Wooster]

What Fluke tester did you use?
Linkrunners will show connectivity at times even if you have a fault on a pair, so it needs to be tested end to end.

(That wee foible with them got Rosco a shift on Thursday  )

[Hijpo]

Turns out that area was never meant to be expanded, and when they configured the DHCP server they set it to only lease 128 address's so when they added the new machines they couldnt be assigned an IP. Its only when a few other machines shut down and these ones connected, they realised what the problem was.