Mac Thread, My macs won't ping server but will ping server.prentonhigh.local in Technical; Hi All,
I have had an ongoing saga trying to connect my macs up to our active directory and somebody ...
1st December 2009, 12:47 PM #1
My macs won't ping server but will ping server.prentonhigh.local
I have had an ongoing saga trying to connect my macs up to our active directory and somebody suggested that i check that I can ping clients and servers from the macs.
When I either try ping of host then a machine name it fails but if I ping or host the fqdn it works.
I assume that this is a DNS error but I'm not suere where this could be rectified.
Could anyone help at all?
1st December 2009, 01:32 PM #2
You need to add your local domain name to the DNS search suffix list in the network control panel.
Something like this:
Hissohathair: How to set your DNS search list in OSX
If your server is at myserver.myschool.co.uk you would add myschool.co.uk as the search suffix.
ETA: Judging by your .sig you should add prentonhigh.wirral.sch.uk (or prentonhigh.local if the server isn't in your external DNS)
Last edited by keithu; 1st December 2009 at 01:36 PM.
Thanks to keithu from:
reggiep (1st December 2009)
1st December 2009, 01:37 PM #3
This sounds like it could be one of two things or possibly both?
Querying the hostname on the forward pointer and having it resolve to an IP address proves the forward lookup zone is configured. If it's returning the correct IP address then you know the zone is configured correctly. If you can verify forward queries return the correct information for all your servers then that's a good sign.
Querying the IP address on the reverse pointer and having it resolve back to the known hostname proves the reverse lookup zone is configured.
Doing the above queries using either the host, nslookup or dig commands basically 'qualifies' your DNS Service. Using ping is OK up to a point but it's not what I would use to troubleshoot DNS issues.
If you're not seeing a successful return on a reverse pointer query then that can only be because:
(a) There is no reverse zone configured
(b) There are multiple reverse zones configured
(c) DHCP Service is not configured as it should be?
(d) DHCP Service and is handing out the wrong information regarding DNS and Domains?
Another possibility is the main DNS Server (presumably your PDC?) is using it's own loopback address as the Primary DNS Server? In which case it won't resolve itself properly and potentially cause problems for successful profile discovery and access.
Hope this helps?
Antonio Rocco (ACSA)
Thanks to AntonioRocco from:
reggiep (1st December 2009)
2nd December 2009, 09:13 AM #4
Thanks, that did it. I've been trying all sorts of fixes for weeks! If you are at BETT I'll buy you a drink!
Originally Posted by keithu
2nd December 2009, 11:40 AM #5
You're welcome. Probably won't be at BETT so it'll have to be a virtual drink - cheers!
Originally Posted by reggiep
8th December 2009, 03:30 PM #6
- Rep Power
You also need to remember what link-local is actually for. It's not designed for enterprise networks - look at RFC 3927 - Dynamic Configuration of IPv4 Link-Local Addresses It's a botch job best used in the home or a small office.
I disable it in Linux.
By ianniow in forum Windows Server 2000/2003
Last Post: 24th June 2009, 02:13 PM
By russdev in forum Jokes/Interweb Things
Last Post: 23rd June 2008, 07:01 PM
By burgemaster in forum Wireless Networks
Last Post: 22nd April 2008, 12:29 PM
By sqdge in forum Windows
Last Post: 10th August 2007, 07:25 AM
By john in forum Wireless Networks
Last Post: 12th April 2006, 01:54 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)