Can't establish a network

D

Don J

Right clicking a folder on my system and selecting "Sharing and Security"
from the displayed menu yields a dialog box that has no "Share this folder
on the network" checkbox available. Is this OK?

On the same display is the statement

"As a security measure, Windows has disabled
remote access to this computer. However, you
can enable remote access and safely share files
by running the 'Network Setup Wizard'".

I've run the 'Network Setup Wizard', and it fails to establish a network, as
evidenced by the fact that again selecting "Sharing and Security" yields the
same screen as described above, with no changes.

I'm running Win'XP Home on two machines. I have firewalls disabled on both
machines.

I'm successfully pinging each PC one from the other.

What do I do? How do I create a network? I am trying to set it up so that
I can share folders on one machine with another.

Don J

--------------------------------------------------------------------------
 
J

John John

Cross Posted to: microsoft.public.windowsxp.general
microsoft.public.windowsxp.network_web

Hi Don;

Perhaps this addresses your problem:

Error message when you try to share a folder on a Windows XP-based
computer: "As a security measure, Windows has disabled remote access to
this computer"
http://support.microsoft.com/kb/913621

Note however that there is an omission in the article. Windows XP Home
Edition does not have a Local Security Policy tool as described in the
article. As explained in another post, in another group, to correct the
problem on XP Home you will have to edit the following registry key/value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
Value: RestrictAnonymous
Value Type: REG_DWORD

Set the value to 0

How to use the RestrictAnonymous registry value in Windows 2000
http://support.microsoft.com/kb/246261/

The article states Windows 2000 but it also applies to Windows XP.

Let us know if it helps.

Regards;
John
 
D

Don J

Restrict Anonymous is already set to 0.

Don J

-------------------------------------------------------------------
John John said:
Cross Posted to: microsoft.public.windowsxp.general
microsoft.public.windowsxp.network_web

Hi Don;

Perhaps this addresses your problem:

Error message when you try to share a folder on a Windows XP-based
computer: "As a security measure, Windows has disabled remote access to
this computer"
http://support.microsoft.com/kb/913621

Note however that there is an omission in the article. Windows XP Home
Edition does not have a Local Security Policy tool as described in the
article. As explained in another post, in another group, to correct the
problem on XP Home you will have to edit the following registry key/value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
Value: RestrictAnonymous
Value Type: REG_DWORD

Set the value to 0

How to use the RestrictAnonymous registry value in Windows 2000
http://support.microsoft.com/kb/246261/

The article states Windows 2000 but it also applies to Windows XP.

Let us know if it helps.

Regards;
John
 
D

Don J

Yes! On both machines.

Don J

-------------------------------------------------------------------------
 
S

Steve Winograd [MVP]

John John said:
Hi Don;

Perhaps this addresses your problem:

Error message when you try to share a folder on a Windows XP-based
computer: "As a security measure, Windows has disabled remote access to
this computer"
http://support.microsoft.com/kb/913621

Note however that there is an omission in the article. Windows XP Home
Edition does not have a Local Security Policy tool as described in the
article. As explained in another post, in another group, to correct the
problem on XP Home you will have to edit the following registry key/value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
Value: RestrictAnonymous
Value Type: REG_DWORD

Set the value to 0

How to use the RestrictAnonymous registry value in Windows 2000
http://support.microsoft.com/kb/246261/

The article states Windows 2000 but it also applies to Windows XP.

Let us know if it helps.

Regards;
John

Yes, the Microsoft KB article is wrong for Windows XP Home Edition.
I'm trying to find another way of accessing the security option
"Network access: Sharing and security model for local accounts" in XP
Home. No luck yet.

The RestrictAnonymous value doesn't determine whether a computer can
share files with other computers on a network. It determines whether
other computers can enumerate (get a complete list of) the disks and
folders that are already shared by that computer.

Set to zero, it allows share enumeration. Typing the sharing
computer's name in the Start > Run box on another computer, in this
form, shows all of the shared disks and folders:

\\computer

Set non-zero, the same command gets an error message saying that
access is denied. In that case, the only way to access a shared disk
or folder is to fully specify its share name, as in:

\\computer\share
--
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
 
J

John John

Steve said:
Yes, the Microsoft KB article is wrong for Windows XP Home Edition.
I'm trying to find another way of accessing the security option
"Network access: Sharing and security model for local accounts" in XP
Home. No luck yet.

The RestrictAnonymous value doesn't determine whether a computer can
share files with other computers on a network. It determines whether
other computers can enumerate (get a complete list of) the disks and
folders that are already shared by that computer.

Set to zero, it allows share enumeration. Typing the sharing
computer's name in the Start > Run box on another computer, in this
form, shows all of the shared disks and folders:

\\computer

Set non-zero, the same command gets an error message saying that
access is denied. In that case, the only way to access a shared disk
or folder is to fully specify its share name, as in:

\\computer\share

I don't have an XP Pro here to try this Steve, but maybe someone with an
XP Pro could snap the registry, do the change to the Local Security
Policy and then re-snap the registry and tell us or post the results of
the compared snaps so we can have a look to see if we can determine the
keys and values to change for XP Home. For anyone interested in doing
it for us, a pretty nifty, good free registry snap tool is available
here: http://regshot.blog.googlepages.com/regshot The snap changes can
easily be saved to a .txt file which could easily be pasted to a post here.

John
 
S

Steve Winograd [MVP]

Lem said:
<snip>

Would NTRights or the NT Security Configuration Manager help here?
http://nitecruzr.blogspot.com/2005/05/advanced-file-sharing-tweaks-in.html

Good idea, Lem.

I ran NTRights, and I don't think that it will help. It grants or
denies rights to specific users. The problem described in KB913621 is
that the sharing and security model for local accounts is set to the
wrong value. That's not a user right.
--
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
 
G

Guest

I have a similar problem that really puzzles me.

I have 2 WinXP-Home SP2 machines named M1 and M2. Each machine has a shared
folder named temp. On either machine, I see their names shown OK under My
Network Places.

On machine M1, when I click to expand M2, I see all shared items from M2,
i.e, \\M2\temp and printer.

On machine M2, clicking to expand M1 yields the error message "M1 is not
accessible, blah blah". However, if I map \\M1\temp to a network drive, say
Z, then I can see the contents of drive Z correctly.

To see why they behave differently, I compare all network, firewall,
RestrictAnonymous settings on the machines. They are identical. Yet machine 1
can see \\M2\temp without problem, while \\M1 is inaccessible to machine 2.
And if I want to see \\M1\temp, then I have to map it to a network drive on
M2 first.

Could someone give me an idea what happens. And what could be done to make
the machine behave the same?

Thank you very much.

Mike U

=====================================================
 

Ask a Question

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.

Ask a Question

Top