Well there is your problem. In 6.0 it is a requirement that your Loggers must be Domain Controllers. This requirement isn't removed until 7.0 when the DC functions can be moved off to other servers.
You are going to have to promote the Loggers to Domain Controllers and re-run setup on all your servers (router, logger, pg's, aw's) and you may be ok. You are actually better off "uninstalling" all the applications on each server using ICM setup.exe > promote > then run setup again.
Loggers do not have to be domain controllers in 6.0. It is actually recommmended that application servers do not function as domain controllers. There is a generally unaccepted security risk of having a domain controller and SQL server on the same box. In 7.0 ICM integrates with Active Directory and it is required that the Loggers not be domain controllers. Seperate/existing servers will have be used for the domain and the Logger DC processes demoted and removed if installed.
1) Can you ping the Call Routers from the AW using the same names that you used in ICM setup on the AW? Don't bother using FQDNs, just put the hostnames in there (make sure that DNS actually matches the real hostname/IP Address of the servers). No need to use Hosts/Lmhosts files if DNS is setup properly. If you can ping,then you know that IP connectivity and domain/dns structure is right.
2) Can you 'net use' from the AW to the Call Routers? e.g. "net use * \\callroutera\c$". if so then you know that you have correct security rights at that level.
3) Root AW connectivity doesn't care about AW sitename at this point, what is the updateaw process saying besides the error?
The connection between the AW and the Call Router occur over the Visible network. Is the Call Router opening the correct ports on the correct Ethernet interface that the AW is trying to connect to?
Do your SQL servernames and NetBIOS names match on the AWs and Loggers?
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...