Strange DNS failure

I have SQL (MSDE2000A) installed on a W2003 server.
I can connect to the database OK using either SQL or Windows authorization
from a W2000 (SP3) machine or from an XP Home (SP2) machine. But connection
from an XP Pro machine (SP1) fails every time - unless I specifically define
the DNS server IP address (i.e. the W2003 server) in the network config for
the XP Pro machine. The other two machines are quite happy connecting with
the DNS left as 'automatically detected'. They will connect to the database
whether logged on as part of the W2003 domain or as a 'this computer'.
Maybe of relevance: without the DNS defined, logging on to the domain takes
ages (5 minutes?) while the system is 'loading my settings'; as soon as the
DNS server is defined explicitly then logging on happens in an instant.
Everything else about the XP Pro machine works just fine - Windows Explorer
is quite happy finding machines (including the server) via its name, rather
than via it's IP, while the DNS is 'aoutomatically detected'.
At least one of our customers is having the same problem (i.e. can connect
via IP address but not by machine name) - this is also an XP cleint - I don't
know the server's OS in this case but the SQL is installed on another
workstation rather than on the server.
.

Relevant Pages

  • Re: Adding XP Client to NT 4 Domain
    ... > It should work fine if you are using Netbios over TCP/IP (Netbt). ... So you're saying that the XP Pro machine should be able ... with no DNS or WINS server service on the NT 4 server? ...
    (microsoft.public.windows.server.networking)
  • Re: Joining Domain Problem
    ... If the Pro machine is getting an IP from the router's DHCP server, ... Either configure the router to pass the IP address of your Server as the DNS ...
    (microsoft.public.win2000.active_directory)
  • Re: Joining Domain Problem
    ... If the Pro machine is getting an IP from the router's DHCP server, ... Either configure the router to pass the IP address of your Server as the DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Yet another Windows XP SP2 Firewall issue
    ... the server isn't doing it's disabling properly [but you say the others ... > new firewall features. ... Look up how to disable that group policy. ... > the 1 XP Pro machine on the network took to the new policy change just fine. ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow logon to 2003 domain and DHCP problems
    ... This sounds like a classic DNS issue. ... Domain Controller as well) have only the internal DNS Server IP Address and ... went from a 2K3 server to a XP Pro machine and a 1GHz P3 went from a XP ...
    (microsoft.public.windows.server.networking)
Loading