- From: Bill Mullen <noprivateemail@xxxxxxxxxx>
- Date: Thu, 06 Dec 2007 19:10:11 -0600
The AT&T tech support rep believes that your ISP/server/whatever and/or
wherever in the path must have put AT&T on a "blacklist" or something
similar. They say at this time that the problem definitely is on "your
end" with your ISP/servers not acknowledging packets from AT&T. (And
it's not just me as John Treder is having the same problem. We are
both AT&T DSL subscribers.)
A very questionable response if you ask me. We've a server at
http://www.starhosting.de with dedicated 100mbit switched connection to a
44gbit of backbones including DE-CIX, TeliaSonera, KPN, GBLX and Lambdanet
without any filtering/blakclisting. I've forwarded the problem report to them
but i seriously doubt that there's any issues there. We've heard of similar
problems from other customers before and in all instances so far it was a
problem in a router misconfiguration at the end of their ISP.
If you do a traceroute what are the last few hops?
Hannes, I too am on AT&T DSL and when trying to ping
news.nexusdb.com, I time out right after I hit my ISP.
No matter how I try to reach starhosting.de it fails. Pinging returns
the following error: "Ping request could not find www.starhosting.de.
Please check the name and try again."
A TraceRt results in, "Unable to resolve target system name
- Re: NexusDB?
- From: Hannes Danzl[NDD]
- Re: NexusDB?
- Prev by Date: Re: NexusDB?
- Next by Date: Re: NexusDB?
- Previous by thread: Re: NexusDB?
- Next by thread: Re: NexusDB?