Select the network interface associated with the IP address, and then note the IP address in the IPv4 Public IP column (if any). In the search box, enter the IP address from step 2.In the navigation pane, under Network & Security, choose Network Interfaces.Open the Amazon Elastic Compute Cloud (Amazon EC2) console.If the WorkSpace is stopped, choose Actions, Start WorkSpaces. Note: The WorkSpace must be in a running state for the private IP address to appear. Select the WorkSpace, and then expand the details pane using the arrow. To allow the client machine to connect to the WorkSpace using RDP, follow these steps: You should authorize only a specific IP address or range of addresses to access your instance. If you use ::/0, you enable all IPv6 address to access your instance. Using 0.0.0.0/0, allows all IPv4 addresses to access your instance using RDP. Important: When entering the IP addresses that you use to connect to the WorkSpace, don't enter 0.0.0.0/0 or allow IP addresses that don't need access. If you use a network address translation (NAT) gateway, then you can RDP from within the network. To RDP outside of the network, you must provide internet access from your WorkSpace by assigning an Elastic IP address to each WorkSpace. When you're done troubleshooting, remove the RDP inbound rule that you added. Note: It's a best practice to use only an RDP client to connect to a WorkSpace for troubleshooting purposes. To do so, you must update the Amazon WorkSpaces security group settings to allow connections from the IP address of your RDP client machine. However, you might need to connect to a WorkSpace using an RDP client for troubleshooting. Typically you connect to your WorkSpace using the Amazon WorkSpaces client.
0 Comments
Leave a Reply. |