Horizon failed to connect to the server что делать
New horizon 6.0 installed.
Connection server freshly installed.
When trying to connect from horizon client gives straigt away the error "error: a network error occured"
I can ping and telnet 443 to connection server from view client.
I selected "do not verify server identify certificates" > still same issue after
View client logs give logs below.
2015-09-21 12:38:35.989+00:00 ERROR (181C) [WinCDK] RebrandingPref::LoadCertFile : Failed create new BIO from cert file: C:\Program Files (x86)\VMware\VMware Horizon View Client\rc\rebranding\vendor.crt.
2015-09-21 12:38:35.989+00:00 INFO (181C) [WinCDK] RebrandingPref::CheckRebranding : Could not find the HashAlg setting in the file signature64.conf.
2015-09-21 12:38:35.989+00:00 ERROR (181C) [WinCDK] RebrandingPref::VerifyCert : Invalid parameter.
2015-09-21 12:38:35.989+00:00 ERROR (181C) [WinCDK] RebrandingPref::CheckRebranding : Failed to verify cert.
no other errors in the log,
but certificate shouldn't be a problem..
disabled proxy server in internet options in windows > still same issue after.
firewall in the client desktop is off.
same issue on 2 win8 and win7 added to our domain.
I tried to install view client in a VM win8 not added in our domain, this works ok. ( BTW I have same cerficate error in the logs there )
=> how to troubleshoot further what prevents horizon client to connect on my machines connected to the domain ?
Бесконечное подключение к Horizon Life иногда вылазит ошибка "Не возможно подключится к сессии", в приложение Xbox написано что "Доступ к серверу" - Заблокирован.
[Edit - Translation] - An endless connection to Horizon Life sometimes gets an error "It is not possible to connect to the session", the Xbox application says that "Access to the server" is blocked.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
Report abuse
Harassment is any behavior intended to disturb or upset a person or group of people. Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect. Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software. Unsolicited bulk mail or bulk advertising. Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation.
Horizon failed to connect to the server что делать
- VMware Technology Network
- :
- Digital Workspace
- :
- Horizon
- :
- Horizon Desktops and Apps
- :
- Failed to connect to Connection Server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Why is it that when I try to access the connection server via IP, it says :failed to connect to connection server"but if FQDN of the server will be used; it connects fine.
Then another setup on another VLAN is observed and IP HTML access is successful.
And why does if connecting to admin window via IP address, a white box appears but is not encountered if FQDN is used.
Horizon failed to connect to the server что делать
- VMware Technology Network
- :
- Digital Workspace
- :
- Horizon
- :
- Horizon Desktops and Apps
- :
- Failed to connect to Connection Server ONLY in Chr.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I am unable to click on the HTML Access Client and get to my resources on the connection server through Chrome i get a "Failed to connect to Connection Server" But again this only happens in Chrome. Any suggestions?
JL1900- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I had the same issue. It works in all other browsers except Chrome. Also if you use the connection server's hostname instead of a dns alias or loadbalanced name it does work!
The issue (at least in my environment) was due to a security feature enabled by default in 7 and if working in a load balanced scenario (who doesn't? )
Читайте также: