up vote 0 down vote favorite
share [g+] share [fb]

I'm on a small-business network with a mix of Ubuntu and Windows machines, both wired and wireless, as well as an Ubuntu fileserver (Samba), and a network printer. All these devices are on one big subnet, connected via switches to a Netgear WNDR3700.

What I'm finding is that I can always ping wired machines using hostname.local, but with machines on wireless (Ubuntu netbooks), the performance is inconsistent-- sometimes it works, sometimes it doesn't. I can always get to them by IP, but the ping time is more like 60-100ms. Would that be over some zeroconf timeout, or is there likely another problem?

Is it likely to be an issue with the wireless router? What's my best plan of attack here?

Thanks,

Mike

link|improve this question
The TLD .local is known to cause problems, because zeroconf uses this. The suggested TLD is .site or .internal. en.wikipedia.org/wiki/Tld#Pseudo-domains – ott-- Nov 4 '11 at 20:23
I'm attempting to contact these machine using zeroconf. – mikepurvis Nov 4 '11 at 20:35
1  
I would watch it with wireshark or tcpdump for differences in the cases works/doesn't work. – ott-- Nov 4 '11 at 21:01
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.