CMS Supervisor - Conection to host was refused

[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

[helmse]

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

[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.

[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.

[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

[ekepne]

CMS Supervisor "Connection to host refused" - WORK-AROUND

Everyone,
During the course of troubleshooting within my Enterprise network, we found two "work-arounds" that work.
First, let discuss the cause of this issue as we have found it to be. When a user's password expires or is force reset and their account is in a password reset state this issue happens on select machines.
The two solutions for this are outlined below:

1. Server-side: Adding the clients hostname and ip address to the HOSTS file located in the root/etc folder on the CMS server.
2. Server-side: We use ssh and deny all other forms of communications, so telnet was not a real option for us on an Enterprise scale, but we were able to add the clients IP address to the HOSTS.ALLOW file located in the root/etc folder on the CMS server and then go back and comment it out after password change.

Both of the above stated methods require root access to the CMS server, which can be gained by using Putty or any other ssh client to get to the server and using the "su -" command and password to gain access to the system root. We also used "VI" editor to modify both of the HOSTS and HOSTS.ALLOW files. If you are not sure how to use these editors please Google "Basic VI Commands Linux" and you should be fine. I hope this helps anyone who is having this issue. If you have any questions or would like more information please comment and I will do my best to respond accordingly.

[shaikht]

You can try folllowing also if it works:

Try to connect using Manual in option option rather than auto in.

If it is occuring only on one PC, you can try to re-install supervisor and see if it make some difference. Follow below steps:
) Start, Settings, Control Panel, Add/Remove Programs
2) Remove CVS software
3) Go to Windows Explorer
4) Do a search/find for cvsup*.cfg
5) When found, delete all instances and dump them from your Recycle Bin.
6) Go into Start, Run window
7) Type in "regedit"
8) Registry Editor window opens
9) HKEY_LOCAL_MACHINE (drill down)
10) Go to SOFTWARE
11) Look for Avaya folders and delete anything related to Supervisor.
12) Reboot PC
13) Reinstall CVS Software

[shaikht]

Hi,

For windows 7, you can get supervisor user profile at:
C:\Users\user_name\AppData\Roaming\Avaya\CMS Supervisor R17\Profiles

While uninstalling, have you removed all supervisor registries?

Issue is only from PC or you are not able to login from all PC's?

[nguyenhoangh]

Thanks for respond!

I fixed my problem by adding the IP and hostname of my PC in /etc/hosts of CMS

Regards

[ebyh]

CMS Supervisor - Conection to host was refused

We had the same issue last year with our Win7 upgrade as well. It was absolutely maddening! The solution is a little over my head, but here's a snippet I copied from an email which may help point you in the right direction:

"The most important step is the per-user initial configuration. The user must be placed in Policy Technical group as the app writes to the registry in a way that is prohibited by Policy Standard.

We have found that with a messed up install, completely de-install, then reinstall as admin, then login with the Policy Technical user and run the app and configure the connection (make sure to delete any existing connection to [the server] first... then add it back in...)"

Best wishes!

[nguyenhoangh]

CMS Supervisor - Conection to host was refused

had to erased my profile from the PC wich has the problem, after create again the profile CMS supervisor could connect to the server

Hi,

I has the same problem with you! Can you help me on that?

I tried to un-install and re-install but it doesn't help. I cannot find profile in the PC which install CMS Supervisor to delete and re-create it!

Thanks so much

[tikho2]

Hi! Have same problem on my PC, cleaned everything from registry --> didn't help.
Same mistake occures - Connection to host was refused, so i use tutty to connect and use system.

[ismab12]

had to erased my profile from the PC wich has the problem, after create again the profile CMS supervisor could connect to the server

[dave1]

From the PC that you are having the problem with can you check if the DNS is the same as on the PC on which the Supervisor is working.

You mentioned that the PC on which the Supervisor works is in the domain. Can you check if the PC on which you are facing the issue is also in the same domain.

[ismab12]

Thanks shaikht

i have already erased the files and made no difference ..... i think i have to erase all my profile from the PC and create it again