Mike said:[snip] On the third computer, run the registry editor, open this key:
HLM\System\CurrentControlSet\Control\Lsa
and make sure that the DWORD value RestrictAnonymous is set to 0.
Reboot the third computer and try accessing it. If that doesn't fix
the problem, compare the registry values for "Lsa" on the third
computer to the values on an XP Home computer that shares
successfully.
I am having the same "access denied" issues. I am a little confused by the
instructions here. When I run "regedit.exe" I cannot see anything that looks
like the "HLM\System\CurrentControlSet\Control\Lsa" key mentioned. Am I
missing something obvious?
"HLM" is an abbreviation for "HKEY_LOCAL_MACHINE". The full path to
the registry key is:
My Computer\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
That did it. Wow, that is a pretty obscure fix! Too bad they don't have
that documented in the Windows "Help & Support"
Thanks a bunch for your assitance.
Mike
Steve Winograd said:Mike said:[snip] On the third computer, run the registry editor, open this key:
HLM\System\CurrentControlSet\Control\Lsa
and make sure that the DWORD value RestrictAnonymous is set to 0.
Reboot the third computer and try accessing it. If that doesn't fix
the problem, compare the registry values for "Lsa" on the third
computer to the values on an XP Home computer that shares
successfully.
I am having the same "access denied" issues. I am a little confused by the
instructions here. When I run "regedit.exe" I cannot see anything that looks
like the "HLM\System\CurrentControlSet\Control\Lsa" key mentioned. Am I
missing something obvious?
"HLM" is an abbreviation for "HKEY_LOCAL_MACHINE". The full path to
the registry key is:
My Computer\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
That did it. Wow, that is a pretty obscure fix! Too bad they don't have
that documented in the Windows "Help & Support"
Thanks a bunch for your assitance.
Mike
You're welcome, Mike. Yes, it's an obscure fix. I've found one
mention of it in the Microsoft Knowledge Base:
Error message when you try to access a Windows XP-based network
computer: "You might not have permission to use this network resource"
http://support.microsoft.com/kb/913628/en-us
This fix is specifically indicated when:
1. You can access a computer's shared folders directly (e.g. by typing
"\\computer\share" in the Start | Run box, or by mapping a network
drive), and:
2. You're denied permission when you try to get a list of all of the
computer's shared folders (e.g. by typing "\\computer" in the Start |
Run box, or by clicking the computer's icon in My Network Places |
"View workgroup computers").
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
Bob said:[snip] On the third computer, run the registry editor, open this key:
HLM\System\CurrentControlSet\Control\Lsa
and make sure that the DWORD value RestrictAnonymous is set to 0.
Reboot the third computer and try accessing it. If that doesn't fix
the problem, compare the registry values for "Lsa" on the third
computer to the values on an XP Home computer that shares
successfully.
I am having the same "access denied" issues. I am a little confused by the
instructions here. When I run "regedit.exe" I cannot see anything that looks
like the "HLM\System\CurrentControlSet\Control\Lsa" key mentioned. Am I
missing something obvious?
"HLM" is an abbreviation for "HKEY_LOCAL_MACHINE". The full path to
the registry key is:
My Computer\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
That did it. Wow, that is a pretty obscure fix! Too bad they don't have
that documented in the Windows "Help & Support"
Thanks a bunch for your assitance.
Mike
You're welcome, Mike. Yes, it's an obscure fix. I've found one
mention of it in the Microsoft Knowledge Base:
Error message when you try to access a Windows XP-based network
computer: "You might not have permission to use this network resource"
http://support.microsoft.com/kb/913628/en-us
This fix is specifically indicated when:
1. You can access a computer's shared folders directly (e.g. by typing
"\\computer\share" in the Start | Run box, or by mapping a network
drive), and:
2. You're denied permission when you try to get a list of all of the
computer's shared folders (e.g. by typing "\\computer" in the Start |
Run box, or by clicking the computer's icon in My Network Places |
"View workgroup computers").
This was the perfect set of solutions for me ... thanks Steve, you've saved
me tons of frustration !!!
Dave said:Steve,
I just wanted to let you know that I have also been grappling with this
issue for a week now and came across your post. I followed your instructions
and IT WORKED! This is awesome. It seems that I had tried everything...I
unistalled my Zone Alarm Firewall, I reset registers, re-ran network wizard
(it seems a hundred times) and nothing worked until I tried your commands.
Thanks for great assistance. I know it's probably not cut and dry but, what
can cause this to get hosed up to begin with? I run CA eTrust Anti-virus and
Zone Alarm firewall...I just can't understand how something could have
slipped through to mess me up. Any ideas so that I can prevent it from
happening again? Thanks again...and my wife thanks you as well (it was her
laptop that couldn't get to our networked printer).
Ed said:Steve,
I am getting the same logon failure message when my XP ties to access
the Vista (Vista can access XP though). I have made it down your check list
as far a running the resource kit on the XP. When I type the first command
line I get the message "yes" is not recognized as an internal or external
command, operable program or batch file. The other command lines were
accepted, but I still get the logon failure message. Suggestions?
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.