XP Pro Conecting to a Windows 2000 server!

  • Thread starter Thread starter RyanWirth
  • Start date Start date
R

RyanWirth

Hello Everyone,

I have been following posts with XP Pros problems with 2000 server but
nothing is helping with my current problem, Im also 3 weeks into a new
job where I admin half the time:

I have 20 users off my windows 2000 server that is connected to a
router, using dynamic IPs and "Obtain DNS server IP automatically," so
all of the MS2000 users connect automatically and work great.

But then the users wanted XP (blah blah) so we have two home versions
(which work fine) one XP Pro that works great, and one XP that ~used~
to work great.

The broken XP went to china for a week and came back and could no
longer connect to the network the way it could when it left. As far
as I can tell all of the settings are exactly the same as the other XP
pro here, but I cannot change its network ID from a workgroup (used in
china) to the domain "here.com" used here! I get the error:
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.here.com
Common causes of this error include the following:
- The DNS SRV record is not registered in DNS.
- One or more of the following zones do not include delegation to its
child zone:
here.com
com
.. (the root zone)

The broken XP can surf the net, check mail (all through the
server->router), ping the server, ping everyone else ... I can ping
it. nslookup works and returns the IP for my "here.com"
On the server, I get a warning event (5782) around the same time as I
try to find the server from the XP, which says "Dynamic registration
or deregistration of one or more DNS records failed with the following
error:
No DNS servers configured for local system."


No other computer here has a LMHOSTS file that I can copy, and since
they dont need one I dont think the broken XP should be unique.

So, to recap:
One broken XP with the same settings as the working XPs that cannot
connect to the Domain (using dynamic everything) here.com, but it can
surf the web, ping the server, ping other users and it can get pinged
.....

Any help would save my sanity,

Ryan
 
I can't make much sense of your one XP problem, but
something else caught my eye...
XP home is incapable of logging on to a domain.. it does
not have the code in the OS at all.. you need PRO for that.
So.. I don't know how you ever had a XP Home machine
logged onto your W2K server.
Can you check your data and send again?
 
Put the 'china'-XP in a workgroup and reboot. After that rejoin it to the
domain.
What is your FQDN-name?

Marina
 
Thanks for your quick reply. I have one Pro using the Domain, and the
two homes are using the workgroup but operating fine. Turns out my
problem was that we are using NetBEUI (Im on my second week with this
company) which is unsupported by XP, so I had to set a static DNS
server IP, and update the LMHOSTS file with the IP for the server.
Now it can see the server, and the users drive on the server, but no
other network resources. So Im still working on it ...

Thanks again,
Ryan
 
I got it all working, so I will just document this incase anyone else
has the same problem:

Windows XP and Windows 2000 Server

Our server uses the NetBIOS Extened User Interface (NetBEUI), a
network protocol that is used (and Im just learning here) for finding
IP addresses and DNS (Domain Name Service for translating host
addresses into IP addresses ex. Ryan.domain.com to 10.1.1.18). XP no
longer supports NetBEUI so it will have trouble finding the domain
domain.com, and any computer name on that domain.

When I tried to add an XP pro computer to the domain Domain.com (in
standard procedure) I would get the error:
"Note: This information is intended for a network administrator. If
you are not your network's administrator, notify the administrator
that you received this information, which has been recorded in the
file C:\WINDOWS\debug\dcdiag.txt.
The following error occurred when DNS was queried for the service
location (SRV) resource record used to locate a domain controller for
domain domain.com:
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.com
Common causes of this error include the following:
- The DNS SRV record is not registered in DNS.
- One or more of the following zones do not include delegation to its
child zone:
domain.com
com
.. (the root zone)
For information about correcting this problem, click Help. "

To correct this problem I needed to added the domain Domain.com to the
XP machines LMHOSTS file ("LMHOSTS" with no extension). The file now
reads

127.1.0.0 localhost
10.1.1.200 main01 #PRE #DOM: domain.com
10.1.1.200 main01.domain.com
10.1.1.3 allen
10.1.1.3 allen.domain.com
10.1.1.16 nona2
10.1.1.16 nona2.domain.com

That is from memory so don't quote me on that. A sample file is
provided in the location where the LMHOSTS needs to be placed (search
the windows directory for hosts to find it). Open the sample file
("LMHOSTS.SAM") and make changes and save it with out the extension
("LMHOSTS") to the same directory. You should now be able to add the
domain, after a reboot, and see all computers whose addresses you
added to the LMHOSTS file.

Hope this helps someone else,
Me.
 
Back
Top