On Sunday 03 February 2002 07:41 am, Joel Hammer wrote:

>
> Also, I would like to know if the new name is resolvable on the internet,
> so, would someone, NOT on the comcast network, kindly ping that name
> (tow33dhcp1252.towson01.md.comcast.net) and see if you get back:
> 68.33.4.228 ?
>
> Thanks,
> Joel
>
>
>
> _______________________________________________
> Linux-users mailing list - http://linux.nf/mailman/listinfo/linux-users
> Subscribe/Unsubscribe info, Archives,and Digests are located at the above
> URL.

-- 
Ted Ozolins (VE7TVO)
Westbank, B. C.
PING tow33dhcp1252.towson01.md.comcast.net (68.33.4.228) from (me) : 56(84) bytes of data.
64 bytes from tow33dhcp1252.towson01.md.comcast.net (68.33.4.228): icmp_seq=0 ttl=240 time=131.896 msec
64 bytes from tow33dhcp1252.towson01.md.comcast.net (68.33.4.228): icmp_seq=1 ttl=240 time=130.139 msec
64 bytes from tow33dhcp1252.towson01.md.comcast.net (68.33.4.228): icmp_seq=2 ttl=240 time=129.973 msec
64 bytes from tow33dhcp1252.towson01.md.comcast.net (68.33.4.228): icmp_seq=3 ttl=240 time=131.733 msec
64 bytes from tow33dhcp1252.towson01.md.comcast.net (68.33.4.228): icmp_seq=4 ttl=240 time=133.442 msec

--- tow33dhcp1252.towson01.md.comcast.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 129.973/131.436/133.442/1.336 ms

Reply via email to