Sunday, March 8, 2009

I apologize..

I officially apologize to the incompetent support staff at ATT Uverse. It would appear that the problem is officially with Comcast in blocking my ATT IP address from my own web server on Comcast's network. If I could force my router to take a new IP address from a different range I will prove it most thoroughly. I switched to openDNS for DNS support and that proved that it actually was not a DNS problem. Then I switched to route through an open proxy (shhh) to mask my ip address and I was able to reach my server.

Comcast has a policy where they feel free to block certain kinds of traffic. They do this to prevent Spamming and phishing. They also do it to block telecommuting. Time Warner will also block telecommuting. My use of Remote Desktop Connection, MS Frontpage and FTP all together I'm guessing must send up big red flags that I'm "telecommuting". That is not cool. What is the point of having business class broadband if you won't allow remote access to your business servers. Grrrr. We'll see what we can do.

6 comments:

CLJ711 said...

yeah, I figured it might be that... Comcast ... would it help to have one of the static IPs - for one, the one on the KNS server that died. Oh and you "shhhhd" about an open proxy... is this something I should know about???! OH and one of their (Comcast's) features they sold us on is all the IPs so we CAN telecommute - that is why we got so many IP addresses.... that we can't figure out how to use .... there is something else wrong here. Maybe they did totally give us the wrong modem as we all suspected in the beginning...?

Tim Niedfeldt said...

No. I already have a static IP or it wouldn't even be a legitimate webserver. I don't need another.

Comcast has said that my IP at home here, provided by ATT is not allowed to proceed any further than a comcast server in MA. On Monday we'll have a speak with them.

If there were a way that the router could detect my connections to my server and decide to blacklist my personal IP address THAT would be not only weird but improbable...because my server is still in a DMZ.

No your router and my server are sitting there happy and ignorant that Comcast has blocked me from proceeding past their gateway. I have found some others on the web forums who have found these kinds of things at times and have had to call to get them fixed.

Tim

Tim Niedfeldt said...

oh and using an open proxy for routing is typically a way a spammer, hacker, porn peruser, or any such person who wants to remain anonymous stays anonymous

CLJ711 said...

right - but do we have an open proxy that is vulnerable? not that I am too worried since our sites aren't there any more, and you take care of yours... but there are other computers...

And I thought you weren't able to put an IP on yours when we were setting up ... well, there must have been something else I was thinking about...

OK so we can telecommute to our office... but from here, not from the backwoods called WI. I'll remember that. :-D

Tim Niedfeldt said...

no open proxies for us. I used one from Russia. My public ip is the one that ends in .65

CLJ711 said...

BTW - my turn to apologize - WI is a very beautiful state.