Re: Mac and Windows 2003 DNS Resolution?
- From: William Smith <mecklists@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 04 Apr 2005 21:53:30 -0500
In article <d2s9kc$8bb$1$830fa7b3@xxxxxxxxxxxxxxxx>,
"Nik Price" <Nik@xxxxxxxxx> wrote:
> Can anyone shed any light on a problem I am having? I am trying to add a
> mac mini running a fully up to date version of OS X to my Windows 2003
> Domain. The mac obtains it's ip via DHCP fine, and I manually enter the DNS
> IP. NSLOOKUP and DIG resolve hostnames from IP's and IP's from hostnames
> perfectly, but if I try to PING the 2003 server by hostname, ping cannot
> resolve the hostname, but I can PING by IP number!
>
> I want to use the Active Directory on the windows server, and the exchange
> server, but none of these will resolve by hostname, which I assume is
> related to the same problem as the ping issue.
>
> Can anyone shed any light on this?
Ni Nik!
Does your DHCP server also provide DNS addresses? If so, I'd not put
anything in the DNS server field and let DHCP provide everything. Any
DNS entry entered on the client side will over ride DHCP supplied DNS
addresses whether it's right or wrong.
Your problem sounds like your domain name may be entered either
incorrectly or not at all. This is also something that should be
provided by DHCP but some administrators fail to include it.
You've tried "servername". See what happens when you enter
"servername.domain.com".
In the TCP/IP settings for your Mac add your internal domain name to the
Search Domains field. It should be something like "domain.com" or
possibly "doman.local".
Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP)
.
- References:
- Mac and Windows 2003 DNS Resolution?
- From: Nik Price
- Mac and Windows 2003 DNS Resolution?
- Prev by Date: Mac and Windows 2003 DNS Resolution?
- Next by Date: Language kit pack
- Previous by thread: Mac and Windows 2003 DNS Resolution?
- Next by thread: Language kit pack
- Index(es):
Relevant Pages
|
Loading