🚀 go-pugleaf

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
> 
> 
> 
>