Mike For any network service, you probably should make sure that the machine name can be resolved to an IP address, and an IP address back to a name as the reverse lookup is frequently used to detect IP spoofing.
So, for example, if client PC A on 192.168.1.1 is connecting to the server PC B on 192.168.1.2 for a service (SAMBA share, Telnet, SSH, etc.) then you should make sure that B can resolve A's IP address to a name somehow or other. DNS is always the best way but reverse DNS lookups don't always get set up correctly, in which case you can put an entry for PC A in the /etc/hosts file of PC B. Since it's easy to do, it might be worth doing it as a quick test for your problem - but the connection delay can be caused by reverse DNS lookups failing and timing out after 30 seconds or so. It is important to get name resolution working correctly, even on an isolated LAN, and even if it means just using manually edited hosts tables. I hope this helps. Peter On 5 July 2011 17:30, Mike Burrows <testerm...@knology.net> wrote: > ** > On 7/5/11 9:42 AM, Benjie Gillam wrote: > > My guess is that his iPad used your IP address beforehand and requested > 'johnrs-ipad' be it's hostname during the DHCP request a while back. When > your MacBook did a DHCP request, the server recycled the old iPad record > without properly cleaning it first. > > Benjie. > > On 5 July 2011 15:28, Mike Burrows <testerm...@knology.net> wrote: > >> Hello folks. >> I am connecting to the LAN at work from my macbook. When I open a terminal >> i get this message: >> >> Last login: Tue Jul 5 09:19:23 on ttys000 >> johnrs-ipad:~ testermike$ >> >> We do have a John R at work and he does have an ipad. However I can't >> understand why its reporting my macbook as his ipad. >> >> > Yes that makes sense. What has peeked my interest is that clients, can > connect to a 'network drive' for the PCs or 'server' for the macs but it > takes a while before the connections are established. Then if you navigate > away from the share and then go back to it, say in windows explorer, it > takes even longer to establish the connection again and sometimes wont at > all. > > could it be that this dns oddity is causing the domain controller to lose > track of its clients? > > Cheers > Mike > > -- > Please post to: Hampshire@mailman.lug.org.uk > Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire > LUG URL: http://www.hantslug.org.uk > -------------------------------------------------------------- >
-- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --------------------------------------------------------------
