Laptop logon problem

[pelkins]

I have a user w/ an xp pro laptop logging on to a 2003 SBS server. When User tries to logon on with domain credetials I get domain not available or no computer account logon error message. However when i use a local logon on account I can see the PC getting correct IP/DNS info and I can use the network. If I unplug the pc from the network then logon with domain credentials and plug the network in after logon everything seems to work fine. User account works fine from his desktop. Windows firewall is disabled via group policy. I tried changing the computer name and making new computer account on server. Same result. This machine was working previously in this fashino w/ no problems.

I am stumped.

Thanks in advance.

 

[bcastner]

See the general advice, and last paragraph in particular in faq779-4017

This is usually a DNS issue, as described in the FAQ, but the fast logon optomization for stand-alone clients should be disabled.

 

[pelkins]

Thanks for the response. I am familiar with that article and have dealt with the slow logon issue. This account works just fine from the users desktop, no slow logon. DNS looks good and works for everyone else. the machine is pulling correct IP and DNS from the server. The error message pops up immediatly after you click to logon. It doesnt even think. It is almost as though some service isnt functioning or some protocol is being blocked. I tried reloading client for microsoft networks w/ no luck.

It is most likely something stupid I am missing.

 

[bcastner]

Both wired and wireless adapters on that laptop?
Disable (not uninstall) the unused adapter through Device Manager.

Also, most adapter OEMs have release post SP2 adapter driver versions. Be current on the drivers.

 

[pelkins]

Good thoughts. I will let you know.

 

[pelkins]

I tried those suggestions to no avail. I noticed that in the server system log I am getting event ID 5277

The session setup from the computer PAPERGLAPTOP failed to authenticate. The name(s) of the account(s) referenced in the security database is PAPERGLAPTOP$. The following error occurred:
Access is denied.

Microsoft has a bulletin out about this an recomends that you reset the computer account to clear the problem. I tried this and no luck. Maybe I need to rejoin the domain.

If anyone has run into this please help. This is getting old quick.

 

[SimonDavies]

As you aren't having much luck with this at the moment here is something to try, have you looked at the computer account to see if it's either disabled or locked?
If neither then I would simply suggest joining a workgroup and rejoining the domain to see if that resolves the issue. Make sure that the account you use to join the domain can actually add workstations to the domain if you haven't deleted and recreated the old computer account.

 

[pelkins]

Thanks for the response.The computer account is not disabled or locked. I am able to diable, enable and reset the computer account on the server with no errors. I will try rejoining the domain and let you know. I cnat get to it until this pm or maybe monday.

thanks again

 

[bcastner]

Let me return to an earlier suggestion.

What you can do is set a local policy to force the
machine to wait for the network before presenting a login
prompt. You can leave the same GPO setting on the domain, but test by setting it locally as well:

Run gpedit.msc and browse to Computer Configuration -->
Administrative Templates --> System --> Logon and set the
policy that says "Always wait for the network at computer
startup and logon".

The fact that you can authenticate with cached credentials, but not "live" suggests that the networking fundamentals are not yet ready at the time the logon prompt is presented.

For some reason this has become a new issue with recent laptops that use either Intel or Broadcomm wireless chipsets, in addition to having a "wired" connection. It is my belief it is due to the option to "team" or "bond" the wireless and wired connections, and this feature should be disabled.

In a related vein, Microsoft is currently recommending disabling the teaming of adapters on Windows servers with NLB enabled until driver issues are sorted or all other network issues are resolved:

http://support.microsoft.com/kb/278431/

 

[pelkins]

It turned out that simply rejoining the Domain cleared the problem. I dont know why renaming and rejoing the computer didnt work the first time but all is well now. By the way I did reset the computer account after I pulled the machine from the domain. Maybe that was the Key.

Thanks for the responses.