A Client Domain may not establish a connection to a Server Domain for several reasons, which might be:

•The Client or Server computer is not connected to a network

•The Server is not executing an E3 Server

•The Server's E3 Server does not contain the correct Domain, or the Domain was not started

•The Server Domain does not accept the user specified by the Client Domain

•The Client's or Server's E3 Server does not contain a Remote Domain license

•The Server's E3 Server version is an older one (2.5 or earlier)

•There is a firewall blocking the TCP/IP port used by REC, or the Client and Server TCP/IP ports do not match

•The Domain's alias does not exist in the Remote Domain configuration

When one of the previous situations occur, all Client links referencing the Domain are disconnected, as well as all Application.GetObject methods referencing the Remote Domain fail, that is, cause script errors. As soon as this problem is solved, Links must connect automatically. Application.GetObject methods, however, must be executed again.