N
NIV Consulting
I have a WatchGuard SSL VPN firewall, in which the VPN login's were
linked using LDAP to the Windows 2000 Active Directory (AD) accounts.
With this configuration, the users could login to the VPN using their
Windows 2000 AD credentials. When the Windows 2000 Server was
upgraded to Windows Server 2003, the AD no longer works with the
WatchGuard SSL VPN using LDAP. No configurations to the WatchGuard
SSL VPN firewall were changed prior to upgrading to Windows Server
2003. I have heard that this problem may be caused by Windows Server
2003's new Group Policy Objects (GPO) features, which may lock down
certain LDAP capabilities. If this is the case, which Windows Server
2003 GPO settings will need to be changed? If anyone who has such
knowledge and experience with getting Windows Server 2003's AD to work
with WatchGuard SSL VPN firewalls (using shared login credentials) can
help me, I would very greatly appreciate it.
linked using LDAP to the Windows 2000 Active Directory (AD) accounts.
With this configuration, the users could login to the VPN using their
Windows 2000 AD credentials. When the Windows 2000 Server was
upgraded to Windows Server 2003, the AD no longer works with the
WatchGuard SSL VPN using LDAP. No configurations to the WatchGuard
SSL VPN firewall were changed prior to upgrading to Windows Server
2003. I have heard that this problem may be caused by Windows Server
2003's new Group Policy Objects (GPO) features, which may lock down
certain LDAP capabilities. If this is the case, which Windows Server
2003 GPO settings will need to be changed? If anyone who has such
knowledge and experience with getting Windows Server 2003's AD to work
with WatchGuard SSL VPN firewalls (using shared login credentials) can
help me, I would very greatly appreciate it.