🚀 go-pugleaf

Bruce,
    If you still have the diskette and files for the NIC you have, you don't
have to replace the NIC with a different one, but as Fernando said in his note,
I likewise had a friend who no matter what we did could not get back on.  What
we did do, was to go to the device manager, and look for the NIC, hit remove,
and let Windows "rediscover" the card. Reload the drivers and the settings.
    The difference in his case though was that his system (for whatever reason)
did not see the card in Winipcfg after he ran the ATTBI utility.  That doesn't
seem to be your scenario.  From what you are saying, Winipcfg sees the card, you
are getting all valid addresses, but just can't talk to anything.
    You can bet on the fact that even if you can schedule someone to come to the
house, they're going to say it is the machine (which I think they are able to
charge for these days), but I guess you can counter with "it worked fine before
the change over".  I'm still betting it has something to do with the modem not
being recognized on the network.  I know it is a wait, but I'd try to get
through to support and ask them to make sure the modem is registered.  Thanks
for the thank you by the way, but it must have been someone else to help in the
registration IPs <grin>!

Jay S.


"Bruce G. Karnacki" wrote:

> "Jay Sottolano" <sottola@attbi.com> wrote in message
> news:3C1AC6E6.77EE542E@attbi.com...
> > Bruce,
> >     I'll assume the obvious here in that you also power cycled the modem
> as
> > well?
> Yes.
>
> I also wonder if there is a delay in registration, although you say you
> > are getting all the addresses, correct.
> Yes, it's now been 4 hours.
>
> If you do a WINIPCFG /ALL from the
> > Start > Run menu, are you getting a full compliment of addresses assigned
> to
> > the adapter?
> Yes.
>
> >     I'd also try to ping and use the browser for some site, but use the IP
> > address and see if you get there.  When I ping www.google.com, I get back
> an
> > address of 216.239.37.101
> pings to 198.133.219.25 (www.cisco.com), 64.58.76.177 (www.yahoo.akadns.net)
> Time Out
> as do all IP pings
>
> >     Try to get there first with the qualified name, and then the IP
> address.
> > If the www attempt fails, and the IP works, you know you are on the
> network,
> > and the problem is DNS resolution, or getting to the DNS'.
> Both fail.
>
> In addition, a ping to his gateway, 12.246.96.1, (from his machine, of
> course) times out.  I can ping from here.  He's in Sacramento, I'm 130 miles
> south in San Carlos, CA.
>
> Thanks, Jay.  I belive you are the fellow who provided the attbi
> registration IPs.
>
> Bruce
>
> >
> > Jay S.
> >
> > "Bruce G. Karnacki" wrote:
> >
> > > Fernando,
> > >
> > > When I say that the machine is set DHCP, I mean it is not set static,
> not
> > > that Use DHCP for WINS resolution is enabled.  All settings are as you
> > > suggest, below.
> > >
> > > Thanks for the reply,
> > > Bruce
> > >
> > > "Fernando L" <no.spam.for.me@hotmail.com> wrote in message
> > > news:Xns9177CB31E89A9fernlab@216.148.227.77...
> > > > Bruce,
> > > >     If I remember the AT&T manual configuration instructions
> correctly,
> > > > you are NOT to set DHCP. That is, in your TCP/IP Properties -> WINS
> > > > Configuration tab - you should have "Disable WINS Resolution" selected
> > > > instead of "Use DHCP for WINS resolution". Unfortunately I can't check
> > > > this on my system because I am using a router which changes things a
> bit.
> > > >     Also, while you are in TCP/IP Properties make sure you have
> Disabled
> > > > DNS, set it to Obtain an IP address automatically, and all Gateways
> are
> > > > blank. Once you have made all these changes, click OK, then reboot (it
> > > > will probably ask you to reboot - but reboot whether it asks you to or
> > > > not). This ought to work.
> > > >
> > > > "Bruce G. Karnacki" <karnacki@invalid.com> wrote in
> > > > news:DHwS7.25719$7y.326322@rwcrnsc54:
> > > >
> > > > > Two nights ago, dad swapped out an RCA 205 for an RCA 235 modem.  We
> > > > > then tried to get to the ATTBI registration web page using any of
> six
> > > > > IP addresses provided by another member a few days ago.  None of the
> > > > > six worked.  Turns out Dad had partially installed AOL on Dec. 1, in
> an
> > > > > attempt to get back online, and his browser was set to use a dial-up
> > > > > connection. But, because he never completed the installation, the
> thing
> > > > > never got a dial-tone, which would have indicated (to me) to disable
> > > > > the dial-up connection.
> > > > >
> > > > > We discovered it today when going through the network configuration
> > > > > properties.  He had a bunch of AOL network components installed.  We
> > > > > uninstalled them all, and disabled the dial-up setting in IE.
> > > > >
> > > > > We were then able to go to 12.242.16.9 and enter the ATTBI
> registration
> > > > > page.  We entered all 16 digits of his subscriber id in the first
> box,
> > > > > and the last 9 digits of this same number in the second box.  We hit
> > > > > "Submit", and it said he was now subscribed.
> > > > >
> > > > > We then tried to go to http://newuser.attbi.com to get to the new
> ATTBI
> > > > > settings/configurator.  (I'd do it myself manually, but at this
> point,
> > > > > it would be easier for Dad to just do it automatically.)  But, no
> go.
> > > > > We get can't locate server.  We tried to go to some other sites,
> like
> > > > > www.netscape.com, but no go either.  Same error.
> > > > >
> > > > > He's set DHCP, and all other properties look correct.
> > > > >
> > > > > I feel like we're 99% there.  Any ideas at this point?
> > > > >
> > > > > Thanks again,
> > > > > Bruce
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> >