I have a Sonicwall NSA 220 on my work network (10.0.2.x). I have a tomato 1.28 router (192.168.1.x) on my local home network. Behind that router I have a windows 2003 server (VPN: 10.0.2.195, LAN: 192.168.1.200) using Sonicwall groupVPN client to connect to the Sonicwall. On the 2003 server everything works great. I can connect to remote shares, exchange server, etc with no issues.
I'd like to be able to access my work network from a client Win7 machine on my home network. First I enabled IP forwarding on the home 2003 server. Next, I set a route on my tomato router (Destination: 10.0.2.0, Gateway: 192.168.1.200, Mask: 255.255.255.0, Interface: LAN). Now, when I tracert 10.0.2.2 (a 2003 server on the work side) from the home side 2003 server there are no problems. But when I try to tracert from the Win 7 client on the home side it gets to my tomato router and then times out on the next step.
I'm not an expert on routing here. I'm not even sure if what I am attempting is possible. The way I understand routing, the tomato routers knows to send 10.0.2.x traffic to my 2003 server (192.168.1.200), and the 2003 server knows to send 10.0.2.x traffic through the VPN using the Sonicwall VPN adapter (10.0.2.195). Can anyone help me understand what I'm missing here?
Thanks
EDIT: After looking into this a little more I enabled routing and remote access on the home 2003 server. In R&RA I created a static route (destination: 10.0.2.0, gateway: 10.0.2.195, mask: 255.255.255.0, interface (Local LAN: 192.168.1.0). Now when I run a tracert on my Win7 client it goes to my tomato router (192.168.1.1) and then to my home server (192.168.1.200) but gets stuck there.
EDIT2: Here's the routing table on my tomato router
Dest Gateway Mask Metric Interface
x.y.z.1 (home vlan IP) * 255.255.255.255 0 vlan2 (WAN)
192.168.1.0 * 255.255.255.0 0 br0 (LAN)
10.0.2.0 192.168.1.200 255.255.255.0 0 br0 (LAN)
x.y.z.0 * 255.255.240.0 0 vlan2 (WAN)
127.0.0.0 * 255.0.0.0 0 lo
default x.y.z.1 0.0.0.0 0 vlan2 (WAN)
Routing table from home server
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x60003 ...00 1b 21 0f 45 49 ...... Intel(R) PRO/1000 MT Server Adapter - Deterministic Network Enhancer Miniport
0x70005 ...00 60 73 f8 d2 19 ...... SonicWALL Virtual NIC - Deterministic Network Enhancer Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.2.195 192.0.2.195 1
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.200 11
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
10.0.2.0 255.255.255.0 10.0.2.195 10.0.2.195 1
10.0.2.195 255.255.255.255 127.0.0.1 127.0.0.1 1
10.0.2.255 255.255.255.255 10.0.2.195 10.0.2.195 1
192.168.1.0 255.255.255.0 192.168.1.200 192.168.1.200 10
192.168.1.200 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.1.255 255.255.255.255 192.168.1.200 192.168.1.200 10
216.165.129.158 255.255.255.255 10.0.2.195 10.0.2.195 1
216.170.153.146 255.255.255.255 10.0.2.195 10.0.2.195 1
224.0.0.0 240.0.0.0 10.0.2.195 10.0.2.195 1
224.0.0.0 240.0.0.0 192.168.1.200 192.168.1.200 10
255.255.255.255 255.255.255.255 10.0.2.195 10.0.2.195 1
255.255.255.255 255.255.255.255 192.168.1.200 192.168.1.200 1
Default Gateway: 10.0.2.195
===========================================================================
Persistent Routes:
None
Network Diagram.
192.168.1.201 (win7) -\
\
192.168.1.200 (2003) -- 192.168.1.1 (tomato) -- {internet} -- 10.0.2.1 (sonicwall) -- 10.0.2.2 (2003)
| |
10.0.2.195 (2003 VPN iface)----------{VPN) --------------------------------
I hope that's what you were looking for. :)
route printon your home Windows 2003 server. – gravyface Dec 28 '11 at 17:06