XP networking problem.

[iamtrout]

I'm on my dorm's network and I can't seem to connect to my laptop from my desktop. Both have SP2 and are on MSHOME. Whenever I try to access my lappy from the "workgroup computers" window I get a screen that asks for a username and password. The problem is that I've never specified a password for my lappy before, and its admin account doesn't have a password... and never has. The admin account username of the lappy is "Admin" and when I type in "Admin" with the password box empty XP says I don't have permission to access my own laptop.

What's going on? I have printer and file sharing on.

 

[KarenMarie]

Try this:
[Start] [Run] and type gpedit.msc and click [OK]
Navigate to Computer Configuration / Windows Settings / Security Settings / Local Policies / Security Options
Double click on Accounts: Limit local account use of blank passwords to console login only.
Select the radio button next to Disabled and click [OK]

Keep a note of these instructions... if it doesn't work, or if there is a problem... you will need to know how to undo it.

Let me know if this works.

🙂

 

[JeffMD]

of course.. only an idiot would DO this as your dorm would then have free access to your laptop. ^^ Set up a password for the admin account instead.

 

[KarenMarie]

My telling him to do that was a temporary measure, so he could access the inernet. From there, well... there are loads of software programs that would give him access to his password.

It was not meant to be a permanent solution. Perhaps I should have been more clear on that.

 

[iamtrout]

I tried it and now when I try to access my lappy from my desktop I get

"//RSM is not accessible etc....
Logon failure: the user has not been granted the requested logon type at this computer."

Thanks for all the help so far!

 

[iamtrout]

Nevermind. I turned off guest accounts and I no longer get the above error message. I still get a login screen, but if I type Administrator into the box with no password it lets me in. But I've never had to do this before. It was working perfectly fine during a LAN that I had a week ago...