Re: DHCP assinged DNS servers don't work

Olaf,
An ipconfig /all printout is below. This is definately not a firewall
issue. Although the WinXP firewall is enabled and configured via Group
Policy, the problem only affects certain machines. (It does seem to affect
laptops more than desktops. Not sure why.) None of the clients are
multi-homed. The first two DNS servers are AD controllers running ONLY core
services (AD, DNS, DHCP, IAS, WINS.)

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : vmtest
Primary Dns Suffix . . . . . . . : internal.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : internal.com
internal.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : internal.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-07-E9-D6-5A-D1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.153
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.75
DHCP Server . . . . . . . . . . . : 192.168.1.38
DNS Servers . . . . . . . . . . . : 192.168.1.38
192.168.1.39
192.168.1.14
Primary WINS Server . . . . . . . : 192.168.1.38
Secondary WINS Server . . . . . . : 192.168.1.39
Lease Obtained. . . . . . . . . . : Tuesday, September 04, 2007
11:23:01
AM
Lease Expires . . . . . . . . . . : Wednesday, September 12, 2007
11:23:
01 AM

C:\>

"Olaf Engelke [MVP Windows Server]" wrote:

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. Hopefully
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.

I have seen a similar behaviour only with the Windows Live One Care Firewall
on my laptop. That blocked DHCP and DNS traffic by default.
What is the output of ipconfig /all on the affected clients?
Are the client PCs "multihomed" (multiple network interfaces)?
Best greetings from Germany
Olaf


.

Relevant Pages

  • Re: Dynamic DNS, DNS Records & Scavenging
    ... There are two DHCP ... Both the servers are set to update A and PTR records for clients. ... DNS however this doesn't seem to be the case. ... DNSUpdateProxy and when i did this i saw my test laptop register its ...
    (microsoft.public.windows.server.dns)
  • Re: networking private and public hosts questions
    ... DHCP isn't going to "help". ... you need to run NAT. ... Move all the Servers to the private side of the Firewall and start ... Controllers must point to themselves in thier DNS Setting and the ISP's DNS ...
    (microsoft.public.win2000.networking)
  • Re: What are FSMO roles?
    ... Hardware firewall as DHCP ... ... SBS2000 is the DNS server, and of course, the DC. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 and DHCP
    ... firewall, which also administers forced virus protection ... SBS2003 on its own subnet 2) Use the SBS2003 DHCP server ... DNS comes from SBS2003) 3) Point the ...
    (microsoft.public.windows.server.sbs)
  • Re: Need DNS For Dummies! Please help!
    ... I set up DNS and DHCP on my Win2k Server without any ... > The FW/R is connected to the hub as are both of my servers. ... member servers and clients) MUST always and ONLY use ...
    (microsoft.public.windows.server.dns)