Access Denied - weird problem.

[Guest]

I setup simple peer to peer network at home. I allowed file and printer
sharing on both PC's. PC1 can access me without any problems, but when I want
to access his files I get this message. I use only one account on each
machine.

\\PC1 is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions.
Access denied

 

[Guest]

Yes, I've got exactly the same problem which I can't understand. I notice
that on the PC which seems to be denying access, that when I go to My
Computer - Tools - Folder Options - View, I don't seem to have at the bottom
of the list 'Use Simple File Sharing (Recommended)'.

A Microsoft article suggests that I turn this on! The other PC that does
give access does have this and its ticked. Maybe its a clue, but I still
can't fathom what's wrong.

All suggestions welcome.

 

[Guest]

I am having the same problem. After getting help setting up my home network
and internet connection sharing, I still found that I could not access files
on this PC (the client) from the host PC.

Not been a really big problem so far, but I need to move a lot of files from
this PC to the other PC, as the other PC is new. It is quite ironic that I
can move files from the new PC to this PC, but the new PC has no files on it.
:|

 

[Hans-Georg Michna]

\\PC1 is not accessible. You might not have permission to use this network
resource. Contact the administrator of this server to find out if you have
access permissions.
Access denied

Please use http://www.michna.com/kb/wxnet.htm to determine the
cause.

Hans-Georg

 

[Guest]

Do you use a password?? If not, one pc may have the "Limit local use of
blank passwords to console logon only" enabled in the Local Security Policy.

Mat

 

[K. Marcakis]

Check Local Security Policy/User Rights Assignment/Deny access to this
computer from the network:

make sure guest is not listed here.

Kosta

 

[Guest]

I checked the policy and the guest wasn't there.

Check Local Security Policy/User Rights Assignment/Deny access to this
computer from the network:

make sure guest is not listed here.

Kosta

 

[Guest]

I don't use passwords on any machines. That machine with denied access has
the policy enabled.

 

[Hans-Georg Michna]

...

You never replied to my previous message, which contains the
solution to your problem. Why is that?

Just curious, because I want to understand better how the web
page works or fails.

Hans-Georg

 

[Guest]

I am not new to networking, I checked the link and didn't find a solution for
the problem. I checked the guest account and added to the share permisions,
but this didn't solve the problem. Thank you anyway.

 

[Guest]

This was my first post, regarding my problem and I am using this newsgroup
first time as well. There might be an misanderstanding.

 

[Hans-Georg Michna]

I am not new to networking, I checked the link and didn't find a solution for
the problem. I checked the guest account and added to the share permisions,
but this didn't solve the problem. Thank you anyway.

That's quite unusual. After filling in the form in
http://www.michna.com/kb/wxnet.htm, please
copy the selections line at the end of the form
and post it here. Then your problem will most
likely be solved quickly.

Hans-Georg

 

[Guest]

I've had exactly the same problem, and Hans-George's site sorted it - after
16 hours trying everything I could think of and find.

Go to his site, or try this:

You have all the following symptoms:

You can ping the computer by IP and by name.
When you type: net view \\computername, you get the error message, "Error 5:
You do not currently have access to this file. The file may be marked
read-only, or it may be part of a shared resource such as a folder, a named
pipe, a queue, or a semaphore. You can use the ATTRIB command to change the
read-only attribute, or try again later when the file may be available."
This is in some cases caused by a registry setting named RestrictAnonymous.
Go to the computer which you cannot access, start a registry editor and
change the following registry value.

HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Lsa
Value name: RestrictAnonymous
Value type: DWORD

If the value is 1 or even 2, change it to 0, reboot and retest. If the
problem is solved, leave the value at zero. If not, you can change it back if
you like.

Background: RestrictAnonymous controls whether null sessions, sessions that
work without any authentication and use the permissions of the groups
Everyone and NETWORK, are allowed (value 0) or disallowed (value 1). The
value 2 is obsolete for Windows XP.

Don't mistake this for the value named restrictanonymoussam, which controls
null session SAM account name listings.

The man is a GENIUS!

 

[Guest]

Hi,

thank you very much -editing the registry setting really solved the problem.
I would never think about it.

Thank again.

Patrick

 

[Guest]

I went throug the suggested form and it let me to the answer. My problem was
a misconfiguration of IP addresses for computers in the Trusted Zone of Zone
Alarm. Once fixed, access happened. Thank you Hans-Georg!

 

[Hans-Georg Michna]

I went throug the suggested form and it let me to the answer. My problem was
a misconfiguration of IP addresses for computers in the Trusted Zone of Zone
Alarm. Once fixed, access happened. Thank you Hans-Georg!

Vince,

you're welcome. Thanks for reporting back.

Hans-Georg

p.s. The mentioned form is the Network Problem Solver at
http://winhlp.com/wxnet.htm .