Home/ AWS Configuration/ Step 8: Testing Network Connections

Step 8: Testing Network Connections

After connecting to your Windows server, you should verify that network connectivity is working correctly. This step tests both internet access and internal VPC communication.

Verify IP Configuration

  1. Open Command Prompt or PowerShell on your EC2 instance.
  1. Type the following command and press Enter:

_CODE_BLOCK_0_

  1. Verify that your IP address matches the address you configured during EC2 instance creation:
    • Public-Server should show 10.0.1.100
    • Private-Server should show 10.0.2.200

    Note: Skip this verification if you selected auto-assignment for your IP address.

    Test Internet Connectivity

    1. In Command Prompt, type:

    _CODE_BLOCK_1_

    1. Press Enter and verify you receive responses.

    Successful ping responses confirm:

    • Your Internet Gateway (IGW) is functioning correctly
    • DNS resolution is working
    • Your route tables are configured properly

    Troubleshooting: If the ping fails, verify:

    • The Internet Gateway is attached to your VPC
    • The public route table has a route to 0.0.0.0/0 through the IGW
    • The security group allows outbound traffic

    Test Private Network Access

    1. In Command Prompt on your Public-Server, type:

    _CODE_BLOCK_2_

    1. Press Enter and verify you receive responses from the Private-Server.

    Troubleshooting: If no response is received:

    • Verify the Private-Server security group allows traffic from 10.0.0.0/16
    • Confirm the Private-Server is running
    • Check that Windows Firewall on the Private-Server allows ICMP traffic

    Test Remote Desktop Between Servers

    Once you can successfully ping the Private-Server, you can also establish Remote Desktop connections:

    1. On the Public-Server, open Remote Desktop Connection.
    1. Enter 10.0.2.200 as the target.
    1. Connect using the Private-Server administrator credentials.

    This works because traffic between subnets is allowed through the security groups you configured.

    Success Criteria

    You are ready to proceed when:

    • [x] You can ping an internet domain (like google.com) from Public-Server
    • [x] You can ping 10.0.2.200 from Public-Server
    • [x] You can RDP to Private-Server from Public-Server

    Note: External connections from your home or office network remain unavailable until VPN configuration is complete and route tables are properly established.

    Related Topics

    ← Back to Index