Re: Existing DSL not detected by re-install

From: Kevin Nathan (knathan_at_project54.com)
Date: 03/23/05 

Date: Tue, 22 Mar 2005 20:06:51 -0700

On Tue, 22 Mar 2005 08:13:48 GMT
lakester <lakester@unknown.invalid> wrote:

> On Tue, 22 Mar 2005 00:09:08 -0700, Kevin Nathan
> <knathan@project54.com> wrote:
>
> >The modem works under Windows, so it's setup already.
>
> That's what I said. I'm beginning to notice that your late night posts
> show up on my server. I just checked a.o.l.s in Google groups and my
> replys haven't shown up there yet. I miss so many posts I down bother
> downloading into Agent except to post my own stuff.
>

You might want to consider:

   http://news.individual.net/

It used to be free, now they are charging 10EUR/year. Not a bad price at
all so I popped for it right away (about 13USD). I've never had any
problems with them, have been *very* happy with them. They don't carry
any binary groups but I don't care about that.

> >You have to setup your network (NIC) to have the correct gateway
> >and DNS servers.
>
> It's like working on the car. I *could* do it, but the mechanic has
> already done it 25 times, so it's a cake walk for him, for me, nothing
> but misery and busted knuckles.
>
> Huh? You mean this stuff? Mr. Bolt directed me to that Web page.
>

Yes, that should give us most of what we need.

> IP Address 69.226.18.83
> IP Gateway 69.226.19.254

These two you don't need -- it's the IP address of the modem that the
outside world will see as you, and the gateway that the modem uses.

> DNS Servers 206.13.29.12 dns1.lsanca.sbcglobal.net
> 206.13.30.12 dns1.sndgca.sbcglobal.net
> Modem IP Address 192.168.0.1

These are important. The 'Modem IP Address' is what your network will
use as the gateway. You should be able to see that somewhere in Windows.
And, no, I don't know where (see later comment). :-)

Go into YaST Control Center -> Network Devices -> Network Card, then in
the dialog box where it says 'Already configured devices', click on the
'Change' button. Click on the network card you're using (in case there's
more than one) and then click the 'Edit' button.

Here's where we have to do a little guessing. Do you *know* if you
assigned an IP address, or are you getting one via DHCP? If you don't
know for sure, let's try DHCP first. Under 'Choose the setup method'
select the 'Automatic address setup (via DHCP)' radio button. However,
if you know that you assigned a static IP, enter it here after checking
the 'Static address setup' radio button. The IP address goes in the 'IP
Address' box and the 'Subnet mask' should contain (enter if not there):

   255.255.255.0

Next, click on the 'Host name and name server' button. Type in a host
name and domain (e.g., on this box I use 'efreet' and 'linux'). In the
'Name Server 1' box, enter:

   206.13.29.12

and in the 'Name Server 2' box, enter:

   206.13.30.12

(these are from the values above). Now, in the 'Domain Search 1' box,
put in the domain you entered above (e.g., on my box that would be
'linux'). Then click the 'OK' button.

Back at the previous dialog box, click on the 'Routing' button. In the
'Default Gateway' box, enter:

   192.168.0.1

and make sure the 'Expert Configuration' and 'Enable IP Forwarding'
check boxes are *not checked*. Click the 'OK' button. Finally, click the
'Next' button and it should restart your network.

> Ethernet Status Connected
>
> >You can check the settings in Windows for these values.
>
> Where?
>

I don't know. In Win98 I used to right-click on Network Neighborhood and
select the interface device and then select 'Properties'. No idea where
that might be in any later version . . .

> Thanks, lakester...what *is* the proper torque value for a head bolt?
>

Um, just immediately before shearing off? ;-)

You're welcome! 

-- 
Kevin Nathan (Arizona, USA)  
Open standards. Open source. Open minds. 
The command line is the front line.