Trace Result | Connectivity Testing | Path Analyzing
Let's Check the internet connectivity.
That is working or not, i means if there is ISP issue or not.
Let's start
first we have to check the connectivity of the connecting media.
Means LAN/ WLAN
Windows > Run > ncpa.cpl
please check your desired media card is connected or not, if not then the issue with the card or medium.
if the desired connection is showing connected then we can proceed further,
check the IP address of your system.
Windows > Run > cmd
and hit the command :
like this :
ipconfig
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::cd0f:defa:613a:7c%2
IPv4 Address. . . . . . . . . . . : 192.168.20.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.20.254
snapshot:
*Note: Be careful if the system ip is showing 169.254.0.0 like this, it means your system not able to contact the DHCP server and the system assigned the self generated IP i.e called APIPA
First up all we have the test our LAN connectivity, gateway,DNS, and so on.
we are going to test the LAN card connectivity.
Microsoft Windows [Version 10.0.10586](c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Night Reader>ping 192.168.20.100
Pinging 192.168.20.100 with 32 bytes of data:
Reply from 192.168.20.100: bytes=32 time<1ms TTL=64
Reply from 192.168.20.100: bytes=32 time<1ms TTL=64
Reply from 192.168.20.100: bytes=32 time<1ms TTL=64
Reply from 192.168.20.100: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.20.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Night Reader>
It means my system is able to communicate to the self system, and it is ready to communicate the other systems.
Now we have to test the gateway connectivity.
C:\Users\Night Reader>ping 192.168.20.254
Pinging 192.168.20.254 with 32 bytes of data:
Reply from 192.168.20.254: bytes=32 time=1ms TTL=64
Reply from 192.168.20.254: bytes=32 time=2ms TTL=64
Reply from 192.168.20.254: bytes=32 time=6ms TTL=64
Reply from 192.168.20.254: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.20.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 6ms, Average = 3ms
C:\Users\Night Reader>
Yes ! the system is able to communicate to the gateway.
C:\Users\Night Reader>ping google.com
Ping request could not find host google.com. Please check the name and try again.
Here i am trying to ping the google.com and the system saying that could not find the host.
it means the system not bale to communicate with the google.com, means the Internet is not working or the system is not able to communicate with the DNS Server.
Now we have to check the DNS connectivity. now we are going to check the DNS address of the system
Start : Run : cmd:
ipconfig /all
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Qualcomm Atheros AR956x Wireless Network Adapter
Physical Address. . . . . . . . . : 18-CF-5E-9F-1B-23
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::cd0f:defa:613a:7c%2(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.20.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 11 September 2016 09:17:52
Lease Expires . . . . . . . . . . : 12 September 2016 00:02:57
Default Gateway . . . . . . . . . : 192.168.20.254
DHCP Server . . . . . . . . . . . : 192.168.20.254
DHCPv6 IAID . . . . . . . . . . . : 102289246
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-77-DD-06-54-EE-75-24-F4-3F
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Now, we are going to rectify the issue.
let's trace the IP (8.8.8.8) if the IP is not reachable, if it sat "Request Time Out" then the issue with the ISP, if we are getting the response or system able to trace the destination IP, then the Internet is working fine.
C:\Users\Night Reader>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.20.254
2 8 ms 5 ms 16 ms 172.17.56.1
3 11 ms 8 ms 22 ms 103.12.132.1.rev.perfectinternet.in [103.12.132.1]
4 57 ms 30 ms 63 ms 72.14.194.113
5 35 ms 20 ms 13 ms 72.14.237.1
6 38 ms 20 ms 42 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\Users\Night Reader>
>> Here i am going to justify the trace result of the google DNS. <<
> 1 mili second is taking to reach the 192.168.20.254 | that is the gateway of my system | which is in the same broadcast domain | This is the fist hop
> 8 mili second is taking to reach the next hop of my gateway | means the ISP Network | 2nd hop
*NOTE: it will show up so on up to 30 hops.
:: Total Six row and five column are there and each of the column having it's own value, let's understand ::
Fist column : hop count
2nd column : RTT1 (Round Trip Time)
3rd column : RTT2
4th Column : RTT3 (Tracert command sends total three RTT)
5th column : Domain / IP Address
So Now, we have the path of the google DNS and we have the latency of their each hops.
We can use this trick to check the every connectivity which is creating issue.
* we can check this trick to use the connectivity testing between a site of a website or any source to destination connectivity.
You can check these command into the Linux/Unix Systems :
Command : OS
ping : LINUX /UNIX/ WINDOWS
tracert : WINDOWS
ipconfig : WINDOWS
ifconfig : LINUX/UNIX/MAC
ip add : LINUX
traceroute : LINUX
Note: tracert command sends the udp packet to the each hops and it collect the information.
Security Concern : UDP packet should be allow in the firewall.
Comments
Post a Comment