XP won't authenticate to SBS 2003 after joining Domain

The last of 6 XP pro desktops has failed to authenticate with the newly
configured SBS 2003. Following the addition of users and computers to the
server, I ran the browser based connection utility
(http://server/connectcomputer) on this particular XP desktop. It went thru
it's routine and rebooted. The new logon came up but would not accept the new
ID and password. It kept saying that the domain server was unavailbale. Try
again later. Unfortunately, the user doesn't remember his previous windows
password so I can't even get to the workstation only.
Any suggestions???? This is desparate.

sounds like dns issue. can you ping dns server by ip and name?

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
Networking Solutions, http://www.chicagotech.net/networksolutions.htm
VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
VPN Process and Error Analysis, http://www.chicagotech.net/VPN%20process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
"Wizard52" <(E-Mail Removed)> wrote in message
news:F5F58AC6-949B-46D6-A1C7-(E-Mail Removed)...
> The last of 6 XP pro desktops has failed to authenticate with the newly
> configured SBS 2003. Following the addition of users and computers to the
> server, I ran the browser based connection utility
> (http://server/connectcomputer) on this particular XP desktop. It went
> thru
> it's routine and rebooted. The new logon came up but would not accept the
> new
> ID and password. It kept saying that the domain server was unavailbale.
> Try
> again later. Unfortunately, the user doesn't remember his previous windows
> password so I can't even get to the workstation only.
> Any suggestions???? This is desparate.

At this point there is no way to check. Even if I restart in safe mode with
command, I still need to Logon locally.

"Robert L [MS-MVP]" wrote:

> sounds like dns issue. can you ping dns server by ip and name?
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more help.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> Networking Solutions, http://www.chicagotech.net/networksolutions.htm
> VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
> VPN Process and Error Analysis, http://www.chicagotech.net/VPN%20process.htm
> VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
> This posting is provided "AS IS" with no warranties.
> "Wizard52" <(E-Mail Removed)> wrote in message
> news:F5F58AC6-949B-46D6-A1C7-(E-Mail Removed)...
> > The last of 6 XP pro desktops has failed to authenticate with the newly
> > configured SBS 2003. Following the addition of users and computers to the
> > server, I ran the browser based connection utility
> > (http://server/connectcomputer) on this particular XP desktop. It went
> > thru
> > it's routine and rebooted. The new logon came up but would not accept the
> > new
> > ID and password. It kept saying that the domain server was unavailbale.
> > Try
> > again later. Unfortunately, the user doesn't remember his previous windows
> > password so I can't even get to the workstation only.
> > Any suggestions???? This is desparate.
>
>
>

"Wizard52" <(E-Mail Removed)> wrote in message
news:50D95464-C64C-4BC8-B67F-(E-Mail Removed)...
> At this point there is no way to check. Even if I restart in safe mode
> with
> command, I still need to Logon locally.
>
Use a password changing bootdisk. Set up DHCP to pass out the DNS server
before doing the disk though.

Matt

You need to logon to the local machine by choosing
options on the logon screen and changing the domain
name to the machine name. Use the built-in "administrator"
account.
"Wizard52" <(E-Mail Removed)> wrote in message news:
> At this point there is no way to check. Even if I restart in safe mode
with
> command, I still need to Logon locally.