I am running Windows Server 2003 as a domain controller and a file server. When I run a Windows XP client I have no problem logging in on the domain. However, when I try to access the file server I get the "Connect to (Fileserver)" prompt which asks for User Name and Password. The problem is that when I type the user name and password I get the following error: "Logon Unsuccessful: The user name you typed is the same as the user name you logged in with. That user name has already been tried. A domain controller cannot be found to verify that user name." OK, well this just states the obvious. The user I logged in with does have read and write permissions under the group /user. The weirdest part is that I can log onto the file server using any other member of /user. To clarify: I can log onto windows using USER_A. If I try to access the file server using USER_A 's user name and password I get the above error. If I enter USER_B 's user name and password at the above prompt, no problems. Now, if I login as USER_B to windows, I cannot access the file server; I get the same error. But if I now enter USER_A 's user name and password I can log in!!!!! I don't get it. Anyone have any idea what the problem is?

What happens when you logon as administrator? Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

I have the same problem when I log on as an Administrator (on the Domain). I have not tried to log on as the Administrator for that specific computer but I don't see how that could help. Any suggestions?

You have the same issue on the server as admin?!? When did this start? Someone change a group policy? How long have you had this server up? Any new software installs? Give a person a fish you feed them for a day. Ask a person to internet search and they learn a skill for a lifetime.

I get the same error (under your same A/B scenario). I suspect perhaps the pc is letting UserA logon locally (although NOT connected to the domain yet - lets say offsite/pre-vpn connection or pre-wifi connection). I say "local" but it is a "pseudo local" since the profile, username, and domain password are all used as if UserA is actually logging into the domain (but clearly UserA is NOT connected to any network). After UserA connects to a network (using wifi or vpn), UserA is still logged in locally and any attempts to access a share on the server would be using "local" creds, hence the prompt "logon unsuccessful"??? I don't have facts to back this theory up but it's the only logical conclusion I can come up with. I'm running XP Pro clients and SBS2003. I wonder if a domain policy is pushed to the client and stays there even while not connected to the domain?

I think I found the fix for this. It appears there is no network connection at logon (CNTL ALT DEL) but then after logging in, a connection is made to the domain. Simply map a drive (manually) to the share or use this script (VBS file extension). Dim objShell,objNetwork Set objShell = WScript.CreateObject("Wscript.Shell") Set objNetwork = WScript.CreateObject("WScript.Network") '<--- put this up one line objNetwork.MapNetworkDrive "S:", _ "\\server_name\share_name", _ "False", "domain-name\username", "password" objShell.Popup "Success!", 3, "Success", 0