This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Authentication with Radius blocked by server 2019 firewall

Hello, 

So I performed an in place upgrade on one of our domain controllers from 2012 to 2019, so that I don't have to worry about demoting and promoting blah blah blah. Before I upgraded the second DC I wanted to make sure our users can still authenticate when they VPN in using ipsec. So I removed the 2012 server from the authentication list in the XG firewall and noticed they won't authenticate. I RDPd in to both DCs to compare the Network Policy and it's pretty much identical. So I contacted support and they had me disable the server firewall and it worked. We then compared the rules and noticed they were the same on both 2012 and 2019, both allowing port 1812 to pass, but it works on 2012 and not on 2019. Has anyone else had the same issue? Not really understanding if both servers have the same firewall rule to allow that port, that it should work on both servers. 



This thread was automatically locked due to age.
Parents Reply Children