cancel
Showing results for 
Search instead for 
Did you mean: 

Connection to 68.178.213.37 failed.

New Member

Re: Connection to 68.178.213.37 failed.

the error I get says "Your cache administrator is root.
Associate Professor

Re: Connection to 68.178.213.37 failed.

You may need to contact godaddy or the webservice owners, because Google is resolving the address as 208.109.4.222, while Hughes resolves to a different address... which takes you straight to their hosting service.  Several days ago they was making network changes, it's possible that services for their users are still not propagating.  Someone somewhere may have messed up their NS settings...
New Member

Re: Connection to 68.178.213.37 failed.

Here's what I just got when I pinged the email server:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Phil Seibert>ping 68.178.213.37

Pinging 68.178.213.37 with 32 bytes of data:
Reply from 68.178.213.37: bytes=32 time=656ms TTL=236
Reply from 68.178.213.37: bytes=32 time=621ms TTL=236
Reply from 68.178.213.37: bytes=32 time=625ms TTL=236
Reply from 68.178.213.37: bytes=32 time=639ms TTL=236

Ping statistics for 68.178.213.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 621ms, Maximum = 656ms, Average = 635ms

C:\Users\Phil Seibert>

New Member

Re: Connection to 68.178.213.37 failed.

But I CAN access that server when I'm connected through an ISP other than HughesNet.  It can't be something Godaddy did if it works through all the other ISPs I connect through!
Moderator

Re: Connection to 68.178.213.37 failed.

Hi Philip,

It may not be just HughesNet - I've tested the IP and the site on my cellphone (Verizon Network) and it still times out. I'll try to locate your account and disable the Web Acceleration Server for you and see if that works.

Thanks
Amanda
Associate Professor

Re: Connection to 68.178.213.37 failed.

And this is what I get when I ping various services... I can ping secureserver.net, but can't reach their email service.  Seems the email server is offline, or something isn't routing right.  I also get very different address results...  GoDaddy (they apparently own these servers/routers?) had issues several days ago, though they claim these issues are resolved.  They started on the 15th, just before you started experiencing issues.

Note: I am using Google DNS and NOT the Hughes DNS, seems Godaddy changed addressing at some point for this domain.  When using a seperate ISP, what does smtp.secureserver.net resolve to?


Just got word from a friend that is on Comcast that he gets the same results we do.
New Member

Re: Connection to 68.178.213.37 failed.

Amanda, We'ver tried FOUR times to disable Web Acceleration in the system control center. I see you did it again for me.  Thanks, but it is STILL not working.  How many times do we keep trying that before we agree that it's not that?
New Member

Re: Connection to 68.178.213.37 failed.

But why will it work for me when I tether my verizon phone to my computer?  I'm able to send messages through Outlook and to access my email via web page when I'm connected through that ISP but not through the HughesNet modem.  It works for me everywhere except on HughesNet.
New Member

Re: Connection to 68.178.213.37 failed.

So how do I use a DNS server other than the HughesNet one?
Associate Professor

Re: Connection to 68.178.213.37 failed.