Thanks Lucian, your advice helped uncover the root cause of my issue :-)
(Sorry about the delay in the reply)
On 28/02/2024 21:06, Lucian Petrut wrote:
Hi,
I’d double check that the 3300 port is accessible (e.g. using telnet, which can
be installed as an optional Windows feature). Make sure
Thanks Robert (sorry about the delay in replying) :-)
On 29/02/2024 01:03, Robert W. Eckert wrote:
I have it working on my machines- the global configuration for me looks like
[global]
fsid = fe3a7cb0-69ca-11eb-8d45-c86000d08867
mon_host =
I have it working on my machines- the global configuration for me looks like
[global]
fsid = fe3a7cb0-69ca-11eb-8d45-c86000d08867
mon_host = [v2:192.168.2.142:3300/0,v1:192.168.2.142:6789/0]
[v2:192.168.2.141:3300/0,v1:192.168.2.141:6789/0]
Hi,
I’d double check that the 3300 port is accessible (e.g. using telnet, which can
be installed as an optional Windows feature). Make sure that it’s using the
default port and not a custom one, also be aware the v1 protocol uses 6789 by
default.
Increasing the messenger log level to 10 might
