Should I create a second WAN Interface for a new SSLVPN setup on my Sonicwall 2400?

Posted by TheSuperman on Server Fault See other posts from Server Fault or by TheSuperman
Published on 2013-11-11T10:31:56Z Indexed on 2013/11/11 15:58 UTC
Read the original article Hit count: 254

Filed under:
|
|
|
|

Sonic Wall 2400

I'm setting up a new SSLVPN on our Sonicwall, very new to this.

I currently have an exchange server as well, so mail.company.com is directed to our mail server. I'd like to setup a clean link for my low end users, remote.company.com to be for the SSLVPN, but I'm not sure how to do this within the Sonicwall?

I setup SSLVPN on port 443. Only 1 WAN setup, on the X1 Interface. We have an A record setup with the same static IP used on the WAN Interface, and is configured for mail.company.com.

Should I use a new static IP from our block of usable IP's to create the new Remote.Company.com? If so, I have no idea where to start on this on the Sonicwall?

Any suggestions?

© Server Fault or respective owner

Related posts about vpn

Related posts about firewall