XP WorkGroups Networking

[jhutton]

I'm having a problem setting up two XP systems under a WorkGroup.
I used the Network wizard on machine A and then ran it on machine B.
I shared out a folder on the B system and gave it full windows permissions and full NTFS permissions.
I went to My Networks Places and the shared drive was listed and accessible.
I then tried to access it through the WorkGroup (still on machine B) and it said I don’t have permissions or rights.

Summary:
I created the share on B
I accessed it though My Network Places on B
I was not allowed access going to it through the WorkGroup listing on B.

What setting is wrong?

Thanks in advance.

 

[bcastner]

Why are you trying to access yourself through a network share? You should be able to in any case but it seems an odd thing to do.

I shared out a folder on the B system and gave it full windows permissions and full NTFS permissions.

To what user or Group did you grant these Share and NTFS permissions?

Relatedly, since you are using XP Professional with Simple File Sharing disabled, what is the status of your Guest account?



____________________________
Users Helping Users

 

[jhutton]

I could not access the shared drive from system A so I was troubleshooting the problem and found that I could not get access to the folder on system B while using the WorkGroup path.
The share is full privileges for EveryOne. The NTFS has each person that has each login.
What do you want me to check on the Guest account?

Thanks,
Jim

 

[bcastner]

Whether it is enabled or not.

Pleae see this article to check the status of your Netbios over TCP/IP settings:

http://support.microsoft.com/?kbid=318030

Now, where is this folder?
Is it in a User Profile?
Is it the Shared Documents folder?
In both these cases making the folders available through a share is slightly complicated:

http://support.microsoft.com/default.aspx?scid=kb;en-us;304040

____________________________
Users Helping Users

 

[jhutton]

Should the Guest account be on or off?

I will look into the other links and get back with you.

Thanks

 

[bcastner]

If authentication is set to the Default:

Start, Run, net user GUEST /Active:yes

This sets Group Guest as active. It does not effect User Guest for local logons to the worktation.

Second, set the restrictanonymous value:

http://support.microsoft.com/Default.aspx?kbid=913628US;q24461756-d8fe-4a91-93cf-ed6985e3927b

Reboot and test again.


____________________________
Users Helping Users

 

[jhutton]

Guest accounts are active
Login accounts are identical on A and B systems
The restrictanonymous value was set to Zero
The Netbios over TCP/IP settings are correct
I have file sharing set to simple
Shared folders are under the shared documents folder on both systems

Computer B can look at A folders
Computer A can not open computer B folders
Computer A can see the shared folders
I get a error that "\\???? is not assessable or you do not have permissions contact admin." when I try to open.

Computer A is wired to the router
Computer B is a wireless connection

I can ping both ways successfully by name and IP address

 

[bcastner]

Now, where is this folder?
Is it in a User Profile?
Is it the Shared Documents folder?
In both these cases making the folders available through a share is slightly complicated. In the case of user profiles you will need to add to the ownership of the folder in Documents and Settings.

http://support.microsoft.com/default.aspx?scid=kb;en-us;304040

____________________________
Users Helping Users

 

[jhutton]

The shared files on A are located:
C:\Documents and Settings\All Users\Documents
And share files on the Network and allow changes

The shared files on B are located:
C:\Documents and Settings\All Users\Documents
And share files on the Network and allow changes

Both have the same permissions
B can open A files
A can't open B files

 

[bcastner]

It really is not a good idea to create shared folders in the Documents and Settings area.

Create a new folder from the root and share that; e.g.
C:\All User Data\

In any case...

Logon to each machine as Administrator.

1. In Explorer, right click:
\Documents and Settings\All Users
2. And then Properties, and then Sharing and Security.
3. Under the Security tab, click Advanced, and then click the Owner tab.
4. In the Name list, click the Everyone group. If you want to take ownership of the contents of that folder, select the Replace owner on subcontainers and objects check box.
5. Click OK, and then click Yes when you receive the following message:
You do not have permission to read the contents of directory folder name. Do you want to replace the directory permissions with permissions granting you Full Control?

All permissions will be replaced if you press Yes.
Note folder name is the name of the folder that you want to take ownership of.
6. Click OK, and then reapply the permissions and security settings that you want for the folder and its contents.

Finally, on both machines, do a:
Start, Run, net localgroup everyone guest /add







____________________________
Users Helping Users

 

[jhutton]

Should simple file sharing be on or off for the suggestion above?

 

[jhutton]

I ask this because I would have to turn Simple File Sharing off to have the security tab and advanced.

Jim

 

[bcastner]

I ask this because I would have to turn Simple File Sharing off to have the security tab and advanced,

You said in your original post that you set NTFS permissions. In order to do this, Simple File Sharing would have to be disabled. I operated under that assumption.

Which security model do you want? Simple File Sharing enabled or disabled? They are profoundly different security models.

You have to make a choice.


____________________________
Users Helping Users

 

[jhutton]

I set the systems to NOT use Simple File Sharing and followed the instructions on applying the permissions.
I still get the same results.
The B computer folders cannot be accessed through the WorkGroup from computer A or locally from the B computer.

I get the same exact error message from both system when try to open the folders:

\\joah\All_Shared_Data is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out it you have access permissions. Not enough server storage is available to process this command.

If you try to access from a browser the last sentence changes to:
The network path was not found.

 

[bcastner]

Do not attempt browser access.
You would need to set custom settings using the registry to avoid the local computer lockdown zone.

Now, have you restarted all the computers since making these changes?

These changes are mainly registry based and require a restart of your Workgroup.


____________________________
Users Helping Users

 

[jhutton]

Yes I have reb ooted each system after making the changes.

 

[bcastner]

Then there is still an issue with restrictanonymous:

http://support.microsoft.com/Default.aspx?kbid=913628

____________________________
Users Helping Users

 

[jhutton]

I just reconfirmed that both systems are set to a value of zero.

 

[bcastner]

Start button/Administrative Tools/Local Security Policy/Security options/

DISABLE: "Accounts: Limit local account use of blank passwords to console login only"

ENABLE: "Network Access: Let Everyone permissions to apply to anonymous users"

Network access: Sharing and security model for local accounts. Set to Classic.

Now Click User Rights Assignments:

Access this computer from the network: make sure it includes the Group Everyone.

Deny access to this computer from the network: Make sure the Group Guests and Group Everyone and any defined user is NOT included in this listing.

Now open Network Places. Expand the listing of Shared Folders under the other computer's icon. Pick any share, right click, and select Map. Use any unused drive letter.

Now see if you can access those files in Explorer.


____________________________
Users Helping Users

 

[jhutton]

I made the changes and rebooted the B computer.
Went to the A computer and Maped the drive and it failed.\ to map the drive.
It stated it could not map the drive. Not enough server storage is available to process this command.

I appreciate your time.