1

I run a bit of a complicated setup, let me give you a quick rundown:

Local pfSense Firewall -> IPSec Tunnel to AWS -> Server 2016 DC.

pfSense runs DNS in the local network, forwards domain queries to the DC via Domain Override.

If I am connected via ethernet, everything works fine. Soon as I use WiFi (UniFi), I can't run gpupdate or print. When running gpupdate I get the error that the computer name can not be resolved.

When I reboot the machine, I get a Netlogon ID 5719, the computer can't establish a safe connection with the DC.

Why does this happen, and why does it work via ethernet and not WiFi?

Andrew Schulman
  • 8,811
  • 21
  • 32
  • 47
ceofreak
  • 11
  • 1
  • Is your wifi on a different subnet? If so, do you use routing or NATting to go from the pfSense to the Server 2016? Probably worth updating your question with the answers – Phil Mar 12 '18 at 11:53
  • Hey Phil, no, the WiFi is on the same subnet. No, no natting towards the Server 2016. – ceofreak Mar 12 '18 at 13:54
  • can you post the output from "ipconfig /all" and "nslookup " for wired and wireless connections. where domain name is e.g. example.com – Phil Mar 16 '18 at 13:46

0 Answers0