XP not logging into server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I loaded Win 2k about 2 months ago with AD on a DC. All computers have been working fine until 2 days ago. One of my XP machines would not log on to the server. Then today, 2 more could not log on. I have Win 2k and 98 machines logging one without any problems. When I do an nslookup, it says that it can't find the server. I checked out the server and it appears that the ".com" did not get added to the end of the domain name when I entered it in. What can I do?
 
In
Ken said:
I loaded Win 2k about 2 months ago with AD on a DC. All computers
have been working fine until 2 days ago. One of my XP machines would
not log on to the server. Then today, 2 more could not log on. I
have Win 2k and 98 machines logging one without any problems.
Click to expand...

What was the last thing you changed or updated? Possibly Service Pack 4?
Are all your clients only pointing to your internal DNS server and NOT the
ISPs? This part is *very* important for AD to function. Win9x clients do not
connect this way, that's why they are connecting and not your newer
machines. So that's what leads me to this guess at this time without knowing
more about your config.

If you can post an unedited ipconfig /all from your DC and one of the
clients having this issue, that would be very helpful.
When I
do an nslookup, it says that it can't find the server.
Click to expand...

This is a separate issue. Nslookup upon intialization tries to do you a
favor by looking up the IP address in your reverse zone and display the name
of the machine. If you don't have a reverse zone for your subnet or if you
do but there is no PTR entry for the DNS server, then that message (not an
error, mind you), will get displayed. I guess you'll know how to fix this
now.

I checked out
the server and it appears that the ".com" did not get added to the
end of the domain name when I entered it in. What can I do?
Click to expand...

My initial feeling is that you have a single label domain name, which SP4
changed support on that. If you forgot to enter the TLD (the .com in this
case) in Active DIrectory, then that would be considered a single label
name. You'll need to reconfigure your domain from scratch or setup another
server with AD on it with the correct name and migrate the user accounts
over to it using the ADMT tool.

See this for more information on how to "bandaid" the server. But keep in
mind, that your XP clients will continue to have issues since they don't
play well with single label names.
http://support.microsoft.com/?id=300684

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thanks for your quick response, I appreciate it. With regards to the article that you sent me, I found it and tried it yesterday but the regedit entrys did not exist on the server or one of the workstations that is having the problem. For example, this one:

To enable such a domain member to use DNS to locate domain controllers in domains with single label DNS names in other forests, set the AllowSingleLabelDnsDomain (REG_DWORD) registry value to 0x1 under the following registry key on each domain member:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

None of them worked. Thanks again.

----- Ken wrote: -----

I loaded Win 2k about 2 months ago with AD on a DC. All computers have been working fine until 2 days ago. One of my XP machines would not log on to the server. Then today, 2 more could not log on. I have Win 2k and 98 machines logging one without any problems. When I do an nslookup, it says that it can't find the server. I checked out the server and it appears that the ".com" did not get added to the end of the domain name when I entered it in. What can I do?
 
In
ken said:
Thanks for your quick response, I appreciate it. With regards to the
article that you sent me, I found it and tried it yesterday but the
regedit entrys did not exist on the server or one of the workstations
that is having the problem. For example, this one:

To enable such a domain member to use DNS to locate domain
controllers in domains with single label DNS names in other forests,
set the AllowSingleLabelDnsDomain (REG_DWORD) registry value to 0x1
under the following registry key on each domain member:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

None of them worked. Thanks again.
Click to expand...

The reg entries have to be added manually on your part. Not sure if you
added. By the looks of your response, you didn;'t add it, but do correct me
if I'm wrong.

The article points out, and the section that you quoted, that you'll need to
add the following key as a DWORD:
AllowSingleLabelDnsDomain
Then set it's value to 1

Hope that helps.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top