File sharing working one way

[Byteguy]

Can't find the solution in other posts so far. A curious problem.
Couldn't ping either way in a 2-computer network. Disabled the
firewall and turned the router firewall on and now can ping both ways.
On computer #1, I can see the shared folders and files on computer #2
and print to its shared printer.
On computer #2, I can see the shared folders on computer #1, but
cannot access the files, but can print to its shared printer. Also
have a shared USB drive that is visible, but not accessible.
I've tried unsharing and resharing the folders to no avail.
What am I missing? This was working several weeks ago but has all of
a sudden stopped.

 

[Anurag Shukla]

- Well you have not mentioned the OS on the both machine
I consider it be XP 32 Bit, bcz if one is 64 bit FS will not work.

- Make sure you check the Simple file sharing on both machine
- Booot both the machine in Safe mode with networking & then check
- If the machines are under the AD enviorement make sure you disable the
default domain policy.
- Make sure both the machines are in the same work group
- enable the guest account on both machine

Still have problems feel free to revert.

 

[Malke]

- Well you have not mentioned the OS on the both machine
I consider it be XP 32 Bit, bcz if one is 64 bit FS will not work.

- Make sure you check the Simple file sharing on both machine
- Booot both the machine in Safe mode with networking & then check
- If the machines are under the AD enviorement make sure you disable the
default domain policy.
- Make sure both the machines are in the same work group
- enable the guest account on both machine

Still have problems feel free to revert.

I'm sorry but this is completely backwards and wrong.

Malke

 

[Malke]

Can't find the solution in other posts so far. A curious problem.
Couldn't ping either way in a 2-computer network. Disabled the
firewall and turned the router firewall on and now can ping both ways.
On computer #1, I can see the shared folders and files on computer #2
and print to its shared printer.
On computer #2, I can see the shared folders on computer #1, but
cannot access the files, but can print to its shared printer. Also
have a shared USB drive that is visible, but not accessible.
I've tried unsharing and resharing the folders to no avail.
What am I missing? This was working several weeks ago but has all of
a sudden stopped.

What changed several weeks ago? Take a look at my standard network
troubleshooting information below. Go through each step carefully (will
only take a few minutes) to see where things went awry.

For XP, start by running the Network Setup Wizard on all machines (see
caveat in Item A below).

Problems sharing files between computers on a network are generally caused
by 1) a misconfigured firewall or overlooked firewall (including a stateful
firewall in a VPN); or 2) inadvertently running two firewalls such as the
built-in Windows Firewall and a third-party firewall; and/or 3) not having
identical user accounts and passwords on all Workgroup machines; 4) trying
to create shares where the operating system does not permit it.

A. Configure firewalls on all machines to allow the Local Area Network (LAN)
traffic as trusted. With Windows Firewall, this means allowing File/Printer
Sharing on the Exceptions tab. Normally running the Network Setup Wizard on
XP will take care of this for those machines.The only "gotcha" is that this
will turn on the XPSP2 Windows Firewall. If you aren't running a
third-party firewall or have an antivirus/security program with its own
firewall component, then you're fine. With third-party firewalls, I
usually configure the LAN allowance with an IP range. Ex. would be
192.168.1.0-192.168.1.254. Obviously you would substitute your correct
subnet. Refer to any third party security program's Help or user forums for
how to properly configure its firewall. Do not run more than one firewall.
DO NOT TURN OFF FIREWALLS; CONFIGURE THEM CORRECTLY.

B. For ease of organization, put all computers in the same Workgroup. This
is done from the System applet in Control Panel, Computer Name tab.

C. Create matching user accounts and passwords on all machines. You do not
need to be logged into the same account on all machines and the passwords
assigned to each user account can be different; the accounts/passwords just
need to exist and match on all machines. DO NOT NEGLECT TO CREATE
PASSWORDS, EVEN IF ONLY SIMPLE ONES. If you wish a machine to boot directly
to the Desktop (into one particular user's account) for convenience, you
can do this:

XP - Configure Windows to Automatically Login (MVP Ramesh) -
http://windowsxp.mvps.org/Autologon.htm

D. If one or more of the computers is XP Pro or Media Center, turn off
Simple File Sharing (Folder Options>View tab).

E. Create shares as desired. XP Home does not permit sharing of users' home
directories or Program Files, but you can share folders inside those
directories. A better choice is to simply use the Shared Documents folder.
See the first link above for details about Vista sharing.

Malke

 

[Malke]

Well, both machines are XP Pro. No, we don't have the same username/
password on both machines--don't have --we are using simple file
sharing. Never had a problem with this before--as I said, from my
machine I can see the other computer and all shared docs. Cannot
reciprocate, though.
Firewall is Trend Internet Security. IP range of the LAN is
explicitly allowed on both machines. No, Windows firewall is not
enabled.
When I disable Trend firewall and enable the router firewall, there is
still the file sharing problem.
Yes, both computers are in the same workgroup.
Just tried to access a notebook. Can access it from this computer,
but the notebook cannot see the files here. Can create network places
(can see the folders) but cannot access the folders.

Then just go ahead and create the matching user accounts/passwords and
disable Simple File Sharing.

Malke

 

[Byteguy]

What changed several weeks ago? Take a look at my standard network
troubleshooting information below. Go through each step carefully (will
only take a few minutes) to see where things went awry.

For XP, start by running the Network Setup Wizard on all machines (see
caveat in Item A below).

Problems sharing files between computers on a network are generally caused
by 1) a misconfigured firewall or overlooked firewall (including a stateful
firewall in a VPN); or 2) inadvertently running two firewalls such as the
built-in Windows Firewall and a third-party firewall; and/or 3) not having
identical user accounts and passwords on all Workgroup machines; 4) trying
to create shares where the operating system does not permit it.

A. Configure firewalls on all machines to allow the Local Area Network (LAN)
traffic as trusted. With Windows Firewall, this means allowing File/Printer
Sharing on the Exceptions tab. Normally running the Network Setup Wizard on
XP will take care of this for those machines.The only "gotcha" is that this
will turn on the XPSP2 Windows Firewall. If you aren't running a
third-party firewall or have an antivirus/security program with its own
firewall component, then you're fine.  With third-party firewalls, I
usually configure the LAN allowance with an IP range. Ex. would be
192.168.1.0-192.168.1.254. Obviously you would substitute your correct
subnet. Refer to any third party security program's Help or user forums for
how to properly configure its firewall. Do not run more than one firewall..
DO NOT TURN OFF FIREWALLS; CONFIGURE THEM CORRECTLY.

B. For ease of organization, put all computers in the same Workgroup. This
is done from the System applet in Control Panel, Computer Name tab.

C. Create matching user accounts and passwords on all machines. You do not
need to be logged into the same account on all machines and the passwords
assigned to each user account can be different; the accounts/passwords just
need to exist and match on all machines. DO NOT NEGLECT TO CREATE
PASSWORDS, EVEN IF ONLY SIMPLE ONES. If you wish a machine to boot directly
to the Desktop (into one particular user's account) for convenience, you
can do this:

XP - Configure Windows to Automatically Login (MVP Ramesh) -http://windowsxp.mvps.org/Autologon.htm

D. If one or more of the computers is XP Pro or Media Center, turn off
Simple File Sharing (Folder Options>View tab).

E. Create shares as desired. XP Home does not permit sharing of users' home
directories or Program Files, but you can share folders inside those
directories. A better choice is to simply use the Shared Documents folder..
See the first link above for details about Vista sharing.

Malke

Well, both machines are XP Pro. No, we don't have the same username/
password on both machines--don't have --we are using simple file
sharing. Never had a problem with this before--as I said, from my
machine I can see the other computer and all shared docs. Cannot
reciprocate, though.
Firewall is Trend Internet Security. IP range of the LAN is
explicitly allowed on both machines. No, Windows firewall is not
enabled.
When I disable Trend firewall and enable the router firewall, there is
still the file sharing problem.
Yes, both computers are in the same workgroup.
Just tried to access a notebook. Can access it from this computer,
but the notebook cannot see the files here. Can create network places
(can see the folders) but cannot access the folders.

 

[Byteguy]

Byteguywrote:

Then just go ahead and create the matching user accounts/passwords and
disable Simple File Sharing.

Malke

I'll give it a try.

 

[Byteguy]

Byteguywrote:

Then just go ahead and create the matching user accounts/passwords and
disable Simple File Sharing.

Malke

Tried it. Same results, but the actual error message is "not enough
server storage is available to process this command"

 

[Malke]

Tried it. Same results, but the actual error message is "not enough
server storage is available to process this command"

And this is why having the exact text of an error message is important. If
you'd told us this in the first place...

From MVP Ron Lowe - This error indicates that you are falling foul of the
IRPStackSize bug. The problem is on the machine you are attempting to
connect to, not the machine where you see the error message. On the
computer you are attempting to connect to, check the event viewer for an
event ID 2011.

Usual fix : You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to, Set the IRPStackSize back
to the default (15 ). Perform the following steps:

1. Start regedit.
2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters.
3. Double-click IRPStackSize (or if this registry setting doesn't exist,
create it with type DWORD and ensure the case is correct).
4. Change the base to decimal, set the value to 15, and click OK.
5. Reboot the computer.

Norton AV is usual suspect for breaking it. There's a KB article about this,
too:

Antivirus Software May Cause Event ID 2011 (Q177078) -
http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078

Malke

 

[Byteguy]

Byteguywrote:

And this is why having the exact text of an error message is important. If
you'd told us this in the first place...

From MVP Ron Lowe - This error indicates that you are falling foul of the
IRPStackSize bug. The problem is on the machine you are attempting to
connect to, not the machine where you see the error message. On the
computer you are attempting to connect to, check the event viewer for an
event ID 2011.

Usual fix : You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to, Set the IRPStackSize back
to the default (15 ). Perform the following steps:

  1. Start regedit.
  2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters.
  3. Double-click IRPStackSize (or if this registry setting doesn't exist,
create it with type DWORD and ensure the case is correct).
  4. Change the base to decimal, set the value to 15, and click OK.
  5. Reboot the computer.

Norton AV is usual suspect for breaking it. There's a KB article about this,
too:

Antivirus Software May Cause Event ID 2011 (Q177078) -http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078

Malke

I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

 

[Malke]

I know--in my frustration, I completely forgot to mention the error.
I did what you said, but the error persists. (the key didn't exist, so
I created it).
I looked at the other computers that allow access to the files, and
this key doesn't exist there.

FYI, I don't use Norton. Too much of a system hog.

Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke

 

[Byteguy]

Byteguywrote:


Then I can't help you any further. It's very difficult to diagnose
networking issues without being able to see the computers involved. Perhaps
someone else will have an idea for you or you may decide that having a
local tech come on-site and straighten things out is a Good Thing. If you
go that route, I don't recommend using a BigComputerStore/GeekSquad type of
place.

Sorry I was unable to help you.

Malke

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

 

[Lem]

Hate to say it, but I am the local computer tech!
I just haven't run into this type of thin before.

Thanks for your efforts

FYI--I have had to go onsite and fix Geek Squad work.

This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15. Keep
trying all the way to 50.

 

[Byteguy]

Byteguywrote:




This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15.  Keep
trying all the way to 50.

Took your suggestions. No change.
The funny thing is, it used to work. We're on a peer-to-peer network
here. From this computer, I can see the others and their files with
no problems at all
They can see this computer and the shared folders. Anything below the
folder level they cannot see. BUT: they can print to the printer
attached to this computer.
It appears that permissions are not passing down below the folder
level, even though I'm using simple file sharing.

 

[Byteguy]

Byteguywrote:




This isn't meant to sound condescending, but double check that you are
making the registry change on the *remote* computer and not the computer
on which the error appears.

Also, sometimes you need to increase IRPStackSize beyond 15.  Keep
trying all the way to 50.

Took your suggestions. No change.
The funny thing is, it used to work. We're on a peer-to-peer network
here. From this computer, I can see the others and their files with
no problems at all
They can see this computer and the shared folders. Anything below the
folder level they cannot see. BUT: they can print to the printer
attached to this computer.
It appears that permissions are not passing down below the folder
level, even though I'm using simple file sharing.