Stefan:

Thanks for the analysis and information.  Why am I not surprised that the "No error" came from Windows!? 

I tried some of your suggestions with the following results:

1.  Ping ==>= works as expected on the failing machine; that is, can successfully ping "max13"  I also can ping successfully in the reverse direction; that is, from "max13" to my "client" machine.

2.  NSLookUp ==>does not work on any of the 3 machines.

3.  Added the computer name "max13" to HOSTS file; ==> observed no change in behavior (i.e., still fails)

I did notice that on the 2 machines that function as desired that there is no anti-virus software installed, while on the non-funcational machine there is A-V SW installed.  I am able to bring up eLOG via the browser on the non-functional machine, so am unsure if the A-V SW is a factor; that is, why does ELOG via browser work as expected, but not via command line. 

QUESTION:  does command line ELOG connect differently than ELOG through the browser?

I ask this question for perhaps the A-V SW *is* blocking some port or whatever, and I will need to ask our IT department how to remove such a restriction.

ELOG connects in the same way as the browser, but it is a different program. I have seen some firewalls which explicitly exclude browsers in firewall rules. So it might well be that yours blocks ELOG but not your browser. So give it a try and disable it.

Since both my machine and the Elog server PC are inside my company's "security zone", I am not running a firewall on my machine.

For what it's worth:  in trying to research the "No error" message, I did come across this information on MS's website; that is, their statement is:

The gethostbyname function retrieves host information corresponding to a host name from a host database.

Note  The gethostbyname function has been deprecated by the introduction of the getaddrinfo function. Developers creating Windows Sockets 2 applications are urged to use the getaddrinfo function instead of gethostbyname.

SOURCE:  http://msdn2.microsoft.com/en-us/library/ms738524.aspx

Preset ticket = TCK-#####

Preset on reply ticket = TCK-#####

With this information I cannot diagnose the problem. I would recommend you to run the elogd on the mirror server in interactive mode with the "-v" flag, so you see all net traffic. Maybe this sheds some light on the problem.

  Hello,

The server hang at this point :

ID362  : 45F505AF26644D7F71A2AF6E9822554D
Cache  : 45F505AF26644D7F71A2AF6E9822554D
Remote : 45F505AF26644D7F71A2AF6E9822554D
 

I can't stop the process with ctrl+c

Kind regards

Stéphane

No, that does not help me to come to a conclusion. So I have no idea what's going on. When you do mirroring, you can start the synchronization from both server sides. Can you maybe try to do that from the "other" server? Maybe you have some firewall problem.

How can I put the output in a file to send it to you ?