SBS2003 User Cannot Access companyweb or Network Shares After Password Change with Server Offline

We had this company's Dell PowerEdge 840 in for repair (PERC Card failed). While the server was offline, a user got a prompt to change his password (domain password policy), which he did. We put the server back in today and everything worked as expected with the other users. They were able to access shares, companyweb, etc. But this one user that changed his password while the server was offline, we cannot get him to connect to anything on the server. Tried changing the password from the server, from the client, nothing works. He can log into the domain with whatever the password is set to, BUT when he attempts to access a share or companyweb, he gets a login prompt and NOTHING we use there will get him access. Client OS is either XP or Win 7. Attempting to verify that now.

Additional config info: DHCP is being handled by the router, not SBS2003. DHCP delivers the server IP address as primary DNS and Google's public DNS server as secondary. This is so, with the server down, the IP phones and Internet browsing from the clients still works.
LVL 1
tcianfloneAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
SteveConnect With a Mentor Commented:
password resets are updated on the DC (PDC) but as the DC was not available at the time it's all gone wrong. I'm surprised it let them change the password without the DC in the first place!

try logging into webmail as the user to establish if the user account is screwed or not, and also to confirm exactly which password is currently active on the DC.

You probably best to remove the PC from the domain via a PC local administrator account, and then re add it.

This may reset accounts and force it to refresh the AD uses that can log on.
0
 
BlueComputeCommented:
DHCP is being handled by the router, not SBS2003. DHCP delivers the server IP address as primary DNS and Google's public DNS server as secondary.

I sense that you may know this, but this is not a supported configuration.  DHCP on SBS (so it knows where the computers are and can update DNS appropriately) and only the SBS svr configured as DNS svr is the supported config.
0
 
Larry Struckmeyer MVPCommented:
Agreeing that DHCP should be on the SBS.  adding that all the nics in all the systems should point to the SBS for DNS and in the DNS app on the SBS you use the ISP DNS servers, (or other known good DNS servers) as forwarders.  The CEICW wizard fixes all that for you after you turn off DHCP on the router.

It the SBS is off line then you can turn on the DHCP server on the router, turning it off again when the SBS comes back on line.

As for your current condition, sounds like the user is out of sync in AD.  There are probably solutions to all of this but I would most like export his OST to pst, verify that as the admin I could move his redirected documents to a safe place, then remove the user, create a new one, import the mail and put the documents back in his My Documents folder.  They will redirect if that policy is in place.  Should be less complicated than messing with the AD.

You can read more about tombstoned objects here:

http://windowsitpro.com/windows-server-2003/ad-tombstone-objects
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
tcianfloneAuthor Commented:
Yes, I know about the recommended SBS configuration regarding DHCP services. I inherited this site and all the while it has been running fine with the non-recommended config, i.e., the router running DHCP. I checked the DNS records for the PC's today, including the problem PC. The DNS records are up to date, meaning they have the correct IP addresses. The client can ping the SBS by short name and fqdn, and vice versa. The login from the problem PC works fine as well, the password change is being registered by the DC.

I tried creating another account for this user, logged into it, and then I could access the SBS shares no problem. BUT, I still could NOT access the companyweb site!!! Got the login prompt for that and could not connect no matter what I tried from that prompt. Why would the DC authenticate me for login, shares, but NOT the companyweb???
0
 
SteveCommented:
as advised above, just remove the PC from the domain. chuck in a reboot and re add it. this should reset its security cache etc.
0
 
tcianfloneAuthor Commented:
The plan is to rebuild the client machine from scratch because there are a lot of other issues with it. Once I do that then rejoin it to the domain, I will report back with results and close the question. Thanks.
0
 
SteveCommented:
If the PC has issues anyway then rebuilding certainly isnt a bad idea.
rebuilding it will also work as the security cache will be created from scratch anyway.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.