Desktop Central port use (Patching, Remote Controle, Remote File Sharing)
Hye people off the forum,
I found some good information that can be useful to some people.
Currently I'm experimenting with Desktop Central in a small test environment. I have tested some patch functions, Remote Control en scan/inventory off PC. Everything has worked when adding some ports to the firewall rules. But the Remote Control keep failing.
On the GUI web-interface it sayd: "Please wait...Establishing remote control connection on -'computer name' ". On the target PC you get something like: 'cant establish connecting, use/dont use proxy'. When you wait 10-20sec you get the message on the GUI web-interface: "Web Socket Connection terminated. Error: Abnormal Closure.Read KB" with a link to there.
BUT when you disable the server, where Desktop Central is running on, firewall. Everything seems to work. WEIRD.
So the investigation start. The port the are used (found there on this forum) are: TCP 8020, 8027, 8031, 8383, 8443. But when adding this port, this doesn't work. After use-sing range port numbers en narrow it don't by testing and testing. It revealed that it used the port 8082 (registered for us-cli - Utilistor (Client) by Andy_Brewerton).
My question, why this port????
I found some good information that can be useful to some people.
Currently I'm experimenting with Desktop Central in a small test environment. I have tested some patch functions, Remote Control en scan/inventory off PC. Everything has worked when adding some ports to the firewall rules. But the Remote Control keep failing.
On the GUI web-interface it sayd: "Please wait...Establishing remote control connection on -'computer name' ". On the target PC you get something like: 'cant establish connecting, use/dont use proxy'. When you wait 10-20sec you get the message on the GUI web-interface: "Web Socket Connection terminated. Error: Abnormal Closure.Read KB" with a link to there.
BUT when you disable the server, where Desktop Central is running on, firewall. Everything seems to work. WEIRD.
So the investigation start. The port the are used (found there on this forum) are: TCP 8020, 8027, 8031, 8383, 8443. But when adding this port, this doesn't work. After use-sing range port numbers en narrow it don't by testing and testing. It revealed that it used the port 8082 (registered for us-cli - Utilistor (Client) by Andy_Brewerton).
My question, why this port????