Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I have a Windows 2003 server for several months (upgraded from W2K server) and the past few days on a client PC with Windows XP (in a workgroup) I cannot open any shared folder unless I type a user and psw... This didn't happen earlier!! Is there something that can bfix this? :(
So you have a domain running on the Win2k3 server?
If so, I have the same problem, but as soon as you have made one connection using a certain username and password, those credentials will be remembered and used each time you access the domain.Sorry I couldnt be more helpful
Rob
0 
Nope, just a workgroup!!!! Each time this client restarts I have to put a user and psw to access a folder or shared printer!!:(
Anthony
0
Create user accounts on the target machine for any/all users that will be connecting. Use the user's username/password (whew...one too many "use"'s in there) when creating the account(s). Once you've created the account(s), add it (them) to the shared folders/printers etc.
0
That's what I had already done (running flawlessly for the past few months)... Suddenly it stopped working just for one user!! I deleted this user from the server and created him again.. Still nothing!!:( Anything else I should check?
0
I had a very identicle problem with a win2k domain. I had users on workgroups with xpHome and also users on the domain. Both started (out of no where) to loose their share permissions. I'd reset everything and it'd work for the domain users but not the workgroup users. Finally I replaced a switch on the network and the problem went away. I know this is probably a 80% chance it's not your problem but you may want to have a look. If a switch drops the client for even a second the server may timeout the users credentials.
Another thing you can try is give them a batch file that uses net use...
net use \\servername\sharename /USER:domainname\username /PERSISTAENT:YESyou can also increase the idle timeout time of the server by using this...
net config server /autodisconnect:number
number can be anywhere from 1 - 65535
if you want idle disconnect turned off use "-1" as the value
0
You mean I should write to "run" from the server this: "\\servername\sharename /USER:domainname\username /PERSISTAENT:YES" ??
I will try another switch too!!:(
0
Is the user on a new computer?
I have seen this where a new computer had been setup on original Administrative account and a proper user account had never been created. The solution suggested above only works if a proper user account has been created (limited or admin level, doesn't matter).
A way to prove it would be setup a new account on the offending computer and see if THAT account can access the server files. If so, rename the account and copy over thier desktop and files etc..
Work Smart, not hard!
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
