Forum Discussion
Oxenburger_1420
Nimbostratus
NimbostratusMultiple Domain Support not working on APM
Hello,
I'm having a bit of a problem with APM and cross domain support using AD authentication.
There are multiple AD domains in our environment and webmail is currently setup through our ...
Oxenburger_1420Nimbostratus
NimbostratusHi Mike,
I also captured some AD traffic from F5 and is showing that dc1 is unreachable.
Pings from F5 to dc1-dc3 are showing reponses from dc2 and dc3 but not from dc1.
If it is a reachability problem is there a way to get the F5 to only target specific KDC's in domain-b. Could this possibly be the issue.
By that I'm refering to the message from the APM logs where it is appears to derive the KDC list using DNS discovery.
May 22 10:45:46 LB-APMDEV01 debug apd[32536]: 0149017c:7: c5b29dcf: AD module: Domain Controller is not specified for domain 'DOMAIN-B.INTERNAL', KDCs will be discovered using DNS
May 22 10:45:46 LB-APMDEV01 debug apd[32536]: 0149017d:7: c5b29dcf: AD module: Adding 'svnewcastleretr.domain-b.internal' to KDC list
May 22 10:45:46 LB-APMDEV01 debug apd[32536]: 0149017d:7: c5b29dcf: AD module: Adding 'dc1.domain-b.internal' to KDC list
May 22 10:45:46 LB-APMDEV01 debug apd[32536]: 0149017d:7: c5b29dcf: AD module: Adding 'dc2.domain-b.internal' to KDC list
May 22 10:45:46 LB-APMDEV01 debug apd[32536]: 0149017d:7: c5b29dcf: AD module: Adding 'dc3.domain-b.internal'
Regards,
David
