on 6/13/02 3:21 PM, Laurent Daudelin at laurent_daudelin_at_fanniemae.com
> On 13/06/02 14:38, "Konstantinos Xonis"
> <Konstantinos.Xonis_at_physik.uni-giessen.de> wrote:
>> I couldn't get to it either.
> Thanks to all that did respond! That confirms to me that something is wrong
> somewhere, but not here, at the office.
> Now, what could be wrong? I've read a message from Eric Strobel saying he
> wouldn't be surprised that Cox is somehow "blocking" those packets. If it
> was so, how could they do that? I've got some real nice traceroute listings,
> but I'm not sure how to read them. Is there anything on these traceroute
> listings that would tell me that the packet is somehow "blocked"? I know
> that the traceroute seems to go through a few servers at Cox, but other than
> that, I don't know.
> If that was the case, why was I able to access my machine on Tuesday?
My guess (just a guess, nothing but a guess, so help me God): the Cox
firewall 'knows' that dyndns is a popular means of folks running servers
from inside their system and watches specifically for this (and other types
of traffic) to try and squash the most people with the least effort.
(BTW, just to make sure I'm clear, I assume your server is your home machine
and that you're trying to access from the office, which is not accessing via
Eric Strobel (fyzycyst_at_NOSPAM^mailaps.org)
===================================================================== The odds are greatly against you being immensely smarter than everyone else in the field. If your analysis says your terminal velocity is twice the speed of light, you may have invented warp drive, but the chances are a lot better that you've screwed up. =====================================================================
-- Read the List FAQ/Etiquette: http://www.newtontalk.net/faq.html Read the Newton FAQ: http://www.guns-media.com/mirrors/newton/faq/ This is the NewtonTalk mailing list - http://www.newtontalk.net
This archive was generated by hypermail 2.1.2 : Wed Jul 03 2002 - 14:02:17 EDT