Unusual workgroup interaction problem

Hello,

I currently have a hardware VPN set up between 2 locations and I just started having some problems. Everything was functioning properly until Tuesday.

Anyway, of the 5 PC's on the Indiana side, only one can see the shares on the Pennsylvania side of the VPN. All of the PC's on the Pennsylvania side and see the shares on all the PC's on the Indiania side.

The weird thing is that the PC's on the Indiana side can view the highest layer of the "server" PC in Pennsylvania. For example, when I type in \\ipaddress of the Pennsylvania server, I can see the "D" drive and "Printers & Faxes ". But when I attempt to click on the "D" drive I recieve an error that it is not accessable, or I might not have permission to view the resources. "The specified network name is no longer available ".

If I watch the Pennsylvania server's list of active sessions when I attempt to connect with the Indiana PC's, the sessions will come up as active. I have also tried mapping a network drive using \\ipaddress\sharename, but I get an error saying that the nework name is already in use, but it's not. I disconnected all network drives from the malfunctioning PC and reconnected using different drive letters with the same results.

But if I am using that one PC in Indiana it works and I can navigate around the "D" drive until my fingers fall off.

Any Ideas? Thanks!!!

EDIT -> I was having this problem previously and never got it resolved. It turns out that the only PC I can RDC to from here is also the only one that can still browse the shares. I'm confused.

 

Domain or Workgroup?

What are the subnets at each location?

 

Both are using different workgroup names and are on the 255.255.255.0 Subnet.

 

Had a similar problem.
If you type net use in a cmd window, can you see any of the shares on the computer you cant reach?
If you do see any, try typing net use \\servernarme\sharename /delete
Some times a share might get mapped without any drive letters assigned. Then you have to remove it like this, and just map it again..(with a drive letter )

 

I checked and the only shares that are shown are the ones that are internal to the network.


After digging further, I've found some new information. This is going to be hard to explain, but I'll do my best.

All PC's on the Pennsylvania side can access and browse the server shares on the Indiana side without a problem. The PC's on the Pennsylvania can also view, but not navigate the shares on the PC's on the Indiana side (except the server).

The server on the Indiana side is the only PC that can access the server on the Pennsylvania side, but it cannot access the shares on any other PC on the Pennsylvania. The other PC's on the Indiana, can view the shares on the Pennsylvania server, but cannot navigate through them.

The weird thing is that it's a hardware VPN between two D-Link routers. There isn't anything in the routers that directs network traffic to the servers. So basically they are just normal PC's as far as the VPN is concerned. There aren't any static routes or anything like that.

I'm really confused.