Suddenly unable to connect to shared folders.

[Guest]

I have been connecting from my XP box at home to my office PDC (SBS2003 R2)
with out issue for months. My home network is a 192.168.2.0 subnet and the
office is 192.168.0.0. I have a persistent VPN connection set up between the
ADSL routers in each location, so there is always a connection between
subnets.

Suddenly, I cannot open shared folders (in either direction) between the two
networks. I get "\\PDCname\share is not accessible. You might not have
permission to use this network resource... The network path was not found."

However

- I can ping either way successfully
- My LMHosts file is being loaded and nbtstat -c lists the correct entries
for the remote domain
- net view \\PDCname fails - System error 53
- net view \\192.168.0.1 fails (this is the ip address of the PDC)
- Error 53

I set up WINS on the PDC and configured my LAN connection to use it instead
of LMHOSTS but I am still unable to open a shared folder. More to the point,
a colleague with exactly the same set up can access the server with no
problem, so I presume the issue lies with the XP network set up.

Any ideas anyone please?

Keith

 

[jamesh]

We're getting a similar problem with a small office network (might as
well be a home network). Suddenly no access is available to shared
folders, Even From The PC Itself!.

We get an error stating that we may not have proper permissions and at
the bottom of that dialog, it says something about not having enough
memory to process the request (or something to that effect).

This appears to be directly related a security update that was
installed on the 11th. I am not at that site now and don't remember
the KB number for that update. But when looking at the KB for that
update, it talks about it being a security patch to fight a
vulnerability where someone could gain control of your PC, but they
have to do so while logged directly onto the PC itself. Of course,
we'd have never installed that update because there's no risk of that
sort of thing, but in any case, installation of the update immediately
killed the networking, and as I said, even prevents us from accessing
shared folders From The Very Machine in question if we try to access
them using the network path.

This is on an XP machine which simply connects to another XP machine.
It appears that this extra security is too secure

Jim

 

[jamesh]

I did a bit more searching and found a couple of other references to
the exact error we're seeing.

In those threads, it was suggested to read

http://support.microsoft.com/?scid=kb;en-us;177078

which seems to address exactly the error messages we're getting.

The error we're getting is similar to the one quoted in one of these
threads:

"\\Serverprcessor\Mydocuments 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.

Not enough server storage is available to process this command."

This may or may not have anything to do with your problem, KeithXP,
but I thought I'd mention it here since it does look like it may be
the answer to my problem.

Here are the threads that I found that reference this:

http://groups.google.com/group/micr...469e0683aab/8219b01996f92821#8219b01996f92821

http://groups.google.com/group/micr...48c3c743a65/836dd66b3631cc5e#836dd66b3631cc5e

Good luck to you, and wish me luck too. This might fix it for me.

Thanks everyone.

Jim

 

[Guest]

Thanks Jim -
Unfortunately it doesn't appear to apply for my situation. I am not getting
a message about server storage, but checked the value of the registry
entry mentioned (IRPStackSize) and it is at the default value of 15.

I thought I might be onto something with the Scope ID for Netbios (which
must be the same on all computers in communication, it seems). But
that was a red herring as well.

I also tried removing all the updates installed in April. No change.

I am connecting to my server directly by VPN as a workaround until I
figure it out. It is very exasperating!

thanks

Keith

 

[Guest]

Solved!

In my case it turned out that something must have happened to the VPN
connection between the my two Netgear routers. I completely reset the
router on my home network, and set up the VPN connection from scratch.
All working perfectly now.

Good luck with your issue.

Keith

 

[Robert L [MVP - Networking]]

Keith,

Thank you for sharing your experience with us.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Solved!

In my case it turned out that something must have happened to the VPN
connection between the my two Netgear routers. I completely reset the
router on my home network, and set up the VPN connection from scratch.
All working perfectly now.

Good luck with your issue.

Keith