Attaching Windows XP Pro Machines to Win2K Server

  • Thread starter Thread starter gnathan.barnes
  • Start date Start date
G

gnathan.barnes

I've had the following problem every single time I've tried to attach a
new Windows XP Pro workstation to my Windows 2000 Server;

Logon Failure: unknown user name or bad password.

I am using the correct administrator username and password to try to
attach to the network. Eventually every other computer has attached,
but some took as much as a month to do so. Anyone have any ideas as to
how I could get this to work faster? It's VERY frustrating. Thanks for
any help you can give.
 
I would check the DNS first. Can you ping the DC using the name?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I've had the following problem every single time I've tried to attach a
new Windows XP Pro workstation to my Windows 2000 Server;

Logon Failure: unknown user name or bad password.

I am using the correct administrator username and password to try to
attach to the network. Eventually every other computer has attached,
but some took as much as a month to do so. Anyone have any ideas as to
how I could get this to work faster? It's VERY frustrating. Thanks for
any help you can give.
 
I've had the following problem every single time I've tried to attach a
new Windows XP Pro workstation to my Windows 2000 Server;

Logon Failure: unknown user name or bad password.

I am using the correct administrator username and password to try to
attach to the network. Eventually every other computer has attached,
but some took as much as a month to do so. Anyone have any ideas as to
how I could get this to work faster? It's VERY frustrating. Thanks for
any help you can give.

Nathan,

I don't see any obvious hints in your report that would suggest any quick fixes.
Do you have any idea what you did after a month that permitted every other
computer to attach?

Try reading my article:
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html

And in particular this section, with a link to a Microsoft whitepaper:
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#OlderOS>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#OlderOS
 
Chuck, thanks for the article. Everything seems to be in correct order
for the XP pro machine to attach. I did not do anything before the
domain decided to allow me to attach the other XP machines to the
network. I just kept trying to attach and one day it let me.
Unfortunately, this isn't entirely useful to be able to recreate the
conditions. Thanks for any help you can give.

Nathan-
 
Chuck, thanks for the article. Everything seems to be in correct order
for the XP pro machine to attach. I did not do anything before the
domain decided to allow me to attach the other XP machines to the
network. I just kept trying to attach and one day it let me.
Unfortunately, this isn't entirely useful to be able to recreate the
conditions. Thanks for any help you can give.

Nathan-

Nathan,

OK, since this is a domain, make sure that the computers, and the domain, are
setup properly.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html
 
Everything appears to be set up correctly. I'm going to do a hard
shut-down/restart of the DC and see if that might force it to fix
itself. If you have any other suggestions, I would be very
appreciative. Thanks for the help so far!
 
Well, I did the shut-down/restart of the entire DC. That did not help.
I tired adding the machine WITHOUT the computer in the AD to see if
that was the problem, still got the same error. I tried adding the
machine WITH the computer in the AD and letting everyone add it, still
the same problem. I think I've narrowed down that it is a DC issue, but
I just don't know what it could be! Any suggestions would be great,
thanks for the help so far.
 
Well, here's an interesting tidbit that might narrow down the problems
I am having. I had NO PROBLEM attaching an XP Desktop. Only the Lenovo
Laptop is giving me a problem! Anyone know what might be causing that?
(other than the fact that it's a Lenovo) Or if there is a setting in
the DC that I might need to change to allow laptops to join the domain?
It does have SP2 so there isn't a problem with the SAM accounts. Thanks
for any ideas people might have.
 
Well, here's an interesting tidbit that might narrow down the problems
I am having. I had NO PROBLEM attaching an XP Desktop. Only the Lenovo
Laptop is giving me a problem! Anyone know what might be causing that?
(other than the fact that it's a Lenovo) Or if there is a setting in
the DC that I might need to change to allow laptops to join the domain?
It does have SP2 so there isn't a problem with the SAM accounts. Thanks
for any ideas people might have.

These are all XP Pro systems? Maybe CPSServ will provide a clue. Run CPSServ
from the problem computer, from 2 properly working computers, and from the
server.
<http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html>
http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html
 
Well, the problem machine is a Win XP Pro laptop, the machine that went
in without a problem is an XP Pro desktop, and the server is Win 2K
Server with SP3. Not that I don't trust you, but there are some remote
access capabilities with PSTools that I am not that keen on installing.
Can I just download specific packets so that we can get the information
that you need? Looks like PSInfo, PSList and PSLogList and possible
PSService would be fine to download and get info from. Let me know.
Thanks for all your help!
 
Well, the problem machine is a Win XP Pro laptop, the machine that went
in without a problem is an XP Pro desktop, and the server is Win 2K
Server with SP3. Not that I don't trust you, but there are some remote
access capabilities with PSTools that I am not that keen on installing.
Can I just download specific packets so that we can get the information
that you need? Looks like PSInfo, PSList and PSLogList and possible
PSService would be fine to download and get info from. Let me know.
Thanks for all your help!

Nate,

Well, PSService is what you need to run. CPSServ just makes it easier to run
PSService, and redirect the output. You're welcome to run PSService by hand, I
simply want the output of:
psservice find browser
psservice find lmhosts
psservice find remoteregistry
psservice find server
psservice find sharedaccess
psservice find workstation

On a well running LAN, you should be able to see each service (within limits)
running on each computer, from each computer. By finding out which computer (if
any) can't see a service running on another computer, we may be able to find
your problem.

Or, we could try CDiag.
<http://nitecruzr.blogspot.com/2005/05/using-cdiag-without-assistance.html>
http://nitecruzr.blogspot.com/2005/05/using-cdiag-without-assistance.html

I can't guarantee that either tool will identify your problem, both are simply
ways of looking for your problem. It's your choice, since it's your network.
 
Here are the results from the problem computer:

Start CPSServ V1.02 - BAS-LAP003

Find Computer Brower ("browser")
Error browsing network:
No active service named browser found.

Find TCP/IP NetBIOS Helper ("lmhosts")
Error browsing network:
No active service named lmhosts found.

Find Remote Registry ("remoteregistry")
Error browsing network:
No active service named remoteregistry found.

Find Server ("server")
Error browsing network:
No active service named server found.

Find WF / ICS ("sharedaccess")
Error browsing network:
No active service named sharedaccess found.

Find Workstation ("workstation")
Error browsing network:
No active service named workstation found.

End CPSServ V1.02 - BAS-LAP003

When I get a working machine that I can run this on, I will post that
as well. Hope this helps a little. If it's not what you are looking
for, let me know and I'll run it again. I only downloaded the PSService
part of the PSTools, so this might not have all the info you are
looking for. Thanks again.
 
Back
Top