Link to home
Start Free TrialLog in
Avatar of Jeff_Burns
Jeff_Burns

asked on

"The user has not been granted the requested logon type at this computer"

I am so tired of file & print sharing problems...

Computer 1: Win XP Home +SP2, six users, passwords, guest account 'on'. Wired. Internet OK
Computer 2: Win XP Home +SP2, same users & passwords, guest account 'on'. Wireless. Internet OK.

Comp1 can access file and print sharing from Comp2. No problems at all.
Comp2 can NOT access file and print sharing from Comp1.

Pinged both, no problems. Firewalls configured and/or disabled for testing purposes. Comp2 can access the AP and can 'see' Comp1 but cannot access the shares. The error is listed in the question title.

Now these are both XP Home and do NOT have the capability of 'unchecking simple file sharing', a "solution" I see regularly in these forums.

What in the HELL am I overlooking???

Thank you,
Jeff
ASKER CERTIFIED SOLUTION
Avatar of RobArdill
RobArdill

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jeff_Burns
Jeff_Burns

ASKER

"secpol.msc" is not valid in Windows XP Home. I know that works in Win 2K Pro, and possibly in Win XP Pro, but not Win XP Home.
Perhaps get a copy of it from the Administration pack - adminpak.msi

Rob
How and where would I go about getting adminpak.msi ?
Just tried it here and it will only install on XP Pro or Win2003 unfortunately. Kinda defeats the point.

http://www.microsoft.com/downloads/details.aspx?familyid=E487F885-F0C7-436A-A392-25793A25BAD7&displaylang=en

If the above is not an option, you can manually check the policies via the below registry keys on each PC.

HKLM\System\CurrentControlSet\Control\Lsa

Rob

Ok...It seems that there must be some other way to configure two Windows XP Home PC's for simple file & print sharing. Deciphering the hieroglyphics of the registry seem to be a really severe means of solving what should be a basic issue.

Of course, this has become more complex, but is anyone familiar with some other setting on this PC that could be causing the communication problem ?!?!?!?
Is a possiblity some update or program has changed these lsa settings.

A simple compare is all that's needed. Report the differences here and we'll be able lock down on the issue.

secpol.msc will fix the issue, you just need to get a copy from a WinXP install. Keep in mind MS has secpol freely available for download from their website. So getting a copy from a XP Pro install isn't bending the rules. A pain, but probably the simplest way atm moment.

Rob
Rob,
While never classified as 'critical' in Windows Updates, I just downloaded and installed the .NET Framework 1.1 and 2.0 on my personal computer. (Clarification only-the 'problem' computers we were discussing are not onsite.) The Admin Tools now lists .NET Framework config and .NET Framework Wizards, and there are local security settings options in both. Do you know anything about .NET? Could this be the problem...that neither of the PC's had the .NET framework installed??
Thanks,
Jeff
No the secpol.msc is seperate from .NET. It's called "Local Security Policy".

Here is the secpol.msc extracted from the from the downloaded adminpack.exe http://www.users.on.net/~rardill/secpol.zip

Run it and check out the settings on both PC, as per above

Rob

Thanks Rob...I will be working on those machines again tomorrow! I'll keep you posted!
Rob,
I was not able to use the extracted secpol.msc. Despite the hours invested, I could not get Comp2 to access Comp1, so I had to give it up. This should have been a cakewalk, especially since both were running XP. I still have no idea what the problem was, or why I haven't come across that problem before. I appreciate your assistance. Thank you very much!

Jeff
No Problem Thanks