Search results for query: *

I found a couple of problems: the Sonicwall/10 router I configured as a bridge between the 172.16.0.0/255.255.0.0 (connected to it's LAN port) and 10.159.241.0/255.255.255.0 (WAN port) segments is part of it. When VPN tunneling, the Sonicwall rejects packets from the tunnel because the address...

Based on the tracert output, I'd say it's a routing problem - is it because the Netscreen is dropping the return packet routing, because it's not configured to recognize the static addresses I'm using? I can't get the Netscreen to issue a DHCP to the lan side of the Netgear, so I had to use a...

Changing and testing one thing at a time, I got a bit further. I discovered that there was a netmask mismatch, that was subnetting my class B network to a class C. I fixed that and was finally able to ping the machines on the 172.16.0.0/255.255.0.0 subnet. I wasn't able to ping any machines...

Here is the output from ipconfig (TIA): C:\Documents and Settings\Neil>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Fishbourne Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. ...

I've successfully set up a home based XP VPN PC client to office based FVS318v2 using XP's IPSec policies, thanks to the excellent info on this site. Before this, I'd also set up FVS318v2 to FVS318v2 site to site VPN. The site to site and the XP vpn tunnels both have the same problem, only the...