[CLUE-Tech] AT&T Broadband

[rrarabie at attbi.com]

> Have you tried unplugging the modem & rebooting?

Are you joking?  Yes.  I did follow their instructions.

I figure if my Mac couldn't get online, it HAS to be their problem.  It would be really hard to misconfigure TCP/IP networking on a Mac.

When I finally got a person on the phone this morning they said they could not "see" my modem on the network.

Cheers!

Randy
> 
> I had the same kind of problem last night -- but this morning
> everything seems to be (finally) working right.
> 
> Last night I managed to pull an IP & DNS, but couldn't resolve
> *anything* -- I could ping the AT&T DNS & even some other IPS,
> but nothing else worked.
> 
> This morning, all is well. I'm 99.9999% all the problems are
> on their end.
> 
> Oh -- I'm in 80231, if that means anything.
> 
> Zonker
> 
> 
> rrarabie at attbi.com wrote:
> 
> > I'm in the 80212 ZIP code.  Apparently there is a problem with AT&T's DHCP 
> there.  I spent two hours trouble shooting with my three two Linux boxes, my 
> OpenBSD box, and my Mac before I broke down and called support.  I could not get 
> an IP assigned with any of those machines.  All were previously configured to 
> work with DHCP on the @home network, and all were working fine.  My OpenBSD was 
> the gateway so would get an IP assigned by @home and then it was assigning 
> 192.X.X.X numbers for the rest internally.
> > After 3 hours of frustrating hold time with AT&T this morning I can only say I 
> have a trouble ticket number.  They could not reach my modem from their end.  
> That contradicts what my modem says, as the two solid lights indicate that it is 
> receiving signal from an upstream provider.
> > 
> > I've got a long detail rant I sent them via a feedback website they have.  I 
> think I'll post it on usenet too, but won't do it here unless your interested.
> > 
> > Cheers!
> > 
> > Randy
> > 
> >>On 12-05 14:00, Joe 'Zonker' Brockmeier wrote:
> >>
> >>>Jeffery Cann wrote:
> >>>
> >>>
> >>>>Joe,
> >>>>
> >>>>I feel your pain.  I already went through section 3 of the DHCP mini-HOWTO,
> >>>>referenced by Brandon and I am still not able to connect as of this morning.  
> >>>>
> >>I
> >>
> >>>>am at work, so I cannot try some other ideas.
> >>>>
> >>>
> >>>Yes, the mini-HOWTO isn't much help. An actual config file that I can
> >>>modify is what I'm looking for. Don't be stingy people, post those
> >>>configs!
> >>>
> >>Here's my pump.conf:
> >>retries 3
> >>device eth1 {
> >>  nodns
> >>}
> >>
> >>eth1 is the "internal" interface on my firewall...eth0 is the external.
> >>
> >>All I did was run pump -i eth0. I am using RH 6.1.
> >>
> >>HTH,
> >>
> >>-- 
> >>Sean LeBlanc:seanleblanc at home.com Yahoo:seanleblancathome 
> >>ICQ:138565743 MSN:seanleblancathome AIM:sleblancathome 
> >>It is easier to change the specification to fit the program than vice versa. 
> >>Management QOTD:Ok. We need more meat and less pretty. Let's maximize our
> >>opportunities and our resources and optimize!, optimize!,
> >>optimize! the policies and procedures.
> >>
> >>_______________________________________________
> >>CLUE-Tech mailing list
> >>CLUE-Tech at clue.denver.co.us
> >>http://clue.denver.co.us/mailman/listinfo/clue-tech
> >>
> > _______________________________________________
> > CLUE-Tech mailing list
> > CLUE-Tech at clue.denver.co.us
> > http://clue.denver.co.us/mailman/listinfo/clue-tech
> > 
> > 
> 
> 
> 
> -- 
> Joe 'Zonker' Brockmeier -=- jbrockmeier at earthlink.net
> http://www.DissociatedPress.net/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> "Life moves pretty fast. If you don't stop and look around
> once in awhile, you could miss it." -- Ferris Bueller
> 
> _______________________________________________
> CLUE-Tech mailing list
> CLUE-Tech at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-tech