I've got a weird scenario in my high school lab:
- computers are connected to wifi and the internet
- kids are on websites, playing games, streaming audio, active internet connection
However, when I log into a computer I use to push updates and manage remotely, I'm unable to ping + ssh to many of the hosts which are currently active.
I'm using host.local addressing space, so say I login to
lab07.local and then try to
ssh lab22.local and can't resolve the hostname. This can last a few seconds or even a couple minutes and then connectivity comes back at some point.
Could this have something to do with the way .local addresses are resolved? should I try some sort of naming convention? Maybe I'll try with IP's directly this next time.