RMAService Error: cannot open port #....

jboardman · Post by **jboardman** » Thu Jun 28, 2007 1:45 pm

RMA agents that have been running for months will randomly say they cant open the port anymore. We end up having to go up one number and redo the config on the firewall and server. This is a pain is there anything else we can do.

KS-Soft · Post by **KS-Soft** » Thu Jun 28, 2007 1:49 pm

Could you please check what application uses the port?

Regards
Alex

jboardman · Post by **jboardman** » Thu Jun 28, 2007 1:58 pm

I guess thats the problem

We dont know what app would be taking the port and I dont know how to tell.

I have one agent that about once a month I flip between 1055 and 1056

We have about 60 RMA agents out there an this is happening to about 3-5 a month.

Its frustrating.

KS-Soft · Post by **KS-Soft** » Thu Jun 28, 2007 2:01 pm

You may use "netstat" command line utility to figure it out, e.g. "netstat -nao".
May be problem is related to Windows RPC and port mapping... try to use port below 1023 (e.g. 999) or higher numbers (e.g. 5555)

Regards
Alex

jboardman · Post by **jboardman** » Thu Jun 28, 2007 2:19 pm

its listed

TCP 192.168.1.11:1026 192.168.1.11:1058

its going to itself on another port

1058 is what RMA is set to

KS-Soft · Post by **KS-Soft** » Thu Jun 28, 2007 2:48 pm

TCP 192.168.1.11:1026 192.168.1.11:1058
1058 is what RMA is set to

1) If RMA is configured to use port 1058, this record should look different because netstat shows local address/port then remote address port
2) You should see more records, not just one
3) If you are using Windows XP or Windows 2003, you should see application that uses port
4) Also you should see status of the connection
I think this record tells you about some other application, however I cannot be sure because you do not provide enough information.

1058 is what RMA is set to

No, it does not. RMA does not change assigned port by itself

Regards
Alex

jboardman · Post by **jboardman** » Thu Jun 28, 2007 2:53 pm

netstat -nao doesnt work only -na

this is a windows 2000 server.

I see

TCP 192.168.1.11:1026 192.168.1.11:1058
TCP 192.168.1.11:1058 192.168.1.11:1026

jboardman · Post by **jboardman** » Thu Jun 28, 2007 3:25 pm

As these break we are going to try higher and lower port ranges and see if that helps.

KS-Soft · Post by **KS-Soft** » Fri Jun 29, 2007 6:35 am

netstat -nao doesnt work only -na
this is a windows 2000 server

Then you may use our software: IP-Tools
http://www.ks-soft.net/ip-tools.eng/index.htm
Connection Manager utility shows process information even on Windows 2000

Regards
Alex