Call Search
     

New to Ham Radio?
My Profile

Community
Articles
Forums
News
Reviews
Friends Remembered
Strays
Survey Question

Operating
Contesting
DX Cluster Spots
Propagation

Resources
Calendar
Classifieds
Ham Exams
Ham Links
List Archives
News Articles
Product Reviews
QSL Managers

Site Info
eHam Help (FAQ)
Support the site
The eHam Team
Advertising Info
Vision Statement
About eHam.net

donate to eham
   Home   Help Search  
Pages: [1]   Go Down
  Print  
Author Topic: eham.net website - not responding through Comcast/xFinity  (Read 1652 times)
AC2TQ
Member

Posts: 1


WWW

Ignore
« on: August 02, 2017, 06:55:47 AM »

All,
  I cannot seem to access eham.net through Xfinity in NJ.  The website responds to a ping, which means that I can resolve the IP (from DNS) and the Ping (ICMP) response is enabled.  I get a site timeout when going to it from any (IE, Edge, Chrome, Firefox) web browser.  (Note: I did NOT try to telnet to port 80 of the server, but that should result in the same timeout.  I will try later.) 
It seems eham.net has some type of protection that has blacklisted some (all?) xfinity addresses from NJ.  Can someone from eHAM check the security/connection logs for evidence of this?  Can we rectify? 

(Note: I am posting this from work that has an independent connection.  Further, Verizon wireless connectivity is fine as well.)

ping eham.net

Pinging eham.net [69.36.242.135] with 32 bytes of data:
Reply from 69.36.242.135: bytes=32 time=94ms TTL=50
Reply from 69.36.242.135: bytes=32 time=95ms TTL=50
Reply from 69.36.242.135: bytes=32 time=91ms TTL=50
Reply from 69.36.242.135: bytes=32 time=95ms TTL=50

Ping statistics for 69.36.242.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 91ms, Maximum = 95ms, Average = 93ms

ping www.eham.net

Pinging www.eham.net [69.36.242.135] with 32 bytes of data:
Reply from 69.36.242.135: bytes=32 time=93ms TTL=50
Reply from 69.36.242.135: bytes=32 time=96ms TTL=50
Reply from 69.36.242.135: bytes=32 time=93ms TTL=50
Reply from 69.36.242.135: bytes=32 time=96ms TTL=50

Ping statistics for 69.36.242.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 96ms, Average = 94ms



-73

Angelo

AC2TQ
Logged
N2MG
Administrator

Posts: 10047



« Reply #1 on: August 03, 2017, 12:49:27 AM »

Your IP address was blocked by our sometimes over-anxious security code.

Please try again.

Mike N2MG
Logged
KC4ZGP
Member

Posts: 1637




Ignore
« Reply #2 on: August 03, 2017, 09:30:31 AM »


Well Angelo, what you describe in detail tells me there is a problem somewhere along the line.
The problem needs to be eliminated.

Glad I could help.

On 1.8136MHz Morse, 2200UTC.

Kraus
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!