By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,149 Members | 885 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,149 IT Pros & Developers. It's quick & easy.

O.T. ==> PING discussion

P: n/a
MLH
C:\Docs\TitleWork>ping piedmonttriadtowing.dyndns.org

Pinging piedmonttriadtowing.dyndns.org [70.60.253.195] with 32 bytes
of data:

Reply from 70.60.253.195: bytes=32 time=49ms TTL=239
Reply from 70.60.253.195: bytes=32 time=52ms TTL=239
Reply from 70.60.253.195: bytes=32 time=324ms TTL=239
Reply from 70.60.253.195: bytes=32 time=61ms TTL=239

Ping statistics for 70.60.253.195:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 324ms, Average = 121ms

C:\Docs\TitleWork>

Q: Should one expect shorter ping times pinging the IP
address directly as opposed to traveling through dyndns?
Aug 31 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Thu, 31 Aug 2006 11:00:29 -0400, MLH <CR**@NorthState.netwrote:
>C:\Docs\TitleWork>ping piedmonttriadtowing.dyndns.org

Pinging piedmonttriadtowing.dyndns.org [70.60.253.195] with 32 bytes
of data:

Reply from 70.60.253.195: bytes=32 time=49ms TTL=239
Reply from 70.60.253.195: bytes=32 time=52ms TTL=239
Reply from 70.60.253.195: bytes=32 time=324ms TTL=239
Reply from 70.60.253.195: bytes=32 time=61ms TTL=239

Ping statistics for 70.60.253.195:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 324ms, Average = 121ms

C:\Docs\TitleWork>

Q: Should one expect shorter ping times pinging the IP
address directly as opposed to traveling through dyndns?
No. The ping will travel the same route. The only difference is that
you won't have to resolve the address before pinging.

-=-=-=-=-=-=-=-=-=-=-=-=
Randy Harris
tech at promail dot com
Aug 31 '06 #2

P: n/a
Why on God's Green Earth would you post this in an Access newsgroup?
Maybe an MS O/S newsgroup, but ACCESS???

MLH wrote:
C:\Docs\TitleWork>ping piedmonttriadtowing.dyndns.org

Pinging piedmonttriadtowing.dyndns.org [70.60.253.195] with 32 bytes
of data:

Reply from 70.60.253.195: bytes=32 time=49ms TTL=239
Reply from 70.60.253.195: bytes=32 time=52ms TTL=239
Reply from 70.60.253.195: bytes=32 time=324ms TTL=239
Reply from 70.60.253.195: bytes=32 time=61ms TTL=239

Ping statistics for 70.60.253.195:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 324ms, Average = 121ms

C:\Docs\TitleWork>

Q: Should one expect shorter ping times pinging the IP
address directly as opposed to traveling through dyndns?
Aug 31 '06 #3

P: n/a
MLH
Sounds reasonable. Thx, Randy.
Aug 31 '06 #4

P: n/a
Since we're on an OT excursion...

You can ping a list of IPs from inside Access and write the results
back to your DB. Very little to it. There's code at vbnet (Randy
Birch's site). You can call it from inside Access. The way I did it
was to convert the various possible responses to T/F (I think the
"success" variable = 0, so you compare that result to zero.) Then if
you open an updateable recordset on your table, you can have access do
all the pinging for you.

Aug 31 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.