The connection to the remote computer ended ошибка vmware horizon client
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Digital Workspace
- :
- Horizon
- :
- Horizon Desktops and Apps
- :
- connection to the remote computer ended
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I setup a new security server in the dmz. from the dmz I can connect and bhring up a list of vms to connect to with the view client. but when i connect to the vm it tries to connect bring up the window and exits
The connection the the remote computer ended.
markbenson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Thanks for letting us know what it was.
mittim12
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
That sounds like one of your ports is blocked. What version of View and what protocol are using?
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
i have opened up all access between the connection server and the security server. I am using 4.6 pcoip
mittim12
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
are you saying I should open up 4172 to the entire vdi desktop network?
eeg3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
If you want to use PCoIP, yes. It is not required for RDP. The guide that mittim12 posted is a great resource to follow.
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
from the view client in the public internet. I should open up 4172 to the entire public?
markbenson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Don't expose your virtual desktops directly to the Internet. The worked example of how to set this up is in the video (about 18 mins in).
mittim12
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
If you check out the document listed earlier it will give you all of the ports and which ways to allow access.
Also keep in mind that PCOIP is already encrypted.
Sent from my iPhone
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
i opened tcp/udp 4172 from the security server to the vdi desktop lan. but still cannot pcoip from dmz to my vdi desktop
spgoeh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I tried cheking the box USe PCoIP Secure gateway for pcOIP connections to desktop but now I cannot even pcoip from the same lan as the view connection server. It says connection timed out. same things from dmz.
when i uncheck that box I can pcoip from view connection server lan
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
where are the logs located?
spgoeh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
My mistake, is only IP and port number.
What IP you assign to PCoIP secure gateway is external/internal IP?
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
npeter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Where did you set up PCoIP ExternalURL with dmz ip in Admin UI? for connection server entry or Security server entry?
It should be for security server entry. Leave the connection server PCoIP ExternalURL entry with its own ip:4172.
Also make sure you have firewall rules set as mentioned in the doc shared above.
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
yes I changed it on the vcs to its own ip and the security server to its dmz ip. but still cannot connect from dmz. it brings up the window and dies
npeter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Do you have these firewall rules in place ?
Client to Security/Connection Server
TCP 4172 from View Client to View Security Server.
UDP 4172 in both directions
Security/Connection Server to Agents
TCP 4172 from View Security Server to View Agents.
UDP 4172 in both directions
tdubb123
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
since client and security server are on the same dmz net, there is no firewall between them.
I allowed all traffice from security server to view connection server. I verified that it works by telnetting to the ports and they di respond
for outbound udp from vm to outbound I am not sure. how can i test this?
In the vdm log on the client
error raising port: unable to connect to: ip of the vdi vm:4172
npeter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
That error indicated client cannot connect to view desktop vm for pcoip connection.
->I allowed all traffice from security server to view connection server. I verified that it works by telnetting to the ports and they di respond
You should allow traffic on 4172 from/to security server from view desktop vm.
Also you should enable PCoIP Secure Gateway option. as Mark Benson pointed out below
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Digital Workspace
- :
- Horizon
- :
- Horizon Desktops and Apps
- :
- Horizon View 7 Error "The connection to the remote.
RickJSalt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I have a lone user who is unable to connect to a virtual desktop with the Horizon View 7 client. Others on the same network are able to access machines in the pool, but he gets an error "The connection to the remote computer ended." I uninstalled and reinstalled the client, re-confirming connection server settings and whatnot, but with the same outcome. He has two pools available to him in the client and the other one will deliver a desktop when it's clicked on. The pool he uses the most gets the error. He is able to get a machine via BLAST, using HTML access, so I have a work-around in place. However, I would like to know what the cause of the error might be. Any and all guidance will be appreciated. Thanks!
MatthewDay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I've seen this error before where the Horizon Client version was not compatible with the Agent version. But, sometimes these horizon errors can be vague without the context of the logs to back them up.
1. Is it possible to assign a test user permissions to the desktop pool that's having problems and then log on as the test user? Maybe do it once from a different client PC and then again on the problematic users client PC. This should tell you whether the problem is specific to that client PC, or anybody who accesses that desktop pool.
2. Any possibility the Agent versions are different on the 2 desktop pools he can access? Its weird that one works and the other doesn't.
RickJSalt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Well, I can get to the pool from my computer using the Horizon View Client, but now I've had two other users report the same error. I have them using the HTML client for now, and I'm checking the parent machine and going to snapshot it again and then recompose the pool against that, and I'll check the pool settings. As for question number 2, I have the same agent on my computer as that on other users, so it shouldn't be an agent mis-match issue. It's bizarre since it's a rather spontaneous issue; the pool has been running fine ever since I created it months and months ago.
RickJSalt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I should also note that I have another floating pool that is set up the same way, for another group of users. Some of those users also have access to the pool that is having this issue. They can get a machine from the other pool with no trouble at all, so I'm befuddled. I am recomposing the pool tonight and we'll see what happens tomorrow.
alienjoker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Can you confirm if your pool is using disposable disks? The reason I ask is that I've experienced the exact same problem and after hours of root cause analysis with ProcMon, found that the logging levels on the RDPBridgeservice for TPAutoconnect were filling up the disposable disk. This then prevents the PCOIP service from being able to run successfully and the only way back onto the desktop was with HTML access.
I have existing SRs open with VMware on this as I've warned them that their logging levels are too aggressive in Horizon 7.0.x
RickJSalt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
You may have hit the nail on the head; I do in fact use disposable disks. I have them set to 2GB for each machine in the pool. Have you heard back from anyone regarding this issue? I'll do some poking around to see if there is a way to resolve this and reply back here if/when I figure it out.
Thanks for your input!
RickJSalt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Spoke too soon; had a user call to say she was getting a black screen when logging into a VM. I reset all the powered up machines in the pool and went to her desk to try again. No luck. Tried getting via HTML with the same result, then a message came up to say that the machine had been disconnected. I have nuked almost all the snapshots, but I think I will try deleting the snapshots altogether and recomposing the pool against a new snapshot of the parent.
alienjoker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Yup, lots of head scratching at VMware as you cannot turn down the VDM logging lower than what its already set at, yet the TP-AutoConnect logs grow exponentially at around 500KB every 10 minutes. I worked it out that over a 7 day Window, that with 1000 users, this will consume circa 500GB of unplanned capacity, not to mention the unwanted IOPs.
I have the following SR open: 16260979110
A quick test would be to free up some space (no more than 10mb needed just get a session back up again) on the disposable hidden drive and then see if you can reconnect to a disconnected session. What you'll find is that once the logs grow and the drives fill up again, the PCoIP session will disconnect.
As a workaround, I've now dumped using disposable disks, bumped up the size of the Master template to compensate for the relocated Pagefile,sys until VMware come up with a way to disable logging. Not ideal as we're still getting the hit on capacity and IOPs until the desktops are refreshed on logoff.
Тут собираю интересное по интересующей меня теме виртуализации.
- Главная страница
- Книга по vSphere
- Performance - как правильно мониторить
- VMware Certification
- Курсы VMware
- Подборка важных материалов
Рекомендую
20 Replies
Firewall issue
Make sure all the requiered ports are added.
Also Check the windows firewall settings of the computer.
We had this issues when doing it on
VMView 4.6.
That's what I thought too, but all our firewall settings match the installation guide and Windows Firewall is disabled on everything. Perhaps they've changed something in 5.0, still looking.
LI DataCom Inc. is an IT service provider.
I've seen this in my recent setups.
- Are you trying to connect using RDP or PCOIP?
- Do you have a banner displayed before the user can login?
StorageNinja
You have a signed cert on your security server?
for demo purposes using a VPN client works just fine (although we use the security service).
Anthony - We're using PCoIP but we've tested with RDP also. same result. No banners.
John - We do not have a signed cert, as this is just a pilot. I haven't tried a vpn yet, I'll setup ssl vpn on our firewall with a vpn client and then try again.
Another theory I've heard is that the dns record for the public IP we're using for our security server isn't resolving and therefor causing the connection to ultimately fail. We previously had a different application on that IP, so we're also working on getting a new dns name to resolve to that old IP. Anyone heard of this being a problem?
yes and also you need a gateway in this new version (actually since VMVIEW 4.6)
StorageNinja
You don't need the gateway unless you want to connect without VPN I Belive.
LI DataCom Inc. is an IT service provider.
We recently upgraded our infrastructure to VCenter/View 5. The Security server was working for a few days and i just found out that it is now doing the same thing as you. I will be calling VMware support tomorrow to fix the issue. I'll post my findings once i talk to them.
Ok, so our problem was that port 4172 (PCoIP) was open for TCP on the Security Server, but not UDP. We had to create a separate rule for that (Fortigate). Also I did not have policies established between the security server and VDi's directly. I thought this was handled through the connection to the VSphere server, but that is not the case. Here are some great articles that helped me resolve this:
have a nice time with you vmview :)
We are currently struggling to get a VMware View security server working behind a FortiGate firewall (version 4.0 MR3) as well. We are getting the black screen and timeout when a remote client tries to connect to a desktop. Would you be able to tell me how you have the Policies, Services, Virtual IP, and NAT set up for connections to and from the VMware View security server?
VMware View 4.6 PCoIP Secure Gateway Troubleshooting
On March 13, 2011, in vCenter Server, View, Virtualisation, by admin
Following on from a recent VMware View 4.5 to 4.6 upgrade I thought I would include a list of the resources I used to troubleshoot connectivity issues.
First off read the View 4.6 Upgrades guide, this lists out the steps required to upgrade all components of the View infrastructure including how to upgrade the View Transfer server, the Composer server etc.My own upgrade was with a single connection server, a security server, a vCenter Server with View Composer and the Active Directory back-end servers.
If you follow the instructions in this guide then the upgrade process should be relatively painless.
The key steps are
1. Make backups and record various configuration and system settings
2. Halt scheduled tasks.
3. If end users are using View 3.1.x or 4.0.x Client with Offline Desktop or View 4.5 Client with Local Mode, ask them to check in their View desktops.
4. Upgrade View Connection Server.
5. Upgrade the View Security Server. (see below)
6. Upgrade Transfer Server instances.
7. Upgrade View Composer.
8. Upgrade the View Agents on the template virtual machines
9. Upgrade the View Client software or download the iPad View 4.6 PCoIP client.
The View Security Server has to be Windows Server 2008 R2, which is a 64-bit server. The connection server can remain Windows Server 2003 32-bit or you can upgrade it to 64-bit version of Server 2003 or 2008.
When configuring the PCoIP secure gateway element you can either install this on the View Connection server or on the View Security Server which can then be installed in a DMZ. The upgrade wizard will prompt for the external PCoIP secure gateway server settings during setup, ensure you enter externally accessible information in here. When you pair the security server to the connection server this information will appear in the connection server web interface. Now all you need to do is go into the view connection server settings and enable the PCoIP Secure Gateway server option.
If you pair a Windows 2003 connection server with a PCoIP server you may get this error after enabling PCoIP support. Warning: This connection server or one of its paired security servers does not have a PCoIP Secure Gateway installed. Ensure that this configuration is correct for your intended use of PCoIP.
This is normal as the 32-bit connection server doesn’t understand the PCoIP element of the View Secure Gateway as it doesn’t have that role installed. It will work fine.
Provided all these steps have been followed the security server should be working as expected.
If not check the following firewall ports are correctly configured.
PCoIP between View Client and Security Server
• TCP 4172 from Client to Security Server
• UDP 4172 from Client to Security Server
• UDP 4172 from Security Server to Client
• TCP 443 from Client to Security Server
• UDP 443 from Client to Security Server
• TCP 80 from Client to Security Server (If not using SSL, not recommended)
• UDP 80 from Client to Security Server (If not using SSL, not recommended)
PCoIP between Security Server and virtual desktop
• TCP 4172 from Security Server to virtual desktop
• UDP 4172 from Security Server to virtual desktop
• UDP 4172 from virtual desktop to Security Server
Useful Links
Check out Paul Slager’s excellent upgrade guides for step by step instructions
VMware View 4.6 Upgrade & PCoIP Security Server Configuration – Part 1
VMware View 4.6 Upgrade & PCoIP Security Server Configuration – Part 2
Troubleshooting PCoIP Secure Gateway (PSG) issues
Setting up PCoIP Remote Access with View 4.6
View 4.6 Architecture Planning Guide
iPad View Client App
Thanks, Manny, but in our case, this is a clean new install of VMware View 5, not an upgrade. I have set up all of the firewall ports as per the document, and I have narrowed down the problem to an issue with the outer firewall and/or NAT settings. Where I seem to need help is in the Fortinet-specific firewall and NAT rules, which Hayes4 must have working.
Популярные посты за все время
Хе хе. Я тут овладел новым джедайством (Денис, спасибо за наводку). Посмотрите на эту картинку: На первый взгляд скриншо.
Intel купил McAfee. по рассказам знающих тему все было вот так: - Так. Нам нужен антивирус. Купите кто-нибудь McAfee. Вечером: .
В двойку лидеров по известности среди продуктов VMware входит программа VMware Workstation. Это весьма эффективное средство создания вир.
В vSphere 5 появилась такая штука как Web Client – по сути, старый добрый web-интерфейс, но слегка в новом обличии. Если в тройке и четве.
Про View
Интересные заметки про VMware View:
В ходе тестирования работы VMware View 4.6 с платформой виртуализации vSphere 5 (в составе vCenter 5 + ESXi 5) мы с моим коллегой Mikhalych обнаружили интересную особенность — при работе пользователя в сессии VMware View по протоколу PCoIP, администратор платформы виртуализации может подключиться к консоли виртуальной рабочей станции пользователя, но при этом он увидит лишь черный экран.
Однако если попытаться переключить фокус в черную область консоли, то нажатия на кнопки и движения мыши будут переданы в сессию пользователя VMware View.
14 комментариев:
PCoIP такое делает когда подключается с WAN стороны через NAT.
У них (виваре) это описано в known issues, решение котрой видимо так и не будет (парни в Ipv6 менят? оО)
В общем то - сводит использование view для бизнесс пользователей почти к 0, т.к. например приложение для ipad работает ТОЛЬКО через PCoIP.
Конечно это можно обойти (черный экран) но для этого надо
1) VPN во внутрь
2) View с PCoIP
Но возникает вопрос, нахрена тогда view =)
только view на моем ipad так и не работат, а vmware предалгает либо включать vpn, либо делать PCoIP Secure Gateway
"On your iPad, if your View desktop does not load, or if you see the message, "Your desktop is loading too slowly," check with your View administrator. You might need to turn on your VPN, or the administrator might need to enable the PCoIP Secure Gateway component in the security server or View Connection Server instance that View Client for iPad connects to"
2morel333 - а я что-то потерял мысль - а на что жалоба?
на то что PCoIP требует прямой видимости десктопа или Secure Gateway?
Михаил - знаете, вы правы. Жалобы в принципе нет никакой, просто нет желания view опять собирать, чтобы посомреть на этот раз заработает или нет c Secure Gateway.
у меня заработало.
ну и теория однозначно гласит что заработает :)
Оказывается, если вью клиент пингует вью агента, то всё как-то работает. Блин, а как же тогда присобачить Secure Gateway? Мне как-то не улыбается поднимать VPN-ы.
такие вопросы правильнее и удобнее задавать на форуме.
по поводу Secure Gateway - а вы установили его? View Security Server это отдельная роль, в дополнение к View Connection Server.
Антон, можно попробовать поставить в "View Configuration->Servers->Connection Servers->your_conn_server"
галочку "use pcoip secure gateway . " и в поле "pcoip external url" укажите свой view connections server
должно работать и без security gateway.
кстати да, вроде же добавили pcoip шлюз и в connection сервер, забыл. спасибо.
но в экстернал url надо добавлять не connection server, а тот адрес на который обращаются клиенты (это надо делать если клиенты обращаются не на connection сервер, а на балансировщик нагрузки или что-то типа того - вот адрес внешней системы там и надо указать)
Владимир, спасибо, сработало.
Михаил, небольшое уточнение по поводу Security Server и Security Gateway.
То, что смотрит "соском" во внешний мир - это кто из них двоих должен быть?
Не совсем корректный вопрос.
Вообще говоря, есть роли Connection Server и Security Server, а Security Gateway - это компонент, который на них обоих может быть активирован.
во вне, технически, может смотреть и Connection server, но это менее безопасно чем если это будет security server.
We are demoing VMware Horizon 6 and I think I have a configuration problem that I'm troubleshooting. So internally on our local network we are not having any issues. When we are external I can ping the connection server by name and everything resolves so I think my NAT and DNS are right, but when I create the server on the Horizon client it just hangs on the "connecting" screen. No errors or time outs. I did some looking for a log entry but I haven't had any luck finding anything. Does someone now what this means?
Enter to win a Bose Sleepbuds II and more!
Contest ends 2022-05-20 Contests Fill out the form fill, and answer a question in the thread! Contest Details View all contests
Посты по email
Популярные посты за месяц
Хе хе. Я тут овладел новым джедайством (Денис, спасибо за наводку). Посмотрите на эту картинку: На первый взгляд скриншо.
Intel купил McAfee. по рассказам знающих тему все было вот так: - Так. Нам нужен антивирус. Купите кто-нибудь McAfee. Вечером: .
Как многие уже слышали, VMware объявила об относительно скором релизе пятой вСферы - в третьем квартале этого года. Уже стали известны по.
С радостью я констатирую тот факт, что практически каждый день мне пишут про мою книгу. В основном - "Где ее можно купить?" С о.
7 Replies
So are you able to authenticate externally at all or is it literally when you enter the connection server URL nothing happens?
Have you tried navigating to the URL externally through a browser as you should at least see a HTML page asking for HTML5 access of Horizon Client download.
All that aside though you will need a security server installed to present horizon traffic externally as while you can tunnel PCOIP traffic through a connection servers its not really designed to be directly accessible through the internet.
Yeah, nothing happens. I tried hitting the connection server via the browser, and it's pretty much the same thing. waiting until it times out. I have a security server, but I wanted to verify the connection server before adding the security server into the mix. So are you saying that "by design" you cannot connect to the connection server externally ?
By design really means thats its not going to be very secure, the connection servers are meant to broker connections only with PCOIP traffic flow direct from horizon client to desktop, while the security servers tunnel the PCOIP traffic through them. Connection servers need to be domain joined while its recommended security servers are not.
A ping reply suggests its hitting something which hopefully means its getting to your DMZ and its just a NATing issue.
Through a firewall you'll need to open up ports SSL 443 8443, and TCP/UDP 4172 for the solution to work.
I would join the connection server to the security server now otherwise its likely you'll have to change NATing rules twice.
When trying to access from outside the LAN. Here's the short version:
We're running a trial to test a View deployment. View 5 and Esxi 5.0. Everything works great inside the LAN, but when trying to access our security server outside the LAN the client connects, validates credentials, allows you to choose a desktop and connects to it, but then closes and simply says: 'The connection to the remote computer ended.'
Firewall issue
Make sure all the requiered ports are added.
Also Check the windows firewall settings of the computer.
We had this issues when doing it on
VMView 4.6.
Ярлыки
вторник, 6 сентября 2011 г.
Подпишись на комментарии
Комментарии
Комментарии
Архив блога
Последние комментарии
Подпишись на обновления по RSS
Обо мне
Все высказанное здесь представлено “как есть” и не предоставляет каких-либо гарантий и прав. Позиция автора может не совпадать с позицией работодателя. Просмотреть профиль
Читайте также: