A client has a TZ210 Sonicwall that we have been using for RDP and RDS connections. Currently they have a public ip of xxx.xxx.xxx.89. They recently purchased a new software that pulls tractor trailer load data from an App server to a website. They require the server have a different public IP and port 443 open to it so that it can pull the load data for display on the website. I assigned a public address object of xxx.xxx.xxx.91 from their block of static IPs from the telco. I then created a private address object for the App server. Then used the wizard to create the NAT policies and the firewall access rule. All seemed to work well with the website gettings it's data. Then their remote office which uses the xxx.xxx.xx.89 public IP for RDS connections back to the server at the main office. Apparently they started getting disconnected from the RDS about every 60-75 seconds. After some playing around with the settings I found that disabling the reflective NAT policy would then allow the RDS users to keep a stable connection. The App server won't talk with the website when the reflective policy was off. The App server would say it's public IP address was the xxx.xxx.xxx.89 IP address, were as with the reflective on it said it was xxx.xxx.xxx.91 like it should be. I cannot determine what about the reflective policy is causing the issue with the RDS connections. The RDS server is Windows Server 2012 R2 and the App server is Windows Server 2008 R2. They are two separate physical machines. I tried using a different port for the website, 8443 instead of 443 thinking that the redirection of the 443 was messing with the RDS authentication in some way, but the results were the same for 8443 as it was 443.
↧
