[PacketFence-users] inline, active directory clients

[mourik j. h. <he...@gm...>]

Hi,

Just out of curiosity I tried a quick test on a win7 workstation, put it
in the packetfence NAT segment, configured two DCs as DNS servers.

Browsing the internet works, but any samba/ad/cifs functionality is
lost. (ssh from the NAT to the DC's also works, so basic connectivity is
there) It's just the active directory functions thatseem NOT to work.

Before looking further into this... Is there anything that packetfence
does that would break this? (any iptables drops or so?)

I am under the impression that AD (contrary to nt4-domains) rely on dns
to 'work', so I assumed this would work.

All servers (DCs, fileservers) are public IPs, it's just the client that
is in the packetfence inline nat.

Is anyone doing this? Tips?

(I have read https://support.microsoft.com/en-us/kb/978772, and the last
paragraph sounds like what we're doing: "The only configuration with NAT
that was tested by Microsoft is running client on the private side of a
NAT and have all servers located on the public side of the NAT. The NAT
would also function as a DNS server.")

Regards,
MJ