Suddenly - - unable to map drives

[JimPletcher]

Two locations connected via VPN routers.
Had been able to map drives in both directions.
As of last week we can only map drives in one direction

Anyone have any ideas?

 

[Helenp1983]

can you map using the IP address instead of the name?

are all ports open between the vpn routers?

In my network places, entire network can you see the server?

 

[JimPletcher]

Can't map by either IP or name.

Never have been able to browse over the VPN.

I should have mentioned that the mapped drives aren't on the server, but on a remote Windows XP machine.

Mapping from the XP to the server is fine.
Users on the same subnet can map to the shares.
Last week userd from other subnets could map the XP shares, this week they can't.

No software firewalls involved (except the Windows firewall, which doesn't seem to have changed).

 

[burtsbees]

What is doing the VPN?

Burt

 

[JimPletcher]

The VPN works fine. EXCEPT that we can not map to the remote XP shares.

 

[brianinms]

There is a limit that only 10 machines can connect to an xp machine. How many machines do you have mapped already?

 

[JimPletcher]

Only one (local) PC is mapped to this XP.

 

[burtsbees]

I realize the vpn works fine, but it could be a config error in the vpn server, such as NAT, acl, split tunneling misconfiguration, etc.

Burt

 

[JimPletcher]

The VPN is established via VPN router/firewalls which have not changed in any way.
I even swapped out both as a test - no change.
This looks more and more like a Microsoft condition.