I have only one acquaintance who used cable IP service,
but that IP address is not answering pings. I did a
quick scan of that /24 and a couple others, and got no
replies from any of them.
"James Long" <james_...@nospam.museum.rain.com> wrote in message
news:3C097FF0...@nospam.museum.rain.com...
If you think the PDX whining about the cap is bad wait until the other
800,000 people get back online!
I'm with you though... I'm definitely not happy about the speed reduction
but I am pleased about the swift transition. It could have been a lot
worse.
- Joe
Anybody got any ideas? I'm about ready to give it up and go have a
pizza and try again tomorrow.
On the + side, it appears that attbi has more options with regard to
email forwarding, etc than @home did. I don't mind them changeing...I
just hope they leave it alone for awhile.
randy
Scott Willsey wrote:
>
> On Sun, 02 Dec 2001 01:39:19 GMT, "wize1" <wiz...@attbi.com> wrote:
>
> >yep. outage only lasted 45 minutes.. now on attbi.com system... Portland
> >looks like one of the first systems to transfer over to ATT...
> >
>
> Yes, we had a smooth transition in PDX, though of course people are
> whining about the 1.5Mbps downstream cap. I'm not thrilled about it,
> but we still have broardband, still have an internet connection, and
> are still getting service cheaper than the equivalent DSL plans.
>
> Some people are never happy, I guess.
>
> BTW, to the first gentleman: your friend's IP address will have
> changed to a new one. That's why you can't ping the old one.
>
> Scott
>
> --
> "The great pleasure of a dog is that you may make
> a fool of yourself with him and not only will he
> not scold you, but he will make a fool of
> himself too." - Samuel Butl
Is it mainly having problems resolving addresses (i.e. DNS problems)?
I was having similar problems earlier today. Entering the IP address of my
router in the DNS section of each computer's TCP/IP Properties seemed to fix
the problem. For instance, I checked 'Use the following DNS server
addresses' and then entered '192.168.1.1' as the 'preferred DNS server'.
- Joe
Hopefully they have informed him what the new IP will be. That
system used to have a static IP. The IP/netmask/gateway are
printed right on the installation work order. If it's now DHCP,
that's going to be fun for the DNS setup. How were you notified
that your IP would be changed? Or have you ever been on a static
IP with @home?
Just curious, how big a change was made? home.net appears to own
a netblock at 65.0.0.0/12. Have your IPs moved around within
that block or into a different block entirely?
And if that machine will now have to use DHCP, what is your exper-
ience on how dynamic those IPs really are? Has your lease ever
changed, and if so, how often?
"Joe Winton" <j...@winton.org> wrote in message
news:j_fO7.2039$R84.898@rwcrnsc52...
"Roger Bingham" <roger.c...@attbi.com> wrote in message
news:riiO7.2359$KY6.1054@rwcrnsc53...
That's basically what I did... For some reason, I had to actually enter my
router's IP address into the DNS settings of my Win2k and WinXP machines.
If I just set 'obtain DNS automatically' they would eventually quit
resolving addresses (and then work again for a few minutes after doing a
'ipconfig /renew'). My WinME machine had no problems at all with the
automatic configuration.
"Joe Winton" <j...@winton.org> wrote in message
news:ZyiO7.1425$Px.43887@rwcrnsc54...
All Emails for @home users changed from na...@home.com to na...@attbi.com
OLD EMAIL ADDRESS: na...@home.com
NEW EMAIL ADDRESS: na...@attbi.com
IP: DHCP
smtp: mail.attbi.com
POP3: mail.attbi.com
newsgroup: netnews.attbi.com
http://www.attbi.com/
Hope that helps
respond only in the newsgroup as my email cerant is changed to stop spam
It's noticably slower than the @home service was. And the AT&T
routers are located in Seattle instead of Portland (I have a machine
on an @home T-1 downtown; before 2am Saturday it was 8 hops from
home to that machine and I never got outside the city limits of
Portland, and now the traffic rolls up to Seattle, bounces around
there a while, the trickles back.) Plus at&t has some sort of http
proxy on the line -- I've got a 10 machine computational cluster at
home which has been idle and only doing seti@home for the past few
weeks, and after the changeover half of those boxes couldn't
retrieve workunits via my local proxy server so I had to set up a
proxy server on my downtown machine [1].
[1: colocation sucks, but it's a lot cheaper than $1000/month +
US West charges.]
____
david parsons \bi/ I suppose AT&T needs the ratecap so they can sell
\/ premium services.
Downstream capped at 1.5? Anyone know what the rated bandwidth was
originally?
Rob
"david parsons" <o...@pell.portland.or.us> wrote in message
news:9ue8b6$g...@pell.pell.portland.or.us...
Real-time report for ns6.attbi.com [63.240.76.4] (80% done)
Analysis: 'ns6.attbi.com' was found in 15 hops (TTL=49).
---------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name |
Location | Tzone | ms | Graph | Network |
---------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 192.168.0.100 | GREENBOX |
... | | | | (private use) |
| 1 | | 192.168.0.1 | - |
... | | 1 | x | (private use) |
| 2 | | 10.88.89.1 | - |
... | | 13 | x | (private use) |
| 3 | | 12.244.84.1 | - | ?Middletown, NJ
07748 | | 13 | x- | AT&T ITS |
| 4 | | 12.244.72.34 | - | ?Middletown, NJ
07748 | | 17 | x- | AT&T ITS |
| 5 | | 12.123.44.61 | gbr2-p70.st6wa.ip.att.net | Seattle, WA,
USA | -08:00 | 17 | x | AT&T ITS |
| 6 | | 12.122.5.169 | gbr4-p80.st6wa.ip.att.net | Seattle, WA,
USA | -08:00 | 18 | x- | AT&T ITS |
| 7 | | 12.122.2.230 | gbr4-p10.cgcil.ip.att.net | Chicago, IL,
USA | -06:00 | 61 | x | AT&T ITS |
| 8 | | 12.122.1.125 | gbr3-p60.cgcil.ip.att.net | Chicago, IL,
USA | -06:00 | 63 | x- | AT&T ITS |
| 9 | | 12.122.2.1 | gbr3-p10.n54ny.ip.att.net | New York, NY,
USA | -05:00 | 93 | x- | AT&T ITS |
| 10 | | 12.122.5.245 | gbr2-p60.n54ny.ip.att.net | New York, NY,
USA | -05:00 | 80 | x- | AT&T ITS |
| 11 | | 12.123.1.133 | gar1-p370.n54ny.ip.att.net | New York, NY,
USA | -05:00 | 82 | x- | AT&T ITS |
| 12 | | 12.122.255.162 | - | ?Middletown, NJ
07748 | | 82 | x-- | AT&T ITS |
| 13 | | 63.240.64.246 | - | ?San Diego, CA
92191 | | 126 | --x--- | AT&T CERFnet |
| 14 | | 63.240.88.74 | - | ?San Diego, CA
92191 | | 78 | x | AT&T CERFnet |
| 15 | | 63.240.76.4 | ns6.attbi.com | ?San Diego, CA
92121 | | 81 | x | Project Redwood ISP |
---------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to ns6.attbi.com, average = 81ms, min = 81ms, max = 86ms --
02-Dec-01 6:10:03 PM
>
> Downstream capped at 1.5? Anyone know what the rated bandwidth was
> originally?
>
i don't know what the rated bandwidth was, but i was regularly seeing
4-5mbps. it's not all useful speed, as most servers aren't going to be able
to send the data that fast, but it's really useful with programs like winmx
where you can have multiple downloads running at the same time.
I did finally get through to a level 2 tech, who said that the reason I
could not connect is because AT&T moved away from using an assigned Host
name and will be using the router's MAC address, but this capability is not
yet ready.
Jack
"Roger Bingham" <roger.c...@attbi.com> wrote in message
news:riiO7.2359$KY6.1054@rwcrnsc53...
Rob
"Jack Price" <jack....@intel.com> wrote in message
news:9uggr6$h...@news.or.intel.com...
Rob
Tonight, I plugged in my old Host name from @home and I have the router
working and all 5 PC's on the net. I give up trying to figure the logic out,
it just works now.
Jack
"Robert" <bsi...@hotmail.com> wrote in message
news:9%QO7.3215$R84.2196@rwcrnsc52...
A lot higher. The first week after the at&t installer came around,
I was getting on the order of 550mbytes/sec transferring large files
(and if the upload cap is there, I don't think I'll be doing much
of THAT anymore -- a few 700m OS install images a month and there
goes all my bandwidth.) I'd guess that the raw cable is capable of
10mbit and that's what @home was offering.
Another annoying feature of the at&t service is that I seem to be
having a hell of a time resolving domain names with the nameservers
they supply with their dhcp leases.
____
david parsons \bi/ And if I tell them I'm using a FreeBSD router serving
\/ a computer cluster and a pair of Windows clients, the
heads of the support staff will explode.
john-
The big deal is to reboot your modem - power off for 5 minutes, then
reboot your system. Dunno what that accomplishes exactly but perhaps
the modem is designed to seek a new momma if the old one isn't there.
Change your settings: anything that was nnn.y...@home.com is now
attbi.com
mail.attbi.com
netnews.attbi.com
yourus...@attbi.com
"John Meissen" <jmei...@shell1.aracnet.com> wrote in message
news:WPbP7.78672$Lc.26...@sjcpnn01.usenetserver.com...
When the changeover was made, from what i'm told, each modem had to be
re-provisioned one by one. which was causing alot of the problems.
re:
***
with the dns issues, look at my post higher up in the thread, it shows where
all
the name servers are located. I'd suggest getting a program called
visualroute and
entering the names into it, and see which NS is closest via ping.
***
Thanks, chris, i'll do that
"Chris Jaggers" <yeag...@home.com> wrote in message
news:3C0D2816...@home.com...
Bleah. G-d invented dhcp to handle those details, and it's too much
trouble for me to go in and manually edit /etc/resolv.conf every time
the dhcp lease renews.
[I wrote]
>> A lot higher. The first week after the at&t installer came around,
>> I was getting on the order of 550mbytes/sec transferring large files
^^^^^^^^^
550kbytes/sec.
A little different, but still a lot faster than the nominal 1.5mbit
that at&t is providing.
As more people are switched over to attbi, the cable is getting
slower. Ugh.
____
david parsons \bi/ At least I'm in range for DSL now.
\/
Rob
Agreed, although AYMK, you can (at least with BSD UNIX) run dhclient
in such a way that it will not overwrite /etc/resolv.conf.
man dhclient, noting 'supersede' and 'prepend'. You could either
supersede the nameservers with ones you like better, or at least insert
your favorite(s) at the beginning of the hunt list.
> As more people are switched over to attbi, the cable is getting
> slower. Ugh.
Almost as though it was a shared medium. :)
It still shares bandwidth, just not as soon in the line from customer to
ISP. DSL is shared from the DSLAM on to the ISP. But the advantage for
the ISP is that if the DSLAM becomes oversubscribed, it's relatively
easy
to just buy more bandwidth between the DSLAM and the ISP. When cable
becomes oversubscribed, they have to physically sever the cable segment,
and physically install a second cable head at the point of the severance
to drive the new segment. Obviously, this requires a truck roll to do
the work, a new cable head every time they split a segment, and a new
feed
to service the physical location of the new cable head. DSLAM bandwidth
can be upgraded by the ISP just by buying more bandwidth from the LEC.
It doesn't require anybody to drive out somewhere and climb a pole, and
figure out a way to get a feed to this new cablehead out in the middle
of
nowhere. DSL bandwidth is always upgraded right at the CO, where it's
pretty darn easy to get bandwidth. Usually. ;)
So they're both shared, and yeah, if you're not publishing any web
content,
just downloading stuff without giving anything back, then cable will be
faster. But in an overloaded scenario, it's easier for a DSL ISP to fix
overloading than it is for a cable ISP to fix overloading.
When it was @home, the local proxy server was about 5 hops away from
my gateway, so that was one thing I didn't have to worry about (my
machine downtown -- also on @home, but on the business side[1] --
was a whopping 8 hops and 12 ms away from my house.
The AT&T dhcp provides me with 4 dns servers -- one in Los Angeles,
one in New Jersey, and two on the other side of gateway in seattle.
The slower ones are the first on the list. I'd forgotten about the
tweaks I could do to dhclient.conf, but, bleah, that's a pretty
dumb way to provision a network.
>> As more people are switched over to attbi, the cable is getting
>> slower. Ugh.
>
>Almost as though it was a shared medium. :)
Well, unless AT&T has materialized a bunch of new subscribers, the
people on the segment are the same people who were on there when
@home was providing the service. It got congested then during
the evenings, but not nearly as bad as now.
[1: Which means that it may keep connectivity until February, if I'm
lucky. Hope I can get a job before then so I can run a T-1 to
my house and not colocate at a more expensive place.]
____
david parsons \bi/ setenv DISGRUNTLED T
\/