- 最新
- 最多得票
- 最多評論
Well a lot of debugging and googling and then a sudden moment of suspicion solved the issue. First off, it is kind of difficult to analyze with just the Amazon Workspaces client as to what IP address/domains are being accessed by it. By searching a lot, I was able to find that the client writes some of the connectivity related logs in a log file at following location: C:\Users\Username\AppData\Local\Amazon Web Services\Amazon WorkSpaces\logs
The log file is created and written when the client is opened and removed when we close it, so need to keep that in mind about it. In the log file there was one line, [ERR] HttpClient Timeout : https://connectivity.amazonworkspaces.com/. Exception: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 5 seconds elapsing.
So basically if the client fails to get a response from the above URL within 5 seconds, the above error of No network : Network connection lost is shown on the client.
Once I came to know this, I could check the URL from browser and each time, it took more than 5 seconds to respond. But again, this was not happening on laptop2 on same network. Then something curiousbee said clicked, the 'network adapter settings '. Although I had checked this previously and assumed as on the laptop1 and net2 combo same adapter settings worked, it must not be an issue. But still when I checked the laptop1 and net1 combo and laptop2 and net1 combo, both had differences in the IP address being allotted to them. The net1 was assigning an IPV4 as well as IPV6 IP address to the laptop1 where as only IPV4 IP address to the laptop2. Then once I updated the network1 to work on IPV4 only(local DHCP, no need for IPV6) and restarted, it resolved my issue!
So TL;DR Disable IPV6 address on local network while using AWS client.
Based on the error message you're seeing, it sounds like the Amazon WorkSpaces client is having trouble maintaining a network connection on your primary laptop and network combination. It's strange that the issue doesn't occur on your secondary laptop, but given that it has a fresh install of the client, it's possible that there could be some differences in how the client is configured or how the networking components are set up.
Some things you could try to troubleshoot the issue on your primary laptop and network:
Check your network settings: Make sure that your network adapter settings are configured correctly and that there are no restrictions or firewalls that could be blocking the client's network traffic.
Check for conflicts with other software: It's possible that there could be other software running on your primary laptop that's interfering with the client's network connection. Try disabling any antivirus, firewall, or VPN software temporarily to see if that resolves the issue.
Try running the client in compatibility mode: Right-click on the Amazon WorkSpaces client shortcut and select Properties. Then, under the Compatibility tab, check the box for "Run this program in compatibility mode for" and select an older version of Windows, such as Windows 8 or 7. Apply the changes and try launching the client again.
Contact Amazon WorkSpaces support: If none of the above steps resolve the issue, it's possible that there could be a problem with your account or the client itself. Contact Amazon WorkSpaces support and provide them with the logs you've collected to see if they can help identify the root cause of the problem.
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Thank you for the reply! For the client configuration, both of them had new installations with latest version setup downloaded from the website and simple next next, so no separate configuration was done. Both the laptop use same vendor and updated version antivirus, but still didn't work after disabling. In fact, by enabling VPN on laptop1, I was able to access the login page, which is my temporary solution for now. I will try the compatibility way and if nothing else works, share the logs with workspace support.