Results 1 to 2 of 2
  1. #1
    Untanglit
    Join Date
    Jan 2019
    Posts
    16

    Default Primary/Secondary connections

    We've been using Directory Connector successfully for over a year and it's worked well. Recently the thought occurred to me that each of my UT AD connections have one connection to the AD server in their local network. The question is, what happens when that AD server is down for whatever reason? Is it possible to add a second AD connection and keep UT properly authenticating?

    For example, I have a UT device with a connection to AD server at 10.0.0.20. Let's say 10.0.0.20 goes down for a period of time. UT won't authenticate users during that time. Can I add another, secondary connection that might be at another physical location, across a WAN link? Thus can I have:

    domain.net cn=users host=10.0.0.20
    domain.net cn=users host=10.0.1.20

    And if 10.0.0.20 is down authentication will continue because there's a secondary connection?

  2. #2
    Untanglit
    Join Date
    Jan 2019
    Posts
    16

    Default

    Ok so I know that Directory Connector is fine reaching across the WAN to another DC in another subnet. Again, will DC fail to the next entry in the list? If so, what is the timeout?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2