OPC Connections to 800xA Surrogate OPC Server May Fail Due To Single-Label Domain Names
It has been seen in rare cases that it is not possible to browse the installed OPC servers, connect to any if they can be seen, or browse the namespace of (at least) the AfwDsOpcSurrogate OPC server, even from another 800xA node in the same system and on the same domain.Symptoms:
It has been seen in a few instances that 800xA systems existing in a domain using a single-label architecture can experience problems when trying to view, connect to, or read from the AfwDsOpcSurrogate OPC server. Best practice is to use the domain.subdomain syntax when first creating the domain (i.e. 800XADOMAIN.local, as opposed to just 800XADOMAIN).
Similar problems have occurred when the existing domain is indeed using the domain.subdomain syntax, but the client attempting to connect to the OPC server is joined to the domain by using the single-label name (i.e. joining 800XADOMAIN instead of 800XADOMAIN.local). This particular situation can be resolved by disjoining the domain, then rejoining using the proper syntax (800XADOMAIN.local).
For more information regarding single-label Active Directory domain names, see http://support.microsoft.com/kb/300684.