- Newest
- Most votes
- Most comments
Check WorkSpace Status =>Check the status of your WorkSpace. It should be in a "Running" state. If it's in "Stopped" or "Stopping" state, start it. Network Configuration =>Ensure that your WorkSpace is in a VPC and subnet that has proper network access. The subnet should have a route to an internet gateway or a NAT gateway if you're using the web client. Security Groups =>Verify that the security group associated with your WorkSpace allows inbound and outbound traffic on the necessary ports: Port 4172 (PCoIP) Port 4195 (WSP - WorkSpaces Streaming Protocol) Ports 53, 80, 443 (for internet access)
Verify Authentication and User Credentials =>Directory Service: Ensure your directory service (AD Connector, Simple AD, or AWS Managed Microsoft AD) is functioning correctly and that your WorkSpace is properly joined to the directory. Verify your user credentials and ensure they are correct.
We have set up manually with all ports open for testing still get this issue frequently. Is there any specific URL we can use to test any blocker on the firewall?
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
Thank you. I ended up deleting the workspace and the directory that was created with the Quick Setup wizard. The wizard apparently improperly configured several settings as when I created everything manually it works like a charm.