Hey everyone, i got a user who is on MacOS Mojave and using the horizon view client v4.9.
when he attempts to launch a virtual app or a VDI desktop, there is a delay when launching the resource and eventually gets a very strange alert below that says "io.netty.handler.timeout.ReadTimeoutException".
We do have 2 other users who are also on Mojave and the same version of horizon and they do not seem to have any problems. I've never run into this before and when i reached out to vmware support, they couldn't really help since Mojave is technically an "unsupported" version of MacOS for that particular version of the horizon view client. so i'm at the mercy of the web.
Any assistance with this would be appreciated.
If this issue only occurs on the specific Mac machine and not on others, I guess it could be network adapter issue on this Mac. Please trying following steps to reset IPv4 network.
Commend lines for above steps:
sudo networksetup -setv4off <networkservice>
sudo networksetup -setdhcp <networkservice>
If the issue is still reproducible, please follow below steps to collect the client logs and attached in this page.
1. Quit Horizon Client, run command from Terminal.app
launchctl setenv VMWARE_VIEW_DEBUG_LOGGING "1"
2. Launch Horizon Client and reproduce this issue
3. Get all logs from below paths:
$HOME/Library/Logs/VMware/VMware Horizon Client/*.*
I am also having the same problem. I am using a Mac and when trying to connect to VDI I get an alert which reads "io.netty.handler.timeout.ReadTimeoutException." I am able to connect successfully on a personal Mac, but I get this error when using my company issued computer. Does anyone have any suggestions? I tried the network setting change listed above, but that did not seem to work.
I've tried using the latest VMware horizon client 4.x and 5.1 with MacOS Mojave 10.14.6
I've tried disable the network/DHCP config
I've tried using internal/external (mobile data) network
_But_ still have the same "io.netty.handler.timeout.ReadTimeoutException". error.
I've changed the log level, and all that it shows in the log is
2019-08-29T12:30:16.379+09:00| vthread-55248| I125: VTHREAD 123145335775232 "vthread-55248" tid 55248
2019-08-29T12:30:16.379+09:00| vthread-55248| I125: SOCKET creating new IPv4 socket, connecting to xxx.xxx.xxx.xxx:xxx (xxx.xxx.xxx.xxx)
2019-08-29T12:30:16.380+09:00| vthread-55248| W115: socket 102 transition to state SYN_SENT, reason FECSocketDoConnect refCount 4
2019-08-29T12:30:16.398+09:00| crtbora| W115: socket 102 transition to state CLOSED, reason FECSocketDoClose refCount 6
2019-08-29T12:38:27.969+09:00| vthread-67043| I125: VTHREAD 123145341677568 "vthread-67043" tid 67043
2019-08-29T12:38:27.970+09:00| vthread-67043| I125: SOCKET creating new IPv4 socket, connecting to xxx.xxx.xxx.xxx:xxx (xxx.xxx.xxx.xxx)
2019-08-29T12:38:27.970+09:00| vthread-67043| W115: socket 103 transition to state SYN_SENT, reason FECSocketDoConnect refCount 4
2019-08-29T12:38:28.042+09:00| crtbora| W115: socket 103 transition to state CLOSED, reason FECSocketDoClose refCount 6
Any idea why?
I take it back, after checking system time (not related)
I started rolling back to previous version
then it finally works with version 4.4 (really have no idea why)
if someone could explain, it could be fantastic. (is it cert related?)