stolenpants
MIS
Last night scheduled updates were applied to a 2003 x64 R2 server. This may or may not be the cause of the problem.
The symptoms are very specific.
If you try to access a \\server\share from a computer that is not a member of the domain (my XP laptop, home computer over VPN, and two other users who are on apple OSX) it won't accept the username - password.
If you try to access the same \\server\share from an XP computer that IS a member of the domain, with the same user name, it works.
With regard to the computers that are not on the windows domain: You can ping the server successfully, and you can log into exchange 2007 through outlook with the same username and password that is rejected when you try to connect to a UNC share.
Because the problem is so specific, I'm guessing there's a single registry key or policy object that has to be changed but for the life of me I can't figure it out mostly because it doesn't give me an error message to google, it just keeps prompting for a password.
The symptoms are very specific.
If you try to access a \\server\share from a computer that is not a member of the domain (my XP laptop, home computer over VPN, and two other users who are on apple OSX) it won't accept the username - password.
If you try to access the same \\server\share from an XP computer that IS a member of the domain, with the same user name, it works.
With regard to the computers that are not on the windows domain: You can ping the server successfully, and you can log into exchange 2007 through outlook with the same username and password that is rejected when you try to connect to a UNC share.
Because the problem is so specific, I'm guessing there's a single registry key or policy object that has to be changed but for the life of me I can't figure it out mostly because it doesn't give me an error message to google, it just keeps prompting for a password.
