asked on
WAN and LAN NIC on Windows Server 2012
I have a web portal that is both internet facing and LAN facing.. I have the WAN NIC with a public IP and gateway. The LAN NIC only had an internal IP and no gateway. This worked just fine, however, we setup a site to site tunnel to our office.. We also use our internal domain DNS which resolved the internal IP of the web portal.. The site to site tunnel will required the LAN NIC to have the local gateway to be able to route between the two subnets in the site to site tunnel. Due to this I added the internal gateway to the LAN NIC. Everything is working, however, as I understand this is not best practice.. So.. Should I change the internal DNS records to resolve the public IP so the site to site users hit the public IP or should I setup static routes on the Windows server? I kind of like how the site to site users can access the web portal through the tunnel for that's more secure for those sessions..
Windows Server 2012Windows Networking
Last Comment
gopher_49
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
The thing is. I have domain resources that the server needs to access on the LAN. And... I want my SIP services to not deal with NATs. That's why I have the public NIC
Why not create a DMZ? Sure, you still have a NAT situation, but it would eliminate some issues, plus improve security.
ASKER
I have never gotten pfsense's NAT to work well with SIP... I have to use the sipproxd module and that doesn't meet my requirements.. I guess with that said I need to stick with my current config and move to a Fortinet virtual appliance versus the pfsense..
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I've tried everything with pfsense.. In this environment I had constant issues getting SIP to work... Will my current config work until I get a different firewall? So far I haven't noticed any issues..
For security's sake, I'd tell you to replace the firewall if there's no way to make pfsense work. As long as it's directly connected to the network AND the internet, that server is serving as a potential gateway to hacking the network.
What type of phone system is it anyway?
What type of phone system is it anyway?
ASKER
I have the Windows Firewall on.. The datacenter DDoS attacks and has some IPS/IDS. It's a unified communcations platform. The SIP stack I Asterisk I think.. But there is a lot going on there. I guess I'll look at getting a different virtual firewall.
ASKER
pfsense can be a pain in complex SIP environments...Due to this I'll just move to Fortinet's virtual firewall where I get vendor support.
Also agreed this should be a single NIC server with a firewall/router doing the public forwarding.