The fact is that if a client in site A can't ping a client in site B (or
vice versa), you don't have a site-to-site VPN! You are obviously lacking a
route somewhere.
Each router should have a subnet route for the "other" site through the
tunnel. If that is there it should work. If it doesn't, the usual reason is
that the VPN router is not the default gateway for the clients in the site.
If that is the case, you need extra routing on the gateway router to bounce
the private traffic to the VPN router.
(E-Mail Removed) wrote:
> I'm posting this again to see if anyone has any new insight. I never
> got an answer before and the workaround we were using is no longer
> acceptable.
>
> Ok here is our setup. We have an Atlanta office controlled by a SBS
> 2003 Server with ISA 2004. We have a network in Dallas controlled by a
> Cisco PIX firewall. I have setup a site-to-site IPSec VPN using ISA
> and the PIX.
>
> Pinging between the Atlanta server and the entire dallas network
> works. Dallas clients can only ping to the Atlanta server, and not
> Atlanta clients, but this isn't a huge concern.
>
> Remote Desktop works from the Atlanta server and clients to all of the
> Dallas servers. RD works from Dallas to the Atlanta server, but not to
> the Atlanta clients, but again this is not a big concern, just
> providing it for information's sake.
>
> What we need working is mapping to shared drives. I am only trying to
> get this working by IP as we won't be using the hostname or server
> names to map.
>
> Mapping works from the Dallas servers to the Atlanta server, but not
> to Atlanta clients. Mapping does not work from the Atlanta server or
> clients to the Dallas network. This last one is our biggest concern.
>
> If anyone can provide any insight why we can't map to Dallas shares it
> would be greatly appreciated.
>
> Thank you,
> John
Similar Threads
Linear Mode
