*** Customer Can't Access Website ***
* If customer can't access internet, we must to do as bellow as:
* Example:
Dear NOC,
Customer have problem can’t access two website : www.thejakartapost.com ; www.nst.com.my and customer need check for him now. Please check for him too.
1. Customer can’t access website: www.thejakartapost.com with ISP OpenNet but 3G access normal.
Item check
Result
id customer
PPDC46338 Seng Sunly 017556119
Name website
www.thejakartapost.com
result nslookup
C:\Users\user>nslookup www.thejakartapost.com
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
Name: www.thejakartapost.com
Address: 54.251.114.84
result ping
C:\Users\user>ping www.thejakartapost.com -t
Pinging www.thejakartapost.com [54.251.114.84] with 32 bytes of data:
Reply from 54.251.114.84: bytes=32 time=302ms TTL=39
Reply from 54.251.114.84: bytes=32 time=108ms TTL=39
Reply from 54.251.114.84: bytes=32 time=253ms TTL=39
Request timed out.
Reply from 54.251.114.84: bytes=32 time=264ms TTL=39
Reply from 54.251.114.84: bytes=32 time=108ms TTL=39
Reply from 54.251.114.84: bytes=32 time=108ms TTL=39
Reply from 54.251.114.84: bytes=32 time=109ms TTL=39
Reply from 54.251.114.84: bytes=32 time=112ms TTL=39
Reply from 54.251.114.84: bytes=32 time=108ms TTL=39
Request timed out.
Reply from 54.251.114.84: bytes=32 time=108ms TTL=39
Reply from 54.251.114.84: bytes=32 time=111ms TTL=39
Reply from 54.251.114.84: bytes=32 time=112ms TTL=39
Reply from 54.251.114.84: bytes=32 time=108ms TTL=39
Reply from 54.251.114.84: bytes=32 time=107ms TTL=39
Reply from 54.251.114.84: bytes=32 time=109ms TTL=39
Reply from 54.251.114.84: bytes=32 time=108ms TTL=39
Reply from 54.251.114.84: bytes=32 time=135ms TTL=39
Reply from 54.251.114.84: bytes=32 time=148ms TTL=39
Reply from 54.251.114.84: bytes=32 time=109ms TTL=39
Reply from 54.251.114.84: bytes=32 time=109ms TTL=39
Reply from 54.251.114.84: bytes=32 time=107ms TTL=39
Reply from 54.251.114.84: bytes=32 time=107ms TTL=39
Ping statistics for 54.251.114.84:
Packets: Sent = 42, Received = 40, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 107ms, Maximum = 302ms, Average = 123ms
Control-C
Result tracert
C:\Users\user>tracert -d www.thejakartapost.com
Tracing route to www.thejakartapost.com [54.251.114.84]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 38 ms 37 ms 36 ms 118.69.131.249
4 * * 94 ms 118.69.132.165
5 176 ms * * 118.69.247.246
6 * 135 ms 65 ms 118.70.2.177
7 * 74 ms 73 ms 203.208.191.97
8 64 ms 64 ms 69 ms 203.208.178.2
9 102 ms 99 ms 208 ms 203.208.178.169
10 96 ms 97 ms 97 ms 203.208.175.70
11 150 ms 155 ms 140 ms 203.83.223.4
12 115 ms 113 ms 177 ms 203.83.223.23
13 107 ms 105 ms 102 ms 203.83.223.231
14 117 ms 109 ms 112 ms 175.41.128.241
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 108 ms 107 ms 108 ms 54.251.114.84
Trace complete.