Thin Clients not booting

[pwaddington]

I have a large number of thin client devices on my network that (up until last Tuesday) were booting to a windows 8 server and connecting fine. Since last week, some fail when connecting to the remote desktop servers yet some in the same classroom work. If i switch a thin client that has connected fine into a port where a thin client has failed, it wont boot and vice versa. The problem isn't site wide so it can be tracked to 4-5 switches which is displaying the error. I'm inclined to beleive that there is a rogue device or NIC card on the network that is broadcasting resulting in the slowdown.

 

Can anyone offer any advice?

[Duke]

You might be better off posting this in the network forum as it does sound like a network issue.

 

Do you have any way of working your way back up the switch hierarchy until the issue disappears, then trying to narrow it down to a specific port causing the issue? Failing that can you set one of the switches to mirror a 'bad' port and plug a machine running wireshark into it to do some packet monitoring and see if you can find some more info on the cause?

[pwaddington]

It turns out that the ethernet first mile RAD box is the cause of the problem. If its switched off then the network speed is restored and the thin clients boot fine. RM have been notified as they supply our internet service.

[Duke]

Cool, glad you got it sorted.