PDA

View Full Version : Changing user name / password for LAN file sharing


levenum
19-07-2006, 01:42 PM
Hi everybody!
I have a little problem. I've set up a home network with a wireless router. I shared some folders on my PC so I can access the files from my Jamin.
So far so good, I managed to access the folders from PIE.
The problems started when I wanted to change user name and password. When I enter a network path PIE pops up a screen asking for user, password and domain. I made the mistake of checking 'remember password' box and now I can't get to this screen again so I can't change the login and access shares on my company network.

So how do I get explorer to ask for a password again? (without doing hard reset)
Or is there an app to manage this thing? I tried pocketLAN but it doesn't have this option.

Thanks in advance.

xdaradar
03-08-2006, 08:26 PM
have yoy tried to look in the registry for key's about this?

had the same problem on accessing a website.

using regedit i found an entry in registry with the userid, deleted that entry and the next time i was asked for the password again.

hope this helpes

levenum
03-08-2006, 09:56 PM
Actually, this is the first thing I tried.
Looked for the user name, then for computer name but all I got was the AS regs.
Maybe it was me, or the PHM reg edit.
Ether way, I solved it by changing the password, but if you fined that key again some time I would appreciate the info, and maybe someone else will two.
At least I learned my lesson: Never ever ever click the 'remember password box' darn M$. :x

Thank for the reply though.

xdaradar
04-08-2006, 11:56 PM
i did a find of a userid which i used and found it in registry via the find options and a search in the entire registry.

it was found in HKCU\Software\Microsoft\Activesync\Partners\.....

maybe this helpes?

levenum
06-08-2006, 09:48 AM
Thanks for the effort, but this just kill the partnership to the PC. (Yep, tried it and was sorry).
So far changing the password seems to be the only solution (there are a couple more threads on similar issues).
Looks like another MS screw up.