Re: DHCP assinged DNS servers don't work
- From: "Olaf Engelke [MVP Windows Server]" <oenews01@xxxxxxxx>
- Date: Thu, 6 Sep 2007 10:27:49 +0200
Hello,
"Joe" <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:249BBF41-75D1-4AD2-AEA9-D7CD7FF4B7E1@xxxxxxxxxxxxxxxx
I've posted this issue in other newsgroups with little success. HopefullyI have seen a similar behaviour only with the Windows Live One Care Firewall on my laptop. That blocked DHCP and DNS traffic by default.
someone here can help me.
I have 75 WinXP machines on a Win2K3 domain using DHCP for address
assignment. I have found that for some machines, using the DHCP-provided DNS
servers fails to resolve all internal host names. If I use DHCP for the IP
address only and manually add the DNS servers, name resolution works every
time.
In more detail, if I use DHCP to assign the name servers, the ping command
will fail on certain internal hosts. However, nslookup works every time. If
I manually assign the name servers (using the same addresses provided by
DHCP) ping works and so does nslookup.
Any thoughts or ideas are greatly appreciated. This problem is preventing
me from taking a new system live because a number of machines can't resolve
the name.
What is the output of ipconfig /all on the affected clients?
Are the client PCs "multihomed" (multiple network interfaces)?
Best greetings from Germany
Olaf
.
- Follow-Ups:
- Re: DHCP assinged DNS servers don't work
- From: Joe
- Re: DHCP assinged DNS servers don't work
- Prev by Date: Re: Programs unable to create files on share after SP2
- Next by Date: Re: Can you have 2 NICs connected to internet at the same time?
- Previous by thread: Re: Programs unable to create files on share after SP2
- Next by thread: Re: DHCP assinged DNS servers don't work
- Index(es):
Relevant Pages
|
Loading