Log In Error
mmonnin
Centreville, VA
Damn I hate XP. I cant connect to any XP machines on my network. Same Domain, MSHOME. 2k machines I can connect to but if I try to connect to any XP machines from any other machine I get this attached error.
I used to know how to get around it but I cant remember. And I am not going to make more user accounts on all the machines for each other computer. I want to be able to Log into each computer using the account that is currently logged in.
All the computers have a default user name of either Marc or Marc Monnin with no password. I dont want to give passwords and have them autologin either.
I should be able to type in "Marc Monnin" with no password to log into each computer but I get this error.
I used to know how to get around it but I cant remember. And I am not going to make more user accounts on all the machines for each other computer. I want to be able to Log into each computer using the account that is currently logged in.
All the computers have a default user name of either Marc or Marc Monnin with no password. I dont want to give passwords and have them autologin either.
I should be able to type in "Marc Monnin" with no password to log into each computer but I get this error.
0
Comments
There are a few ways to do this.
Depending on what you're most comfortable with, I'd say there are two *best* ways to proceed.
1.) Cheesy way, try not to do this: Grab an XP install media, do a repair installation over your current windows install... May work, may not.
2.) Best way, head over to http://www.knoppix-std.org/ and grab a copy of Knoppix - STD. Read in their newbies forum about how to mount an NTFS formatted drive using the capture command (or read the man page). Then use the chntpw command, and just set your Windows Administrator password to whatever. Then at the logon to WinXP, if it does random bull to you again, just hit crtl+alt+del at the handy little graphical login, and log in as a nice full administrator account, with a non-null password.
So, to recap, if you know Linux, or can at least get around in a bash shell, do that. Else.... learn to do that
I want to connect to XP machines from other machines on the network. Say I share a folder an on XP machine and then want to view the contents of the folder by finding it in "Computers Near Me." When the log in prompt comes up and I try to log into the computer using the default ID I get the above error. If I log in the same way into a 2k machine I can see the shared folders and stuff but not on XP machines.
One thing you can try quickly and easily is connecting to the Windows Admin default share \\ComputerName\c$ where c is the drive name (for instance, that's for C:\)
If you can connect that way, why not just make a drive map to there, to avoid the joys of MSHome/MSWorkgroup idiosyncracies?
And I need to be able to acces shared folders. I want to be able to share FAH folders so I can monitor their progress across the network?
Seriously what is up with this damn thing.
Oh and I cant share my printer either without this working,
Also, are the 'Full Computer Name' in system properties of the XP machines different? Because they need to be.
-Go to My Computer
-Under 'other places' click 'My Network Places'
-Click 'View workgroup computers'
You should see the available computers on your network. Go into the computer where you made a shared folder to see if it is there.
Are these wireless or wired? Have you run the Network Setup Wizard in control panel?
All admins.
I dont have passwords on 2k machines and i dont get this crap.
2K allows for null\blank PWs, XP with security packs does NOT allow for that when sharing data from machine to machine. Your XP boxes need PWs for networking if you security packed them.
Marc, try going to Administrative Tools>>Local Security Policy>>Local Policies>>Security Options, then go through the stuff in there and see if you can spot anything.
You could also try Internet Options>>Security; highlight Local Intranet, pick Custom Level, then check out the logon settings at the bottom.
I wish I could remember more about it, but a couple years ago I had the same problem - in reverse. It was the Win2K machines locking me out and the WinXP computers which played nice.
prof: I will take a look at some of that later on. Thanks.