Any ways to fix the client listening port?

[Lin Yihui]

Hi,

Just to check if there is any ways to fix the client listening port?

As the client listening port is concurrently randomly assigned, the port is changed whenever the NetMonitor is launched on GUI.

Thanks in advance.

Topic

[Max Drown (Infor)]

Take a look at this document.

-- Max Drown (Infor)

[Lin Yihui]

Updated the server.ini as recommended.

[firewall]

rmi_registry_port=13019

host_server_default_port=34502

tunnel_port=34503

monitord_server_use=true

monitord_server_buffer_size=3000

rmi_exported_server_port=k1401ap0

Requested the firewall to be opened for ports 34502 and 34503. However, the GUI still takes some time to load (faster as compared to before(3mins after alteration))

From the document, it said that “If the port is specified, the connection is established from client to server”. However when checked, the client is still listening on random port. As for the server, it is listening on 34503. Why is this so? Shouldn’t it be the other way round where the client is listening on port 34503?

Note:

– Security server is not installed on the server.

– Screenshot attached is for the client side

[Bob Richardson]

Greetings,

We had received the following setting from INFOR support some time ago.

I think this must be hard-wired into the hostserver?

Anyway, it works for our remote clients so far. No new holes punched in our firewall as far as I know.

[firewall]

tunnel_port=14019

May the odds be ever in your favor!

[Author]

Replies