I'm installing a VIEW 5.0 security server and I'm trying to pair it with a view 5.0 connection server. I've generated a new pairing password from the view administrator console but when I insert it during the security server installation I get the error INVALID PAIRING PASSWORD, I've tried to generate some different passwords but the message is always the same. What can I do to solve this problem?
Do you already tried using CTRL+C (password configured on console administrator) and CTRL+V to put in Security Server) ? With ctrl+c and ctrl+v if you´ve differente layout configured into Guest Os of keyboard, might works.
If possible, try restart services
Before installing the VMware View Security Server, the Security Server pairing password must be configured. This is a one-time password that allows a Security Server to be paired with a specific VMware View Connection Server instance.
To configure the Security Server pairing password:
Thanks but I'm doing all the steps noted. I do not wait the pasword expiration so I can't understand why I have this problem.
Do you already tried using CTRL+C (password configured on console administrator) and CTRL+V to put in Security Server) ? With ctrl+c and ctrl+v if you´ve differente layout configured into Guest Os of keyboard, might works.
If possible, try restart services
CTRL + V is not allowed inside the password field. Anyway restarting the vmware view connection server service and generating a new password solved my problem. Before I tried to reboot the connection server but was not useful. Thanks .
I'm having the exact same issue with View 5.1 security server pairing. Did you disable the IPSEC global setting and disable Windows firewall? I can't get the security server to pair no matter what I try.
I disabled the windows firewall. Did you try to reboot the connection server ?
Yah. I rebooted my connection server and the security server and still no go. I even disabled the firewall on both the connection and security servers. I'm stumped . I wonder if it's a bug?
It always the stupidest things . I had the wrong installable (version 5 instead of 5.1).
I had similar issue. Restarting the connection server fixed it.