• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Ping me please :)

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
philip@Rivendell philip $ nslookup www.vexcom.com
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 24.93.1.118
Address: 24.93.1.118#53

Non-authoritative answer:
Name: www.vexcom.com
Address: 207.44.234.119

philip@Rivendell philip $ ping www.vexcom.com
PING www.vexcom.com (207.44.234.119) 56(84) bytes of data.
64 bytes from 207.44.234.119: icmp_seq=1 ttl=43 time=75.7 ms
64 bytes from 207.44.234.119: icmp_seq=2 ttl=43 time=116 ms
64 bytes from 207.44.234.119: icmp_seq=3 ttl=43 time=82.1 ms
64 bytes from 207.44.234.119: icmp_seq=4 ttl=43 time=79.2 ms

--- www.vexcom.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3038ms
rtt min/avg/max/mdev = 75.727/88.490/116.858/16.536 ms
 
Pinging vexcom.com [207.44.234.119] with 32 bytes of data

Reply from 207.44.234.119: bytes=32 time=47ms TTL=44
Reply from 207.44.234.119: bytes=32 time=47ms TTL=44
Reply from 207.44.234.119: bytes=32 time=32ms TTL=44
Reply from 207.44.234.119: bytes=32 time=47ms TTL=44

Ping statistics for 207.44.234.119:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 47ms, Average = 43ms
 
Originally posted by: Nohr
Start menu > Run > type in "command" > hit OK

At the prompt type "ping <address>".

<address> can either be a name or ip address.
Click to expand...

wow didint know about command 😱 are CMD (command prompt) and command the same thing?

btw, ping <www.vecom.com> isint working 😕
 
>ping vexcom.com

Pinging vexcom.com [64.246.22.46] with 32 bytes of data:

Reply from 64.246.22.46: bytes=32 time=500ms TTL=236
Reply from 64.246.22.46: bytes=32 time=380ms TTL=236
Reply from 64.246.22.46: bytes=32 time=126ms TTL=236
Reply from 64.246.22.46: bytes=32 time=131ms TTL=236

Ping statistics for 64.246.22.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 500ms, Average = 284ms


C:\Documents and Settings\Garry Mitchell>tracert vexcom.com

Tracing route to vexcom.com [64.246.22.46]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 15 ms 8 ms 9 ms 10.71.32.1
3 9 ms 8 ms 10 ms wal-t2cam1-b-ge-wan34-104.inet.ntl.com [80.1.170.145]
4 10 ms 11 ms 12 ms pop-t2core-b-ge-wan61.inet.ntl.com [62.255.81.141]
5 9 ms 8 ms 9 ms pop-bb-b-so-320-0.inet.ntl.com [62.253.185.69]
6 20 ms 19 ms 20 ms so-3-0-0.cr1.lhr3.uk.mfnx.net [208.185.188.41]
7 20 ms 20 ms 21 ms so-0-0-0.cr2.lhr3.uk.mfnx.net [208.184.231.146]
8 83 ms 82 ms 84 ms so-7-0-0.cr2.lga1.us.mfnx.net [64.125.31.182]
9 82 ms 83 ms 80 ms so-0-0-0.cr2.lga2.us.mfnx.net [208.184.232.198]
10 106 ms 111 ms 106 ms so-4-0-0.cr2.atl2.us.mfnx.net [208.184.232.157]
11 107 ms 107 ms 107 ms so-0-0-0.cr1.atl2.us.mfnx.net [208.185.0.217]
12 119 ms 119 ms 124 ms so-3-0-0.mpr1.iah1.us.mfnx.net [64.125.31.25]
13 121 ms 119 ms 119 ms 216.200.251.29.ev1.net [216.200.251.29]
14 126 ms 126 ms 125 ms 207.218.245.37
15 127 ms 128 ms 125 ms ns1.hosting2020.com [64.246.22.46]

Trace complete.
 
Originally posted by: MainFramed
Originally posted by: Nohr
Start menu > Run > type in "command" > hit OK

At the prompt type "ping <address>".

<address> can either be a name or ip address.
Click to expand...

wow didint know about command 😱 are CMD (command prompt) and command the same thing?

btw, ping <www.vecom.com> isint working 😕
Click to expand...

Sorry, meant for you to take out < and >. It's:

ping www.vexcom.com

command and cmd aren't the same, but I'm not sure what the difference is. Command is the dos emulation and cmd.exe is XP's command prompt. Something like that..
 
C:\Documents and Settings\ping www.vexcom.com

Pinging www.vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=69ms TTL=48
Reply from 207.44.234.119: bytes=32 time=58ms TTL=48
Reply from 207.44.234.119: bytes=32 time=60ms TTL=48
Reply from 207.44.234.119: bytes=32 time=58ms TTL=48

Ping statistics for 207.44.234.119:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 69ms, Average = 61ms
 
i pinged, but i dont know how to copy text from the command box 😕

i see your not supposed to use those brackets <> 😛
 
Originally posted by: Nohr
Originally posted by: MainFramed
Originally posted by: Nohr
Start menu > Run > type in "command" > hit OK

At the prompt type "ping <address>".

<address> can either be a name or ip address.
Click to expand...

wow didint know about command 😱 are CMD (command prompt) and command the same thing?

btw, ping <www.vecom.com> isint working 😕
Click to expand...

Sorry, meant for you to take out < and >. It's:

ping www.vexcom.com

command and cmd aren't the same, but I'm not sure what the difference is. Command is the dos emulation and cmd.exe is XP's command prompt. Something like that..
Click to expand...

lol yup i just got that, thanks Nohr
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

Pinging vexcom.com [64.246.22.46] with 32 bytes of data:

Reply from 64.246.22.46: bytes=32 time=157ms TTL=230
Reply from 64.246.22.46: bytes=32 time=157ms TTL=230
Reply from 64.246.22.46: bytes=32 time=160ms TTL=230
Reply from 64.246.22.46: bytes=32 time=158ms TTL=230

Ping statistics for 64.246.22.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 157ms, Maximum = 160ms, Average = 158ms
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\CadetLee.DESKTOP1>ping www.vexcom.com

Pinging www.vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=67ms TTL=46
Reply from 207.44.234.119: bytes=32 time=210ms TTL=46
Reply from 207.44.234.119: bytes=32 time=61ms TTL=46
Reply from 207.44.234.119: bytes=32 time=62ms TTL=46

Ping statistics for 207.44.234.119:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 210ms, Average = 100ms

C:\Documents and Settings\CadetLee.DESKTOP1>ping vexcom.com

Pinging vexcom.com [64.246.22.46] with 32 bytes of data:

Reply from 64.246.22.46: bytes=32 time=56ms TTL=240
Reply from 64.246.22.46: bytes=32 time=55ms TTL=240
Reply from 64.246.22.46: bytes=32 time=54ms TTL=240
Reply from 64.246.22.46: bytes=32 time=55ms TTL=240

Ping statistics for 64.246.22.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 56ms, Average = 55ms

C:\Documents and Settings\CadetLee.DESKTOP1>
 
Starting ping - Apr 28, 2003 15:32:24
Pinging www.vexcom.com [64.246.22.46]....
IP Address RTT(ms) TTL Bytes Received
64.246.22.46 101 240 64
64.246.22.46 48 240 64
64.246.22.46 48 240 64
64.246.22.46 49 240 64
64.246.22.46 51 240 64
64.246.22.46 51 240 64
64.246.22.46 66 240 64
64.246.22.46 54 240 64
64.246.22.46 49 240 64
64.246.22.46 52 240 64
64.246.22.46 49 240 64
64.246.22.46 48 240 64
64.246.22.46 50 240 64
64.246.22.46 52 240 64
64.246.22.46 52 240 64
64.246.22.46 53 240 64
64.246.22.46 48 240 64
64.246.22.46 48 240 64
64.246.22.46 48 240 64
64.246.22.46 80 240 64
Ping Successful
20 packets received out of 20 packets transmitted : 0% PACKET LOSS
Round Trip Time (in milliseconds) Max/Min/Av: 101/48/54
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\xxxxxxxx>cd\

C:\>tracert vexcom.com

Tracing route to vexcom.com [64.246.22.46]
over a maximum of 30 hops:

1 7 ms 1 ms 1 ms xxxxxxxxxxxxxxxxx
2 19 ms 18 ms 18 ms xxxxxx
3 19 ms 18 ms 15 ms xxxxxxx
4 22 ms 17 ms 18 ms p7-0.evrtwa1-cr6.bbnplanet.net [4.0.79.129]
5 18 ms 18 ms 18 ms p7-0.evrtwa1-br2.bbnplanet.net [4.24.9.125]
6 19 ms 18 ms 18 ms so-4-2-0.sttlwa1-hcr2.bbnplanet.net [4.24.6.61]

7 19 ms 18 ms 20 ms so-7-0-0.sttlwa1-hcr1.bbnplanet.net [4.24.10.233
]
8 18 ms 20 ms 18 ms p1-0.sttlwa1-cr1.bbnplanet.net [4.24.10.237]
9 36 ms 37 ms 36 ms p3-3.xsttlwa15-abovenet.bbnplanet.net [4.25.88.3
0]
10 36 ms 36 ms 39 ms so-2-0-0.cr1.sea1.us.mfnx.net [208.185.175.178]

11 37 ms 36 ms 36 ms so-3-1-0.mpr3.sjc2.us.mfnx.net [216.200.127.117]

12 113 ms 111 ms 108 ms pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81]
13 107 ms 110 ms 109 ms so-3-0-0.cr1.dfw2.us.mfnx.net [216.200.127.213]

14 105 ms 109 ms 107 ms so-4-0-0.mpr1.iah1.us.mfnx.net [64.125.31.37]
15 111 ms 111 ms 111 ms 216.200.251.29.ev1.net [216.200.251.29]
16 83 ms 81 ms 82 ms 207.218.245.37
17 82 ms 82 ms 81 ms ns1.hosting2020.com [64.246.22.46]

Trace complete.

C:\>ping vexcom.com

Pinging vexcom.com [64.246.22.46] with 32 bytes of data:

Reply from 64.246.22.46: bytes=32 time=86ms TTL=238
Reply from 64.246.22.46: bytes=32 time=78ms TTL=238
Reply from 64.246.22.46: bytes=32 time=78ms TTL=238
Reply from 64.246.22.46: bytes=32 time=80ms TTL=238

Ping statistics for 64.246.22.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 86ms, Average = 80ms




first few tracert result should be censor to protect yourselves
 
C:\>ping www.vexcom.com

Pinging www.vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=70ms TTL=46
Reply from 207.44.234.119: bytes=32 time=70ms TTL=46
Reply from 207.44.234.119: bytes=32 time=80ms TTL=46
Reply from 207.44.234.119: bytes=32 time=70ms TTL=46

Ping statistics for 207.44.234.119:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 80ms, Average = 72ms

C:\>tracert www.vexcom.com

Tracing route to www.vexcom.com [207.44.234.119]
over a maximum of 30 hops:

1 30 ms 20 ms 20 ms adsl-67-116-51-254.dsl.sntc01.pacbell.net [67.11
6.51.254]
2 20 ms 30 ms 20 ms dist2-vlan60.sntc01.pbi.net [63.203.51.66]
3 20 ms 30 ms 20 ms bb1-g1-0.sntc01.pbi.net [63.203.35.17]
4 20 ms 20 ms 30 ms bb2-p14-0.pxpaca.sbcglobal.net [64.161.1.42]
5 20 ms 20 ms 30 ms bb1-p11-0.pxpaca.sbcglobal.net [64.161.1.49]
6 20 ms 20 ms 30 ms pos9-2.mpr1.pao1.us.mfnx.net [64.125.31.205]
7 20 ms 20 ms 20 ms so-6-3-0.mpr3.sjc2.us.mfnx.net [208.184.233.141]

8 70 ms 70 ms 70 ms pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81]
9 70 ms 60 ms 60 ms so-3-0-0.cr1.dfw2.us.mfnx.net [216.200.127.213]

10 70 ms 81 ms 70 ms so-4-0-0.mpr1.iah1.us.mfnx.net [64.125.31.37]
11 70 ms 80 ms 70 ms 216.200.251.61.ev1.net [216.200.251.61]
12 70 ms 70 ms 80 ms 207.218.245.41
13 80 ms 70 ms 70 ms 207.44.234.119

Trace complete.

C:\>


looks fine to me.
 
Pinging vexcom.com [64.246.22.46] with 32 bytes of

Reply from 64.246.22.46: bytes=32 time=53ms TTL=240
Reply from 64.246.22.46: bytes=32 time=52ms TTL=240
Reply from 64.246.22.46: bytes=32 time=55ms TTL=240
Reply from 64.246.22.46: bytes=32 time=56ms TTL=240

Ping statistics for 64.246.22.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 56ms, Average = 54ms
 
chris@panther:~$ ping www.vexcom.com
PING www.vexcom.com (207.44.234.119): 56 data bytes
64 bytes from 207.44.234.119: icmp_seq=0 ttl=45 time=48.7 ms
64 bytes from 207.44.234.119: icmp_seq=1 ttl=45 time=52.6 ms
64 bytes from 207.44.234.119: icmp_seq=2 ttl=45 time=46.5 ms
64 bytes from 207.44.234.119: icmp_seq=3 ttl=45 time=49.5 ms
64 bytes from 207.44.234.119: icmp_seq=4 ttl=45 time=50.8 ms
 
THanks for the pings peeps, now that everyone can see half the time im getting one ping, half the time i get another, yet im not running round-robin DNS... should i move this topic somewhere else?
 
H:\>ping www.vexcom.com -t

Pinging vexcom.com [64.246.22.46] with 32 bytes of data:
Reply from 64.246.22.46: bytes=32 time=90ms TTL=239
..................

😀
 
ping -fs 4000 www.vexcom.com
PING www.vexcom.com (207.44.234.119): 4000 data bytes
...........................................................................................................................................................................................
...........................................................................................................................................................................................
...........................................................................................................................................................................................
...........................................................................................................................................................................................
...........................................................................................................................................................................................
...........................................................................................................................................................................................
........................................................................................................................^C
--- www.vexcom.com ping statistics ---
1243 packets transmitted, 0 packets received, 100% packet loss
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\ffmcobalt>ping www.vexcom.com -t

Pinging www.vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=81ms TTL=50
Reply from 207.44.234.119: bytes=32 time=75ms TTL=50
Reply from 207.44.234.119: bytes=32 time=102ms TTL=50
Reply from 207.44.234.119: bytes=32 time=73ms TTL=50
Reply from 207.44.234.119: bytes=32 time=72ms TTL=50
Reply from 207.44.234.119: bytes=32 time=95ms TTL=50
Reply from 207.44.234.119: bytes=32 time=72ms TTL=50
Reply from 207.44.234.119: bytes=32 time=79ms TTL=50
Reply from 207.44.234.119: bytes=32 time=76ms TTL=50
Reply from 207.44.234.119: bytes=32 time=75ms TTL=50
Reply from 207.44.234.119: bytes=32 time=73ms TTL=50
Reply from 207.44.234.119: bytes=32 time=72ms TTL=50
Reply from 207.44.234.119: bytes=32 time=75ms TTL=50
Reply from 207.44.234.119: bytes=32 time=76ms TTL=50
Reply from 207.44.234.119: bytes=32 time=86ms TTL=50
Reply from 207.44.234.119: bytes=32 time=73ms TTL=50
Reply from 207.44.234.119: bytes=32 time=76ms TTL=50
Reply from 207.44.234.119: bytes=32 time=73ms TTL=50
Reply from 207.44.234.119: bytes=32 time=76ms TTL=50
Reply from 207.44.234.119: bytes=32 time=78ms TTL=50
Reply from 207.44.234.119: bytes=32 time=88ms TTL=50
Reply from 207.44.234.119: bytes=32 time=76ms TTL=50
Reply from 207.44.234.119: bytes=32 time=81ms TTL=50
Reply from 207.44.234.119: bytes=32 time=76ms TTL=50
Reply from 207.44.234.119: bytes=32 time=99ms TTL=50

Ping statistics for 207.44.234.119:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 102ms, Average = 79ms
Control-C
^C
C:\Documents and Settings\ffmcobalt>
 
Originally posted by: MainFramed
ffmcobalt looks better imo
Click to expand...
😕

Heh...

Ping statistics for 64.246.22.46:
Packets: Sent = 1496, Received = 1496, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 180ms, Average = 84ms
Control-C
^C
H:\>

😀
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top