Connection

Hi, 

The router on the workstation needs to be able to connect to the router on the server and ideally the router on the server needs to be able to connect to the router on the workstation in order for downstream message to delivery to be instant.

Basic connectivity tests would be:

From the client:

telnet server 8192

You should receive back the IOR of the server router.  Again from the client:

telnet server 8194

This is the SSL port the server router is listening on and the one pointed to by the IOR as read from 8192 as per above.  It will connect but nothing will be displayed.

Both ports are TCP.

To test the server to client, from the server you can run:

telnet client 8194

This test should work if the server is going to be able to notify the client to come and get a message/messages from the parent router, rather than waiting for the client to poll the server router for messages which happens ever 15 mins +- 50%.

The address(s) the client will use to contact the server will be in the router registry key (ParentAddress).  By default, if the server has a static IP at install of the management server it will be IP,FQDN,NetBIOS.  It will try in that order.  If the management server is DHCP at the time of install, the client will reference the server using FQDN, NetBIOS.

Regards,

Jak

Hi, 

The router on the workstation needs to be able to connect to the router on the server and ideally the router on the server needs to be able to connect to the router on the workstation in order for downstream message to delivery to be instant.

Basic connectivity tests would be:

From the client:

telnet server 8192

You should receive back the IOR of the server router.  Again from the client:

telnet server 8194

This is the SSL port the server router is listening on and the one pointed to by the IOR as read from 8192 as per above.  It will connect but nothing will be displayed.

Both ports are TCP.

To test the server to client, from the server you can run:

telnet client 8194

This test should work if the server is going to be able to notify the client to come and get a message/messages from the parent router, rather than waiting for the client to poll the server router for messages which happens ever 15 mins +- 50%.

The address(s) the client will use to contact the server will be in the router registry key (ParentAddress).  By default, if the server has a static IP at install of the management server it will be IP,FQDN,NetBIOS.  It will try in that order.  If the management server is DHCP at the time of install, the client will reference the server using FQDN, NetBIOS.

Regards,

Jak

So basically:

Telnet server 8192 is the correct approach to achieve connectivity from Workstation to MR on the Server?

well it will make a connection to the remote port (8192) on the server to test nothing is blocking the port, a remote process can connect to it and that the IOR (once parsed) is as expected.