I am trying to setup the vpn feature using quickvpn. I can get the quickvpn client to connect but can not ping any local subnet machine addresses except for the one assigned to the router. I need some info on the vpn policy setup to ensure I am configuring it correctly as I am unfamiliar with this devices interface and terminology. My local subnet is 192.168.1.0/255.255.255.0 the router local is 192.168.1.18 with the public ip assigned and pingable via the net. Any help would be appreciated I have worked on this for hours with no avail

In the rules, you will need to create a new rule that allows your VPN subnets access to you office LAN, and then on your office network gateway, add a route for your VPN subnet pointing back to your checkpoint firewall.

192.168.1.X is a local ip address ,, i trust that thhe vpn is in seperate places and is done with the wan ip over an internet connection?????

OK maybe the problem isnt on your side but the main office building,, when connecting , have someone looked for repeated attemps to connect by observing the fire wall,, if it appears to be blocked byu the firewall simply diasable any and try it out.. If it works then all you need to do is set the firewall correctly..

I was reading the ip address in your original post and those are local address,s are you certin the VPN is correct ???? did you use the correct STATIC IP ADDRESS ASSIGNED BY YOUR ISP??

It could be a missing route... are the file server and email server on the same subnet? If they are then it is possibly not a routing issue.

Also it would be worth checking the tunneling settings for the VPNs... if you have specifed either only the fileserver subnet or specifically the file server address, then this could be the reason they can get to nothing else.

Hope that this has helped a little :)

Ok to Setup you VPN follow the instructions below. You can configure DI-804HV, DI-808HV, and DI-824VUP+ by web management interface. Type 192.168.0.1 (The LAN IP is 192.168.0.1 by default) in the browser, and then input user name: admin (there is no password by default) to pass authentication of web management interface. Then finish the configurations as showed below on Gateway A and Gateway B. Configurations of Gateway A 􀂾 Model: DI-804HV (DI-808HV, or DI-824VUP+) 􀂾 Firmware version: v1.40 (You can download the latest firmware on D-Link’s website.) 􀂾 WAN IP Address: 14.15.16.17 (Static IP) 􀂾 LAN IP Address: 10.5.6.1 (Subnet Mask: 255.255.255.0) 􀂾 VPN Configurations: 􀂄 Enable VPN function on Gateway A. 􀂄 Tunnel Name: toGatewayB 􀂄 VPN Method: IKE (Main mode) 􀂄 Local Subnet: 10.5.6.0 􀂄 Local Netmask: 255.255.255.0 􀂄 Remote Subnet: 172.23.9.0 􀂄 Remote Netmask: 255.255.255.0 􀂄 Remote Gateway: 22.23.24.25 􀂄 Pre-share Key: hr5xb8416aa9r6 􀂄 IKE Proposal (Please remember to add the correct proposal ID into the list of IKE Proposal Index when you finish inputting the following information.) 􀀹 Proposal Name: toGatewayB 􀀹 DH Group: Group 2 􀀹 Encryption Algorithm: 3DES 􀀹 Authentication Algorithm: SHA1 􀀹 Life Time: 28800 􀀹 Life Time Unit: Second 􀂄 IPSec Proposal (Please remember to add the correct proposal ID into the list of IKE Proposal Index when you finish inputting the following information.) 􀀹 Proposal Name: toGatewayB 􀀹 DH Group: Group 2 􀀹 Encapsulation Protocol: ESP 􀀹 Encryption Algorithm: 3DES 􀀹 Authentication Algorithm: SHA1 􀀹 Life Time: 3600 􀀹 Life Time Unit: Second 4. Verify the VPN connection Before you start to establish VPN connection between Gateway A and Gateway B, please make sure the Internet connection between Gateway A and Gateway B is workable. You can use “Ping Test” tool on Gateway A (or Gateway B), and input the IP address of Gateway B (or Gateway A) to see if there is any response from its peer device. Connect a PC (called PC_A) to the LAN port of Gateway A, and connect another PC (called PC_B) to the LAN port of Gateway B. Start to “Ping” PC_B on PC_A, then Gateway A will start to establish IPSec connection with Gateway B. If you can get “Ping” responses from PC_B on PC_A, then it means the tunnel has been established successfully. You can also check the “VPN Status” page with web management interface to verify the status of VPN connections. Figure 1: VPN status of Gateway A after IPSec connection has been established. Figure 2: VPN status of Gateway B after IPSec connection has been established.
Hope this helps
Here it is in PDF.http://www.vpnc.org/InteropProfiles/D-Link-DI.pdf

So you verified ICMP traffic isn't blocked and it appears the servers allow the netBios traffic to pass.

On the client machine, check to make sure the windows print and file sharing is installed and the machine isn't blocking netBios traffic.

Make sure TCP ports 137,139, and 445 are open on the xp machine and any devices in between.

It's acting like the TCP data is being blocked by the client machine.

HTH,
-Aaron

This is an excerpt from a MS Technet page for error 53:
Resolutions: 1) if it is domain environment, check your WINS; 2) if it is peer-to-peer workgroup, enable NetBIOS over TCP/IP; 3) make sure the machine is running; 4) make sure file and Printer Share enabled on remote computer; 5) make sure client for ms networks is enabled on local computer; 6) make sure you type the correct name. 7) Make sure no firewall running or any security setting.
Pay close attention to #s 4 and 5 - I suspect XP pro might not be open enough.

Use the Sonicwall configuration wizard..

Please find below is to configure what ever you want.

Setup Wizard - This wizard will help you quickly configure the SonicWALL to secure your Internet connection. Once completed, you can use the SonicWALL Web Management Interface for additional configuration.

Registration & License Wizard - This wizard will help you register you and your firewall with mysonicwall.com and obtain licenses for additional Security Services features.

PortShield Interface Wizard - Segment and configure the integrated managed LAN switch of the SonicWALL.

Public Server Wizard - Quickly configure your SonicWALL to provide public access to an internal server.

VPN Wizard - Create a new site-to-site VPN Policy or configure the WAN GroupVPN to accept connections from the SonicWALL Global VPN Client
Thanks
..

sonic is sitting on the gateway. so dont matter where u are still u cant get outside

Resolutions: 1) if you have firewall, open TCP Port 1723, IP Protocol 47 (GRE). 2) make sure you can reach the VPN server by using ping. Sometimes, poor connection can cause this issue too. 3) You may need to updated firmware on a router or firewall if other OS (win9x/nt/me/w2k) works except XP. 4) The VPN server may not be able to get IP from DHCP for the VPN client. So, you may want to re-configure VPN host networking settings. For XP pro VPN host, go to the Properties of the VPN>Network, check Specify TCP/IP address and Allow calling computer to specify its own IP address, and uncheck Assign TCP/IP addresses automatically using DHCP. 5) Make sure no other secure software blocks your access, for example, if you use Norton secure software, you may need to add the remote client's IP so that the client can access. 6) If your VPN running on a Windows RRAS with NAT enabled, you may want to check the NAT settings. 7) If you can establish the VPN from the desktop at home but not from the laptop. Make sure no security software like Microsoft OneCare software that blocks the GRE.