Forum Discussion
Mac and RDP Issues
Currently running APM 11.4.1 with the latest hotfix. Hoping to replace our Firepass soon. I have setup everything in regards to Access Profile, VIP, etc.
I have everything working now except for Macs being able to RDP into VMs. I have a RDP setup for Windows machines that works great. However, I can't get the Macs to be able to RDP in. I have Java enabled on the VIP as well as on the RDP resource for it. When I log into the webtop I see the link to the java rdp session. When I click on it, it starts to load the java applet and then I get an error that states "Connection Exception" then craps out. I have not been able to figure out what is causing this.
When I run a tcpdump, I can see where it tries to start a connection, but gets a reject and ends. Not sure what is going on and F5 support hasn't been the greatest help in regards to this. Thanks.
5 Replies
- Grayson_149410
Nimbostratus
Bump - Hamish
Cirrocumulus
Basically java RDP is broken. Not F5's fault, blame Oracle and the ever changing requirements to try & shore up the security of the JVM's...
One of the biggest issues is that on the Mac, java RDP really really really wants to be able to resolve the hostname (Of the Mac) to an IP. It doesn't need to, and doesn't use it when it does, but if the resolution is NOT available, then java RDP just won't work.
To fix it, I usually make sure that the hostname is in the /etc/hosts file on the Mac. Then Java RDP should work (Unless you've found yet a other issue with it :)
There's other postings around here (From about 18 months - 2 years ago IIRC) where this was discussed for a bit until I finally stumbled over the answer while running with tracing enabled and judicious tcpdumps...
H
- Hamish
Cirrocumulus
In a shell/terminal window, type
hostname
That'll return the hostname of the Mac... e.g.
bash-3.2 hostname this-host.domain.com bash-3.2So in /etc/hosts, the easiest thing to do is to add that (this-host.domain.com) as an alias for localhost... So the line in /etc/hosts that currently reads
::1 localhostshould be changed to read
::1 localhost this-host.domain.comThe important thing is that whatever the hostname command returns needs to be in /etc/hosts to make it resolvable (Actually that's a little white lie... if you're somewhere that has the output from hostname resolvable already.. e.g. DHCP with DDNS) would work already.
You can test your entry by typing
ping `hostname`The Backtick characters are important... If ping says it can't resolve the name, then /etc/hosts isn't correct.
H
- Hamish
Cirrocumulus
What does the java console on the Mac say if you bump the log/tracing up to level 5
H
- Hamish
Cirrocumulus
Oh!
You aren't behind a proxy are you? Check that the proxy settings for your JVM are set (Or not set) appropriately.
H
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com