Quote:
Originally Posted by Ron Bennett
Maybe Comcast isn't solely the problem.
Does the hosting provider have multiple network routes? Perhaps the hosting company is lying about having more network redundancy than they really have.
Has the server changed IP addresses lately? And/or physically been moved? (if it's dedicated, check the uptime - did it go down lately; if it's a virtual / vps, such moves may be done with no notice; ask the provider if anything has been changed / moved).
Ron
|
I'm embarrassed to admit, it wasn't Comcast afterall.. Turns out my servers firewall blacklisted my own IP address by mistake!
Initially the server blamed my ISP. Comcast ran inconclusive tests, and sent me up a tier. Today I was at my wits end, and started getting pissy on the phone. Comcast ran a trace route, and concluded it WAS on my server afterall!
The first guy I spoke with on my server passed the buck to Comcast - the first guy at Comcast passed the buck up a tier - the second guy at Comcast determined it was on the server's end - the second guy at the server finally sorted it all out.
24 hours later I am finally able to communicate with my own server again, and in the end it was not Comcast's fault at all.
Thanks for your advice though Ron - your theory was the closest to the actual problem.
