Server veiwable from far side of VPN, but Server can not see far side of VPN

I have a client that has two locations conected via IPSEC VPN. The VPN is controled by an Astaro 220 firewall on the near side (10.0.X.X) and and a Linksys WRV200 at the remote location (192.168.X.X).  The remote location has no problem seeing all of the computers, mapping drives, or accessing exchange on the  10.0.X.X network. The issues is that the 10.0.X.X network can not see any of the PCs on the 192.168.X.X network. I can ping them, but can not access them via RDP, Net Use, or Map drive option in my computer.

What I have Chedcked so Far.
1. The Astaro Firewall has rules to allow all traffic in both directions over the VPN
2. The remote router looks to the Server on the 10.0.X.X network for DNS
3. The Server looks to itsef for DNS first
4. There are records in DNS for the remote network on the Server (Windows 2003 SBS)
5. Net Bios is enabled on PCs on both sides of the VPN
 
I am not sure where to go from here, any help would be great , Thanks
TeleswitchAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Rob WilliamsConnect With a Mentor Commented:
>>"RDP and file share do not work ."
I assume you mean they do not work when accessing by IP rather than by name?

It can be related to too high an MTU value, usually you can connect, with MTU it doesn't fail until you actually start to transfer data.

The only other thought I have is this can sometimes be resolved by disabling "black Hole Router" detection. :
http://support.microsoft.com/kb/314825
0
 
Rob WilliamsCommented:
For the record NetBIOS will not as a rule work over the VPN, however if there are DNS entris on the local (10.0.x.x) server for the remote site, I am surprised access by DNS name doesn't work.
As a test can you access remote resources by IP such as RDP or file shares:
RDP:             mstsc  -v:192.168.123.123
Flie shares:  \\192.168.123.123\ShareName

If that works try accessing by FQDN:
RDP:             mstsc  -v:Computer1.local
Flie shares:  \\Computer1.local\ShareName
0
 
TeleswitchAuthor Commented:
RDP and file share do not work .
0
 
Rob WilliamsCommented:
Thanks Teleswitch.
Cheers !
--Rob
0
All Courses

From novice to tech pro — start learning today.