Some times a user encountered rdp disconnects to a server/machine which is located at remote site. The probable cause of this issue is the unavailability of the link over which packet is routed from source to destinations.
Lets assume we have to take remote desktop connection of a machine which as IP address 192.168.90.225 from source ip address 172.16.141.10 and we are not able to take rdp.
we need to do following steps to troubleshoot the issue.
1. Ping the remote IP address .
2. Check traceroute
3. Check VPN tunnels status. incase tunnel is down then we would not able to connect to the remote host and rdp will not come.
4. Coordinate with respective ISP over which tunnel has created.
In this way most of the cases tunnels have issue and the same will get fixed once tunnel connectivity has resumed.
When issue was going on ping status is
Traceroute
Tracing route to 192.168.20.15 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 172.16.119.1
2 <1 ms <1 ms <1 ms 172.16.13.10
3 <1 ms <1 ms <1 ms 115.113.51.137
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 *
Check VPN status
Lets assume we have to take remote desktop connection of a machine which as IP address 192.168.90.225 from source ip address 172.16.141.10 and we are not able to take rdp.
we need to do following steps to troubleshoot the issue.
1. Ping the remote IP address .
2. Check traceroute
3. Check VPN tunnels status. incase tunnel is down then we would not able to connect to the remote host and rdp will not come.
4. Coordinate with respective ISP over which tunnel has created.
In this way most of the cases tunnels have issue and the same will get fixed once tunnel connectivity has resumed.
When issue was going on ping status is
C:\Users\hikumar>ping 192.168.90.225
Pinging 192.168.90.225 with 32 bytes of data:
Request timed out.
Request timed out
Request timed out
Request timed out
Traceroute
Tracing route to 192.168.20.15 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 172.16.119.1
2 <1 ms <1 ms <1 ms 172.16.13.10
3 <1 ms <1 ms <1 ms 115.113.51.137
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 *
Check VPN status
root@JUN-SRX650-357-FW2-
node0:
------------------------------
Index State Initiator cookie Responder cookie Mode Remote Address
6008554 DOWN 973dddb26fb07774 0000000000000000 Main 216.214.181.210
Since VPN tunnel is showing down, please check with respective ISP at our end well far end whosoever is required and once the tunnel came up, issue will get fixed.
Results once issue get resolved:
Ping Status
C:\Users\hikumar>ping 192.168.90.225
Pinging 192.168.90.225 with 32 bytes of data:
Reply from 192.168.90.225: bytes=32 time=230ms TTL=124
Reply from 192.168.90.225: bytes=32 time=230ms TTL=124
Reply from 192.168.90.225: bytes=32 time=230ms TTL=124
Reply from 192.168.90.225: bytes=32 time=240ms TTL=124
Traceroute
C:\Users\hikumar>tracert -d 192.168.90.225
Tracing route to 192.168.90.225 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 172.16.141.1
2 <1 ms <1 ms <1 ms 172.16.13.10
3 224 ms 224 ms 224 ms 10.100.1.13
4 225 ms 225 ms 228 ms 10.50.1.1
5 224 ms 224 ms 224 ms 192.168.90.225
Trace complete.
VPN Tunnel Status
root@JUN-SRX650-357-FW2-Cluster> show security ike security-associations
node0:
--------------------------------------------------------------------------
Index State Initiator cookie Responder cookie Mode Remote Address
6008599 UP 44c61ed4ae11f7c3 2a0682bf2eae5707 Main 216.214.181.210
Comments
Post a Comment