[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Trouble getting mail, connecting to eskimo (fwd)
- To: hydra@eskimo.com, ericj@eskimo.com, badger@eskimo.com
- Subject: Re: Trouble getting mail, connecting to eskimo (fwd)
- From: Robert Dinse <nanook@eskimo.com>
- Date: Thu, 26 Apr 2001 12:50:03 -0700 (PDT)
- cc: outages-list@eskimo.com
- In-Reply-To: <Pine.SUN.3.96.1010425072432.22412C-100000@eskimo.com>
- Resent-Date: Thu, 26 Apr 2001 12:50:22 -0700
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"sIpXB2.0.gt6.yl7ww"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
I've talked to the support technicians at MegaPOP about this and they tell
me that they have had other reports of people getting assigned dynamic IP's out
of the 64.24.35 block not routing properly.
This block corrosponds to a particular box, each box has 196 ports and is
assigned a class C for dynamic IP assignment.
They've had enough reports to know this is a real problem but have not
been able to reproduce it. They say often people report being able to ping or
traceroute but being unable to make a TCP connection (www, ftp, mail, etc).
If we get a customer experiencing this if possible they would like us to
get them on-line while the customer is still on-line so they can do some
testing and try to nail it down.
On Wed, 25 Apr 2001, Eskimo North Support wrote:
>
> I seem to remember eric investigating this IP Block, that is the first
> three octets in this address.
>
> 64.24.35
>
> ---------- Forwarded message ----------
> Date: Wed, 25 Apr 2001 06:33:15 -0700 (PDT)
> From: archer@eskimo.com
> To: support@eskimo.com
> Cc: archer@eskimo.com, "Curt, WE7U Mills" <hacker@tc.fluke.com>
> Subject: Re: Trouble getting mail, connecting to eskimo
>
> On Wed, 25 Apr 2001 archer@eskimo.com wrote:
>
> > For the last couple of months though I get connected fine
> > but cannot get my mail via fetchmail, and cannot do an
> > SSH to eskimo.com to get into my account.
> >
> > Sometimes I can hang up and dial again and get in,
> > sometimes not.
>
> Three times logging in this morning (at 5:00am) I got this
> assigned to me and could not get in:
>
> inet addr:64.24.35.161 P-t-P:192.168.254.1 Mask:255.0.0.0
>
> Then the fourth time logging in I got this, and was able
> to finally communicate:
>
> inet addr:64.24.34.73 P-t-P:192.168.254.1 Mask:255.0.0.0