VMware Horizon Community
dawho9
Enthusiast
Enthusiast

View Connection Server Problems - Error raising port

So here we go. Have a fully functional View 3.1 install w/ composer. Build an edge server (non domain member) and have ports 80 and 443 open to the edge server from the internet NAT'ed to the edge server IP address. The edge server is not in a DMZ but actually on the same subnet as the connection server, so there is no firewall between the connection server and security server. There is also no firewall between the security server/connection server and the win XP workstations. To verify I can remote desktop to the xp workstations from both the security server and the connection server.

On the edge server I have set an edge server in the connection server and saved the security file (config.properties renamed to locked.properties) into the \conf directory. I have restarted services on the edge server. During the install of the security server I was prompted to choose a location of my connection server and I put in viewmgr1.test.com which is the name of the view server that works. On the CS server, I have NOT put an external URL on the View Server as my understanding is that I do not have to put one in there.

I can login to the view client with no issues through the security server. When I attempt to launch my VM I get an error that says "The desktop is currently not available". On the CS I get the following error:

Failed to launch desktop: CN=Apps,OU=Applications,DC=vdi,DC=vmware,DC=int for user: user2: Error raising port: Session has not connected yet.

On the security server I get the following error in the event viewer:

Problem sending JMS message, message not sent: Javax.jms.JMSException and then a bunch of junk after that. The funny thing is, if I login to the XP workstation that view is attempting to connect to, I can see my connection hit the workstation as it disconnects me from the workstation and tells me it's locked by my user.

Thoughts?

Richard

Reply
0 Kudos
5 Replies
dawho9
Enthusiast
Enthusiast

So if I NAT the external IP straight to the connection server and only open up port 443 is works (I have to set the external URL then on the CS server). So it's definately something wrong with my security server. Anyone have any thoughts on what I'm missing/wrong?

dw9

Reply
0 Kudos
mjsvirt
Hot Shot
Hot Shot

on the external url specified on the security server did you specify :443 as a suffix?

also is port 4001 open on the desktops?

Jason Silva http://silvaecs.com http://twitter.com/silvaecs
Reply
0 Kudos
dawho9
Enthusiast
Enthusiast

4001 to the workstation? I don't see anything listening on that port. Cannot telnet from connection server to workstation on 4001. I can the other way around. I have no firewall running on the XP workstations.

I am not using the external URL on the connection server. I have left it blank because my understanding was you did not need to set it if you had a security server. And just to confirm, my locked.props file is:

clientProtocol=https

clientHost=vdi.externaldnsname.com

clientPort=443

Richard

Reply
0 Kudos
mjsvirt
Hot Shot
Hot Shot

ok yes your security server file looks correct.

Yes it would be the other way around for 4001 (from workstation).

So far it sounds like everything is right. Check out all of the other ports outlined in the Admin Guide p.34 I think..

I know there are no firewalls.. but justwant to be sure that communication is flowing through and through..

Jason Silva http://silvaecs.com http://twitter.com/silvaecs
Reply
0 Kudos
fatherharm
Contributor
Contributor

Did you find a solution? I am having this exact issue and have no hope in sight.

Reply
0 Kudos