CMS Supervisor - Conection to host was refused

[raska1]

Re connection to host refused

Hi,

The problem was I wasn’t able to login using SSH (CMS supervisor V17.0), 'connection to host refused'. Network, port 23 worked just fine. Installed wireshark on my PC and found that every time when I tried to login using SSH, CMS supervisor tries to establish SSH session with one of my media gateways. WTF. Searched registry by media gateway’s IP and found that it’s default IP in Putty! For some reasons CMS gets settings for SSH session from Putty’s SshHostKeys. Renamed HKEY_CURRENT_USER\Software\SimonTatham\PuTTY to PuTTY_1 and now everything is working just fine.

I think before trying any other options install wireshark and check what server your CMS supervisor is trying to connect to.

Artem

[bcanto]

Look at the messages file in /var/adm . You might see a message that states something like "connection refused (name/address mismatch).

I'm not sure of the exact mechanism at play but cms tries to do a dns lookup on the incoming connection. If it doesn't get the response it is expecting, it refuses the connection. I suspect that the initial connection from the client passes its hostname somehow and then cms does a dns lookup to make sure things match.

[chamber2236]

I had the same issue. Was a bad registry key in the HKEY_CURRENT_USER>Software>SimonTatham>PuTTY>Sessi ons section of the registry. I believe it was in either the Default or Default%20Settings key. Don't remember exactly which value was the issue but it had a host name or IP that when I removed it there was no longer an issue.

[helmse]

Thanks!! Changing Default%20Settings key fixed it for me. Incidentally, I believe this fix would only apply to people who are using Tutty.

[vorobi]

Hi,

The problem was I wasn’t able to login using SSH (CMS supervisor V17.0), 'connection to host refused'. Network, port 23 worked just fine. Installed wireshark on my PC and found that every time when I tried to login using SSH, CMS supervisor tries to establish SSH session with one of my media gateways. WTF. Searched registry by media gateway’s IP and found that it’s default IP in Putty! For some reasons CMS gets settings for SSH session from Putty’s SshHostKeys. Renamed HKEY_CURRENT_USER\Software\SimonTatham\PuTTY to PuTTY_1 and now everything is working just fine.

I think before trying any other options install wireshark and check what server your CMS supervisor is trying to connect to.

Artem

Thx, this helps to me