Active Directory authentication with Great Plains
Posted on 2006-07-03
We are experiencing a horrible performance hit with GP over Terminal Services with users authenticating to an AD server over a VPN. Our current configuration has a GP server and AD server in location 1 and an AD server connected via IPSec VPN at location 2. Location 1 runs like a champ when using TS to connect to Great Plains. Users that authenticate on the AD server in location 2 take upwards of 2 minutes before the GP login screen appears. During this period "Dexterity runtime" displays on the title bar of GP. This happens even if you are in location 1 and use a login ID from location 2.
Can you specifiy which active directory server is used for authentication for specific users?