Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Logon Failure: the user has not been granted the requested logon t

29 views
Skip to first unread message

H@discussions.microsoft.com Todd H

unread,
Sep 12, 2005, 12:35:04 PM9/12/05
to
I am running a wireless network on WinXP Home w/SP2 (installed on all
computers). Since installing SP2, we are having trouble sharing files on one
of the networked computers (the other two work fine). Specifically, a)
shared folders and files on this computer do not appear in My Network Places,
and b) although we can view the workgroup computer in My Network Places, when
we try to access it, we get the error message: "Logon failure: the user has
not been granted the requested logon type at this computer."

Please help.......Todd

Steve Winograd [MVP]

unread,
Sep 12, 2005, 1:51:41 PM9/12/05
to
In article <779BC177-208A-4EF6...@microsoft.com>, Todd

The problem and the solution are on the XP Home computer that can't be
accessed. Run XP's Network Setup Wizard on that computer -- that's
sometimes all that's needed. If that doesn't fix the problem:

1. Download and install the Windows 2003 Server Resource Kit Tools
from http://go.microsoft.com/fwlink/?LinkId=4544 .

2. Click Start | All Programs | Windows Resource Kit Tools | Command
Shell.

3. Type these lines at the command prompt. The second and third
commands are case-sensitive, so type them exactly as shown. Note the
"+r" in the second one and the "-r" in the third one:

net user guest /active:yes
ntrights +r SeNetworkLogonRight -u Guest
ntrights -r SeDenyNetworkLogonRight -u Guest
--
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

Todd H

unread,
Sep 12, 2005, 2:49:04 PM9/12/05
to
Steve: The Network Setup Wizard did not fix the problem but the Windows 2003
Server Resource Kit Tools did the trick. Thanks for the help!

Todd

Steve Winograd [MVP]

unread,
Sep 12, 2005, 3:10:34 PM9/12/05
to
In article <235C3891-BEA5-4A1B...@microsoft.com>, Todd

H <To...@discussions.microsoft.com> wrote:
>> >I am running a wireless network on WinXP Home w/SP2 (installed on all
>> >computers). Since installing SP2, we are having trouble sharing files on one
>> >of the networked computers (the other two work fine). Specifically, a)
>> >shared folders and files on this computer do not appear in My Network Places,
>> >and b) although we can view the workgroup computer in My Network Places, when
>> >we try to access it, we get the error message: "Logon failure: the user has
>> >not been granted the requested logon type at this computer."
>> >
>> >Please help.......Todd
>>
>> The problem and the solution are on the XP Home computer that can't be
>> accessed. Run XP's Network Setup Wizard on that computer -- that's
>> sometimes all that's needed. If that doesn't fix the problem:
>>
>> 1. Download and install the Windows 2003 Server Resource Kit Tools
>> from http://go.microsoft.com/fwlink/?LinkId=4544 .
>>
>> 2. Click Start | All Programs | Windows Resource Kit Tools | Command
>> Shell.
>>
>> 3. Type these lines at the command prompt. The second and third
>> commands are case-sensitive, so type them exactly as shown. Note the
>> "+r" in the second one and the "-r" in the third one:
>>
>> net user guest /active:yes
>> ntrights +r SeNetworkLogonRight -u Guest
>> ntrights -r SeDenyNetworkLogonRight -u Guest
>
>Steve: The Network Setup Wizard did not fix the problem but the Windows 2003
>Server Resource Kit Tools did the trick. Thanks for the help!
>
>Todd

You're welcome, Todd. I'm glad that it worked for you. Thanks for
the report.

Boopa@discussions.microsoft.com Big Boopa

unread,
Jan 6, 2006, 9:33:02 PM1/6/06
to
Mike B

I have the same problem as Tod H, with 2 wireless computers unable to access
a third computer wired to a router, even though that computer can be seen in
workgroup computers. I get the message "Logon failure:the user has not been
granted the requested logon type at this computer." I used the solution from
Steve, by downloading the 2003 Server Resourse Kit Tools, and entering the
required text. Now I get an "Access is denied" message. Any suggetions.

Steve Winograd [MVP]

unread,
Jan 6, 2006, 10:13:07 PM1/6/06
to
In article <A38A78F3-69F2-40D1...@microsoft.com>, Big
>Mike B
>
>I have the same problem as Tod H, with 2 wireless computers unable to access
>a third computer wired to a router, even though that computer can be seen in
>workgroup computers. I get the message "Logon failure:the user has not been
>granted the requested logon type at this computer." I used the solution from
>Steve, by downloading the 2003 Server Resourse Kit Tools, and entering the
>required text. Now I get an "Access is denied" message. Any suggetions.

Run the Network Setup Wizard on the third computer and see if that
solves the problem.

If it doesn't, please reply to this message in the news group (not by
E-mail) with more information to help other people understand the
problem:

1. Does the third computer run XP Home Edition or XP Professional?

2. If it runs XP Professional, is simple file sharing enabled or
disabled?

Big Boopa

unread,
Jan 8, 2006, 9:13:02 AM1/8/06
to
Steve, the 3rd computer (the one that will not share files) is running XP
Home. One of the wireless computers is running XP Pro, but that one does not
seem to have any problem sharing files. The original error message (about
logon type) had "Windows Explorer" written in the title bar, however the new
message has the workgroup name written in the title bar. The message itself
refers to the computer that will not share files. I don't know whether this
is helpful or not. I'm thinking of running the network wizard again on the
problematic computer, and if that is not successful, repeating the 3 steps
from the Server Resource Kit.

Steve Winograd [MVP]

unread,
Jan 8, 2006, 2:19:47 PM1/8/06
to
In article <913D679F-4229-4909...@microsoft.com>, Big
>Steve, the 3rd computer (the one that will not share files) is running XP
>Home. One of the wireless computers is running XP Pro, but that one does not
>seem to have any problem sharing files. The original error message (about
>logon type) had "Windows Explorer" written in the title bar, however the new
>message has the workgroup name written in the title bar. The message itself
>refers to the computer that will not share files. I don't know whether this
>is helpful or not. I'm thinking of running the network wizard again on the
>problematic computer, and if that is not successful, repeating the 3 steps
>from the Server Resource Kit.

Running the Network Setup Wizard on third computer might help. I
don't think that repeating the steps from the Server Resource Kit will
help -- they're specifically designed to solve the "Login failure"
problem, and you've already done that.

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.

Big Boopa

unread,
Jan 10, 2006, 8:13:03 AM1/10/06
to
Steve; I ran the registry editor and found that the DWORD value
RestrictAnonymous was set to 1. I have not attempted to change the value yet.
I assume that I would simply change the present value 0x00000001 (1) to
0x00000000 (0) by typing over it.

Thanks, Mike

Hans-Georg Michna

unread,
Jan 10, 2006, 8:59:11 AM1/10/06
to
On Tue, 10 Jan 2006 05:13:03 -0800, Big Boopa wrote:

>Steve; I ran the registry editor and found that the DWORD value
>RestrictAnonymous was set to 1. I have not attempted to change the value yet.
>I assume that I would simply change the present value 0x00000001 (1) to
>0x00000000 (0) by typing over it.

Mike,

yes, that is correct. (Stepping in for Steve temporarily.)

Hans-Georg

--
No mail, please.

Big Boopa

unread,
Jan 10, 2006, 5:01:02 PM1/10/06
to
Steve and Hans, I changed the value using the registry editor and it worked.
I am no able to share files and printers from this computer. THANKS, GREAT
JOB!
Mike

Steve Winograd [MVP]

unread,
Jan 10, 2006, 5:42:55 PM1/10/06
to
In article <6A34F6CB-5616-43F9...@microsoft.com>, Big

Boopa <BigB...@discussions.microsoft.com> wrote:
>>>>>Steve, the 3rd computer (the one that will not share files) is running XP
>>>>>Home. One of the wireless computers is running XP Pro, but that one does not
>>>>>seem to have any problem sharing files. The original error message (about
>>>>>logon type) had "Windows Explorer" written in the title bar, however the new
>>>>>message has the workgroup name written in the title bar. The message itself
>>>>>refers to the computer that will not share files. I don't know whether this
>>>>>is helpful or not. I'm thinking of running the network wizard again on the
>>>>>problematic computer, and if that is not successful, repeating the 3 steps
>>>>>from the Server Resource Kit.
>>>>
>>>>Running the Network Setup Wizard on third computer might help. I
>>>>don't think that repeating the steps from the Server Resource Kit will
>>>>help -- they're specifically designed to solve the "Login failure"
>>>>problem, and you've already done that.
>>>>
>>>>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.
>
>> >Steve; I ran the registry editor and found that the DWORD value
>> >RestrictAnonymous was set to 1. I have not attempted to change the value yet.
>> >I assume that I would simply change the present value 0x00000001 (1) to
>> >0x00000000 (0) by typing over it.
>>
>> Mike,
>>
>> yes, that is correct. (Stepping in for Steve temporarily.)
>>
>> Hans-Georg
>
>Steve and Hans, I changed the value using the registry editor and it worked.
>I am no able to share files and printers from this computer. THANKS, GREAT
>JOB!
>Mike

You're welcome, Mike. Thanks for reporting the result.

HarlyRidnLady4

unread,
Jan 30, 2006, 11:26:28 AM1/30/06
to
And i have the same problem also but cannot fnd the shell command prompt in
the Windows Resource Kit please be more specific for me
Linda
lwm...@alltel.net
HELP ME PLEASE

HarlyRidnLady4

unread,
Jan 30, 2006, 11:37:26 AM1/30/06
to
ok found the darn command shell used copy paste to do commands everything was
successful. you game no other instructions ok i did that for the guest but
should my own account work????

HarlyRidnLady4

unread,
Jan 30, 2006, 11:46:03 AM1/30/06
to
OMG STEVE it WORKED OMG OMG OMG I'M SO ETERNALLY GRATEFULL TO YOU. i was on
the phone for almost 20 hours with ms support and they couldnt do this omg
wow wow 3 weekssssssssssss i've been trying to get this to work omg omg
roflmao wow wow wow ty tytytytytytytytytytytytytytytytytytytytytytytytyty
I'M IN SHOCK
I LOVE YOU
LINDA

Steve Winograd [MVP]

unread,
Jan 30, 2006, 3:33:23 PM1/30/06
to
In article <A4BFC866-A99F-4254...@microsoft.com>,
>OMG STEVE it WORKED OMG OMG OMG I'M SO ETERNALLY GRATEFULL TO YOU. i was on
>the phone for almost 20 hours with ms support and they couldnt do this omg
>wow wow 3 weekssssssssssss i've been trying to get this to work omg omg
>roflmao wow wow wow ty tytytytytytytytytytytytytytytytytytytytytytytytyty
>I'M IN SHOCK
>I LOVE YOU
>LINDA

You're welcome, Linda! I'm glad to help.

Please send an E-mail to my wife and tell her that I actually do
something useful on the computer in the rare moments that I'm not
playing Hearts. :-)

Lynn Gobin

unread,
Jun 18, 2006, 7:40:02 PM6/18/06
to
Linda said she loved you. I won't go quite so far as to say that, but trust
that I am extremely grateful for your advice. This same problem has dogged me
for months. These three short commands through the Server Resource Kit did
the trick. Thanks!
--
Lynn Gobin

Steve Winograd [MVP]

unread,
Jun 18, 2006, 8:09:54 PM6/18/06
to
In article <07B57CE2-D8AD-4E23...@microsoft.com>, Lynn

Gobin <Lynn...@discussions.microsoft.com> wrote:
>"Steve Winograd [MVP]" wrote:
>>
>> 1. Download and install the Windows 2003 Server Resource Kit Tools
>> from http://go.microsoft.com/fwlink/?LinkId=4544 . >>
>> 2. Click Start | All Programs | Windows Resource Kit Tools | Command
>> Shell.
>>
>> 3. Type these lines at the command prompt. The second and third
>> commands are case-sensitive, so type them exactly as shown. Note the
>> "+r" in the second one and the "-r" in the third one:
>>
>> net user guest /active:yes
>> ntrights +r SeNetworkLogonRight -u Guest
>> ntrights -r SeDenyNetworkLogonRight -u Guest

>Linda said she loved you. I won't go quite so far as to say that, but trust

>that I am extremely grateful for your advice. This same problem has dogged me
>for months. These three short commands through the Server Resource Kit did
>the trick. Thanks!

You're welcome, Lynn. :-)

Mike

unread,
Jun 21, 2006, 12:32:02 AM6/21/06
to
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?

Steve Winograd [MVP]

unread,
Jun 21, 2006, 12:43:30 AM6/21/06
to
In article <1E6CA5EC-340B-4E56...@microsoft.com>, Mike
>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

Mike

unread,
Jun 21, 2006, 9:22:01 PM6/21/06
to
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 [MVP]

unread,
Jun 21, 2006, 11:52:53 PM6/21/06
to
In article <DA040419-3B0B-460A...@microsoft.com>, Mike
<Mi...@discussions.microsoft.com> wrote:
>> >> [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").

Message has been deleted

Bob

unread,
Aug 27, 2006, 4:29:01 PM8/27/06
to
This was the perfect set of solutions for me ... thanks Steve, you've saved
me tons of frustration !!!

Steve Winograd [MVP]

unread,
Aug 31, 2006, 12:20:18 PM8/31/06
to
In article <85A0F962-81B2-4E32...@microsoft.com>, Bob
>This was the perfect set of solutions for me ... thanks Steve, you've saved
>me tons of frustration !!!

You're welcome, Bob!!!

L.@discussions.microsoft.com Dave L.

unread,
Nov 30, 2006, 2:50:00 AM11/30/06
to
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).

Dave L.

Steve Winograd [MVP]

unread,
Nov 30, 2006, 9:04:08 PM11/30/06
to
In article <BF0E9A8B-6044-4CCF...@microsoft.com>, Dave

L. <Dave L.@discussions.microsoft.com> wrote:
>>> >I am running a wireless network on WinXP Home w/SP2 (installed on all
>>> >computers). Since installing SP2, we are having trouble sharing files on one
>>> >of the networked computers (the other two work fine). Specifically, a)
>>> >shared folders and files on this computer do not appear in My Network Places,
>>> >and b) although we can view the workgroup computer in My Network Places, when
>>> >we try to access it, we get the error message: "Logon failure: the user has
>>> >not been granted the requested logon type at this computer."
>>>
>>> The problem and the solution are on the XP Home computer that can't be
>>> accessed. Run XP's Network Setup Wizard on that computer -- that's
>>> sometimes all that's needed. If that doesn't fix the problem:
>>>
>>> 1. Download and install the Windows 2003 Server Resource Kit Tools
>>> from http://go.microsoft.com/fwlink/?LinkId=4544 .
>>>
>>> 2. Click Start | All Programs | Windows Resource Kit Tools | Command
>>> Shell.
>>>
>>> 3. Type these lines at the command prompt. The second and third
>>> commands are case-sensitive, so type them exactly as shown. Note the
>>> "+r" in the second one and the "-r" in the third one:
>>>
>>> net user guest /active:yes
>>> ntrights +r SeNetworkLogonRight -u Guest
>>> ntrights -r SeDenyNetworkLogonRight -u Guest
>
>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).

You're welcome, Dave!

Windows XP Home Edition validates all access requests from other
computers via the built-in Guest account. The first "ntrights"
command turns on a setting that allows Guest access on the network.
The second "ntrights" command turns off a setting that denies Guest
access from the network.

I don't what causes the problem. I'm not aware of anything built into
Windows XP Home Edition that can change those settings, but I see the
problem several times a year in the Windows XP networking news group,
and it happened once on my computer.

Haggerrty@discussions.microsoft.com Ed Haggerrty

unread,
May 22, 2007, 5:58:02 PM5/22/07
to
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?

Steve Winograd [MVP]

unread,
May 30, 2007, 4:28:09 PM5/30/07
to
In article <2E9F9563-25F5-45E5...@microsoft.com>, Ed
Haggerrty <Ed Hagg...@discussions.microsoft.com> wrote:

>"Steve Winograd [MVP]" wrote:
>
>> In article <07B57CE2-D8AD-4E23...@microsoft.com>, Lynn
>> Gobin <Lynn...@discussions.microsoft.com> wrote:
>> >"Steve Winograd [MVP]" wrote:
>> >>
>> >> 1. Download and install the Windows 2003 Server Resource Kit Tools
>> >> from http://go.microsoft.com/fwlink/?LinkId=4544 . >>
>> >> 2. Click Start | All Programs | Windows Resource Kit Tools | Command
>> >> Shell.
>> >>
>> >> 3. Type these lines at the command prompt. The second and third
>> >> commands are case-sensitive, so type them exactly as shown. Note the
>> >> "+r" in the second one and the "-r" in the third one:
>> >>
>> >> net user guest /active:yes
>> >> ntrights +r SeNetworkLogonRight -u Guest
>> >> ntrights -r SeDenyNetworkLogonRight -u Guest
>>
>> >Linda said she loved you. I won't go quite so far as to say that, but trust
>> >that I am extremely grateful for your advice. This same problem has dogged me
>> >for months. These three short commands through the Server Resource Kit did
>> >the trick. Thanks!
>>
>> You're welcome, Lynn. :-)
>

>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?

If XP can't access Vista, the problem and the solution are on the
Vista computer. In that case, there's no reason to install the
resource kit and run the commands on XP.

I haven't tried installing the resource kit and running those commands
on Vista, and I don't know whether they work on Vista.

I recommend posting your question in the Vista networking newsgroup.

sheila

unread,
Sep 21, 2008, 12:28:01 AM9/21/08
to

--
Sheila E


"Todd H" wrote:

> I am running a wireless network on WinXP Home w/SP2 (installed on all
> computers). Since installing SP2, we are having trouble sharing files on one
> of the networked computers (the other two work fine). Specifically, a)
> shared folders and files on this computer do not appear in My Network Places,
> and b) although we can view the workgroup computer in My Network Places, when
> we try to access it, we get the error message: "Logon failure: the user has
> not been granted the requested logon type at this computer."
>

> Please help.......Todd

Robert L. (MS-MVP)

unread,
Sep 21, 2008, 10:32:59 AM9/21/08
to
If it is XP Home, try this net user guest /active:yes. More details can be
found this link. Please post back with the result.

Logon Failure user has not been granted the requested logon
http://www.chicagotech.net/netforums/viewtopic.php?p=8035#8035
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"sheila" <she...@discussions.microsoft.com> wrote in message
news:5BDDD9C9-BFC6-43CA...@microsoft.com...

0 new messages