XP DNS problem in Windows NT network

[Guest]

Our Agency has a Windows NT network with the PDC serving as a DNS server and
WINS server as well. This configuration has had no problems at all with the
Windows NT clients, but we are now adding Windows XP Pro (SP1) clients onto
the network. For the most part, the XP clients seem to participate
successfully: no problems joining the domain, and accessing most resources.

However, there seems to be a latent defect with Windows XP in terms of DNS
resolution when working with the NT DNS server. Almost all of the time after
the XP computers are logged onto in the morning, addresses resolved by the NT
DNS server do not initially work (i.e. Internet Explorer will produce a "Page
cannot be displayed" error). a PING or TRACERT will fail to even resolve the
name involved.
However, DNS resolution to the ISP provider (for those users who have
authorized Internet access) doesn't seem to be affected by this problem.

I believe it is a defect with XP because if I merely stop, and then restart,
the "DNS Client" service, the address resolutions from the NT DNS server
start working as expected. In fact, I have added these stop/start commands
to most users' logon scripts as a "temporary workaround". However, this is
not acceptible for the long term because the users must also be given
Administrator priveleges in order for the NET command to work in the logon
scripts.

I tried reporting this defect to the computer manufacturer (as Windows XP is
an OEM installation), but they claim they cannot get involved with a
Microsoft problem. I have not read anywhere that there is any limitation on
running a Windows XP client in an NT server configuration. I also searched
the knowledge base and Internet without much success. If anyone can offer
any insight (i.e. Is this a known limitation, are there any other more
acceptible workarounds that might be tried, etc), I would be most
appreciative.

 

[Eric Niewoehner]

I have only a few ideas to explore:
* Key difference, if I recall, between Windows NT and 2000 DNS is the
availability of Dynamic DNS.
* There is a control in the Advanced TCP/IP protocol properties where
you can turn off the function for Dynamic DNS (Register this
connection's address in DNS)
* If that doesn't work, try a trick I have used regarding
Administration-level scripts. I have inserted scripts into the
Scheduler applet in Control Panel, and run them as a designateed
Administration-level account. You can set it up to run upon Logon or
System Startup. The cool thing is that there is no visual evidence of
the procedure being run on the user's desktop. You can, however, see
the process being run in Tast Manager.

 

[Guest]

Thanks for your reply.

1. Regarding the first suggestion ("Dynamic DNS"): I have already tried
unchecking the "Register this connection's address in DNS" option, even though
it technically shouldn't have any impact on the client's ability to perform
basic
address resolution. However, the same problem existed after trying that, so
I turned the option back on.

2. Regarding the 2nd suggestion: I had considered the option of issuing the
NET commands via a scheduled task instead, to be able to remove the users'
Administrator priveleges locally. However, the whole "workaround" of using
the NET commands to stop/restart the DNS Client is unacceptible because it
is unreliable and flaky. Sometimes, it needs to be issued a 2nd time for it
to
work, and it seems to have a limited effective time (maybe some sort of Time
To Live factor involved??) and the DNS resolutions often get "lost" again some
time later in the day. Again, this seems to point to some fundamental flaw in
the communication/synchronization between the XP client and the NT DNS
server.