when i try to access one windows xp machine from another xp machine (both pro version), i get the following error.
http://btfh.net/error.jpg
the network we are on is a simple one, no domain controller, workgroup set to workgroup. We've tried turning guest accounts on, turning them off, etc.......any suggestions?
Page 1 of 1
wierd error with file sharing /user authentication
#2
Posted 24 March 2002 - 10:41 PM
It is recommended that you do not use the guest account. Instead you should create user accounts on both machines with the same user/pass as the other machine's logged in user and grant them access to the shared folders.
If you're still going to use the guest account then check this:
[list=1]
[*]Go to Start -> Run
[*]Enter "secpol.msc"
[*]Go to Local Policies -> User Rights Assignment
[*]Double-click on "Deny access to this computer from the network"
[*]Remove the guest account if it's in there.
[/list=1]
If you're still going to use the guest account then check this:
[list=1]
[*]Go to Start -> Run
[*]Enter "secpol.msc"
[*]Go to Local Policies -> User Rights Assignment
[*]Double-click on "Deny access to this computer from the network"
[*]Remove the guest account if it's in there.
[/list=1]
#3
Posted 24 March 2002 - 11:07 PM
In WinXP clients are forced to use the Guest account to logon when you are in a workgroup.
If you disable the Guest account as Xiven said (I also recommend you do this) you need to turn off the forceguest feature like this:
1. Go to Start --> Run
2. Enter secpol.msc
3. Go to Local Policies -> Security Options
4. Double-click on "Network Access: Sharing and security model for local accounts"
5. Change the setting to "Classic"
If you disable the Guest account as Xiven said (I also recommend you do this) you need to turn off the forceguest feature like this:
1. Go to Start --> Run
2. Enter secpol.msc
3. Go to Local Policies -> Security Options
4. Double-click on "Network Access: Sharing and security model for local accounts"
5. Change the setting to "Classic"
#4
Posted 24 March 2002 - 11:29 PM
thank you for the hint regarding secpol.msc. As it turns out, the problem was a new policy inside there that was introduced by another program i believe. The network now performs as desired
Share this topic:
Page 1 of 1

Help










