Subj : Re: Birthday present from he.net
To   : Roger Nelson
From : Joe Delahaye
Date : Fri Jul 08 2016 22:52:12

  Re: Re: Birthday present from he.net
  By: Roger Nelson to Joe Delahaye on Fri Jul 08 2016 21:23:36

 JD>RM>> Can you try this:
 JD>RM>> ping6 fe80::c612:f5ff:fe66:e6c8%9

 RN> [...]

 JD> C:\Windows\system32>>ping fe80::c612:f5ff:fe66:e6c8%9

 JD>> Pinging fe80::c612:f5ff:fe66:e6c8%9 with 32 bytes of data:
 JD>> Reply from fe80::c612:f5ff:fe66:e6c8%9: time=2ms
 JD>> Reply from fe80::c612:f5ff:fe66:e6c8%9: time<1ms
 JD>> Reply from fe80::c612:f5ff:fe66:e6c8%9: time<1ms
 JD>> Reply from fe80::c612:f5ff:fe66:e6c8%9: time<1ms

 JD>> Ping statistics for fe80::c612:f5ff:fe66:e6c8%9:
 JD>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
 JD>> Approximate round trip times in milli-seconds:
 JD>> Minimum = 0ms, Maximum = 2ms, Average = 0ms

 RN> What happens when you run TRACERT? PING isn't all that telling because
 RN> some people have PING blocked.


Tracert to that address returns the same address <G>  It is mine.

Tracing route to fe80::c612:f5ff:fe66:e6c8%9 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  fe80::c612:f5ff:fe66:e6c8
--- SBBSecho 3.00-Win32
 * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

.