Posts: 16
Threads: 4
Joined: Sep 2010
Reputation:
0
Windows XP SP2 system doesn't remember network share passwords, every time i reboot the system have to enter password again.
- Checked on remember password check-box. Still it doesn't remember.
- Mapped drive also never connects even if check marked on Reconnect at logon option.
- Firewall is disabled.
Stored Users names and passwords from Control Panel> Users Account> Username> Manage my network passwords always remains empty even if i make manual entry in it.
Any ideas??
Posts: 221
Threads: 15
Joined: Aug 2010
Reputation:
8
09-21-2010, 03:25 PM
(This post was last modified: 09-21-2010, 03:25 PM by Brandon.)
This isn't exactly possible. What your only solutions are is to either remove the passwords, or create a login account on the network share computer with the same credentials as the one on your XP computer.
Good luck.
Posts: 16
Threads: 4
Joined: Sep 2010
Reputation:
0
All system are on workgroup environment.
or create a login account on the network share computer with the same credentials as the one on your XP computer.
^^
This should not be done ideally write? Because on all other systems it works fine.
Posts: 221
Threads: 15
Joined: Aug 2010
Reputation:
8
09-24-2010, 12:24 AM
(This post was last modified: 09-24-2010, 12:25 AM by Brandon.)
Ah, since you are using group policy on a workgroup environment, you have to change the policy on ALL computers instead of just one using a domain controller in a domain environment.
If that doesn't mean anything to you, I'm slightly confused as well on what you are aiming to do. Are you attempting to go through with my second option?
Please go into detail with what created that popup and what you are exactly trying to change.
Posts: 16
Threads: 4
Joined: Sep 2010
Reputation:
0
No we don't have any group policy, its default on all systems.
I just saying that whenever i Goto> Group Policy > Security settings or click on any options in it gives above message box i don't understand why is that. Ideally on all other systems it doesn't happens.
Posts: 221
Threads: 15
Joined: Aug 2010
Reputation:
8
Your local security policy database is definitely corrupted then. What I'd recommend is that you back it up, then repair it. You can repair it using the esentutl /p command from the cmd prompt.
So, open up a cmd prompt and type esentutl /p %windir%\security\database\secedit.sdb
That utility should repair your database and set you up properly. Then you can proceed with what you are attempting to try.
Posts: 16
Threads: 4
Joined: Sep 2010
Reputation:
0
Hmm that might be the case, i'll try that.