asked on

2 Networks connected by site to site VPN, 1 Server is not contactable, everything else ok!!

Ok i have 2 networks connected by two sonicwall tz170's they have different domains.

domain1.local - 192.168.102.0 -255
domain2.local - 192.168.50.0 -255

domain2 is the branch domain so this needs access to domain1.

Every other server is fully contactable on domain1 other than sql.domain1.local (192.168.102.2)

Even if i ping 192.168.102.2 from domain2's Sonicwall utility it cant see it...

Tracert wont show anything at all for this IP.

Any help here would be great!!

Britt Thompson

Is the server in question using a different gateway than the other servers? If so, you'll need to create a static route on the server itself so the Sonic Wall can talk to it:

(assuming 192.168.102.1 is your gateway)
Route -p add 192.168.50.0 mask 255.255.255.0 192.168.102.1

racphillips

ASKER

Thanks for reply, its on the same gateway, but is on subnet 255.255.0.0 and all other servers and machines are on 255.255.255.0.

sorry didnt notice this before, but i assume this is my problem!

Cheers,

RIch

Rob Williams

Are you sure there is no software firewall enabled on sql.domain1.local, such as the windows firewall? Often various services automatically create firewall exceptions but they do so only for the local subnet. Remote subnets require the firewall be disabled, or the firewall exception scope option be edited to allow the remote subnet.

racphillips

ASKER

No software Firwalls, windows ICS and firewall disabled. RRAS disabled. subnet being different is all i can find...

Rob Williams

Are the other servers for that domain on the same subnet?
With a typical site-to-site VPN, there is one subnet at each site, and for routing to take place they must be different. Unless there are multiple gateways (make sure sql.domain1.local has the VPN router set as its default gateway) it shouldn't be a routing or subnet issue.

racphillips

ASKER

Domain1

dc.domain1.local - 192.168.102.1 (255.255.255.0) gateway: 192.168.102.5
sql.domain1.local - 192.168.102.2 (255.255.0.0) gateway: 192.168.102.5
ts.domain1.local - 192.168.102.3 (255.255.0.0) gateway: 192.168.102.5
Sonicwall - 192.168.102.5

Domain2

dc2.domain1.local - 192.168.50.1 (255.255.255.0) gateway: 192.168.50.4
Sonicwall - 192.168.50.4

ASKER CERTIFIED SOLUTION

Rob Williams

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

racphillips

ASKER

Changed it to 255.255.255.0 and all is good! :) i dont know why it would have been set to this? accident? a bad one! thanks for your help

Rob Williams

Good to hear. Easy enough mistake to make.
Thanks racphillips.
Cheers!
--Rob