- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
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.
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
Here's a real simple problem to your remote access problems. Go to: http://www.logmein.com Sign up for a free acct, download/install their free software on your Server. Now go over to your laptop, login to your new logmein acct. In the next page, you'll see your Server listed. Click on it - follow instructions to connect. This will tunnel through whatever stuff you have on your network! Trust me - esp. in your scenario, this is *by far* the *simplest remote connect you'll ever perform! And it just .... works! Everytime.
1. Pix does not like class A address, make sure you are using B or C.
2. The VPN subnet always has to be differant to the LAN.
3. Has to have a working DNS server.
4. Add static route, and last resort to main ethernet port that has the DNS & R62. (or 2 if on differant sub)
The key with any VPN solution is to make sure that the configurations on both ends match. I am not very familiar with this particular product, but it looks like you need to have the proper VPN licenses installed first.
There are two types of VPN you can do.
1) Site to Site - This is where the are two static boxes that you want to create an encrypted tunnel between
2) Remote User access - This is where mobile users connect to a central site over an encrypted tunnel from their home or on the road.
Next, take a looks at the User Guide PDF here:
Chapter 10 tells how to configure the VPN on the Firebox side. You would just duplicate your settings if your doing option #1.
Chapter 11 tells how to configure the VPN on the client side. This section would tell you how to configure the client software for option #2.
Hope this helps.