Subj : Re: Ping Response...
To : Ian Segers
From : Bill McGarrity
Date : Tue Nov 07 2017 06:25 am
-=> Ian Segers wrote to Bill McGarrity <=-
-=> Bill McGarrity wrote to Ian Segers <=-
BM> Hello Ian!
ok.. Found an issue on my end with PEERBLOCK that was causing an issue. My
apologies on that...
IS> Sorry I don't have an answer really, I don't now why it worked once for
IS> you then not again, can I send same snap shot of my firewall settings
IS> via sportne e-mail address for you to lok at, I did change an option
IS> for inbound but the firewall menu went red so I put it back to the way
IS> it was.
IS> ie
IS> Microsoft Windows [Version 6.1.7601]
IS> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
IS> C:\Users\Ian>cd\
C:\>ping 1stchoicecore.co.nz
IS> Pinging 1stchoicecore.co.nz [125.238.104.56] with 32 bytes of data:
IS> Reply from 125.238.104.56: bytes=32 time=2ms TTL=64
IS> Reply from 125.238.104.56: bytes=32 time=1ms TTL=64
IS> Reply from 125.238.104.56: bytes=32 time=1ms TTL=64
IS> Reply from 125.238.104.56: bytes=32 time=2ms TTL=64
If you do it locally you shouldn't have an issue but after I fixed the
Peerblock issue, I was getting the following...
Pinging 125.238.104.56 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 125.238.104.56:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
As you can see at least my system was trying to get out to you.
Would someone else please ping Ian's address to see if it's not me going
nuts....
