Mac->PC Fluid connection (if it connects) takes 1-2minutes
Platforms: OSX-Sonoma 14 (latest SP)
Target: Win11
Connection: MAC --> PC
Jump Desktop+Connect (latest)
Connecting from MAC->PC over RDP is "instant" (Jump or native/built-in)
Connecting over Fluid will either time-out the first time, and I have to put in my "<DOMAIN>/username" -- it seemingly forgets to use my domain name when this happens, or its just forgetting it all the time and thats why its doing this?? :shrug:
But after timing out the first time, I put <DOMAIN>/username and Password, and it spins there for about 1 minutes, then eventually connects.
Sometimes it doesn't connect unless I log into the machine first and its sitting at the desktop, but ONCE it's connect (regardless of how I manage to get there), it will re-connect consistently, and much faster (15'ish seconds -- which is still too long!)
How can I get this connecting faster? Seems like there's something wrong with the fact a domain name is required.
-
Hi, Thank you for reaching out to us.
I'm sorry to hear about the issues you're facing with Jump.
For us to be more efficient in resolving this issue, please submit a support request and include the Jump logs from your Mac.
Please open up Jump Desktop, click Help, and then Diagnostic Logs. Please attach the zip file directly to this ticket and send it over.
Kind Regards,
Abdul Ghani -
Well, its across all machines. I'm running Sonoma 14.4 Beta 3.
Considering it literally does this on EVERY SINGLE MAC, its not my setup, Jump isn't working right with Sonoma 14.4 Beta 2 or Beta 3. No matter what you do, it Asks if JD Connect can "Share the Screen" 2-3x..and then jump doesn't connect. The only way to get it to connect is to make a MAC Shared screen to it, and click Yes. This isn't localized to myself, I've now tried this on multiple machines. Ya'll need to test your stuff against Apple's Betas... You make it impossible to use as a developer if you don't. Also, connecting to a PC now is painful, takes 2-3 minutes, unless you goto the PC, run the Connect client as Admin, or at least login..its seems rather random-- but even connecting to PC's (while much more reliable) takes literally 2 minutes. I'm connected via Wifi and direct-Lan in all tests, and in all test-cases, its horrible. To make matters worse, logging into a domain is broken, you have to add domain-name\username each time. And in credential manager, your passwords are saved as "{" ... have to manually correct keychain.
Please sign in to leave a comment.
Comments
2 comments