Allowing full, network-like access for users

Prev Next

When users connect remotely, their devices cannot communicate with the Active Directory (AD) Domain Controller. Connecting through AppGate ZTNA with limited application access does not change this — the user's device still cannot reach AD, even when the user authenticated using AD as the identity provider. As a result, services such as password changes and group policy updates do not work on the remote device.

To allow a user's device to communicate with AD, include the appropriate actions in a suitable entitlement. When configured correctly, the user's device behaves as if it were on the office LAN, even when connected through AppGate ZTNA. Because AD was not designed with this use case in mind, the requirements are extensive.


AD entitlement actions

Include the following actions in your AD entitlement. The Notes column indicates applicability:

  • D — Should already be in place in your DNS entitlements

  • L — Likely required for more recent network installations

  • S — May be required in specific situations

PROTOCOL

DIRECTION

PORT

APPLIES TO

USE

NOTES

TCP

UP

53

DNS

D

UDP

UP

53

DNS

D

TCP

UP + DOWN

42

Win NT

WINS

S

TCP + UDP

UP + DOWN

88

KERBEROS

L

UDP

UP + DOWN

123

WINDOWS TIME

S

TCP

UP + DOWN

135

RPC/EPM

L

UDP

UP + DOWN

137

Win NT

VARIOUS

S

UDP

UP + DOWN

138

Win NT

VARIOUS

S

TCP + UDP

UP + DOWN

139

Win NT

VARIOUS

S

TCP + UDP

UP + DOWN

389

LDAP

L

TCP

UP + DOWN

445

SMB

L

TCP + UDP

UP + DOWN

464

KERBEROS PW CHANGE

L

TCP

UP + DOWN

636

LDAPS

L

TCP + UDP

UP + DOWN

1512

Win NT

WINS REPLICATION

S

TCP

UP + DOWN

3268

LDAP GC

L

TCP

UP + DOWN

3269

LDAPS GC

L

TCP

UP + DOWN

5722

RPC

S

ICMP

UP

0-255

Win 2000/XP clients

GROUP POLICY

S

TCP

UP + DOWN

1024-5000

2003 and before

RPC Dynamically-assigned

S

TCP

UP + DOWN

49152-65535

2008 and later

RPC Dynamically-assigned

S