Re: Network Configuration Utility

[Robert Krueger <rlk01 frontiernet net>]

Michael Thomas wrote:
> 
> Are you trying to get the ethernet working .???

 Yes and no.  The DSL works fine through eth0 if I do as I said below. 
The problem is in the Interface section.  When you select an Interface
type, ppp0 for instance, which is currently labeled "Inactive", and
click on the "Activate" button, the interface, if properly configured,
should toggle immediately to "Active", as mine does also.  I suspect
that there is a parameter missing somewhere with the eth0 interface,
however.  If I click on "Activate", nothing happens, and the dialog
freezes.  Pushing any other buttons in the Interface dialog is useless,
it is "hung".  So now, if I log out, then log back in, and reselect
Network Configuration Utility, go to the Interface section once again,
the eth0
Interface will now be listed as "Active", and my DSL Internet connection
through the ethernet card works fine and normal.
   A bigger, but similar problem occurs if I select "atboot" in the
Interface section. 
( Anotherwords, bring up eth0 at boot-up )  The boot-up process goes
normally, and these next two lines appear in the boot screen:

   Bringing up interface lo
   Bringing up interface eth0

...and now the computer sits there until the chips burn out.  So I know
that the DHCP or ethernet connection is having a problem somewhere, but
by doing what I said above, I can get it to work.  My DSL connection
requires that DCHP be set as the Protocol type in the Interface section,
as the IP address is server assigned only.  It's a weird problem, but I
don't know where to go to solve it.

Thanks,
Robert
> 
> Robert Krueger wrote:
> 
> > Hello,
> >    I'm not sure where to post this question, which is really what I'm
> > asking.
> > I'm establishing a DSL Internet connection through an ethernet card
> > (eth0), and setting this up through the Network Configuration Utility. (
> > System / Control Panel )   When I go to activate the connection, the
> > dialog box hangs up, and the only way I can do anything else is to log
> > out, and log back in.  When I log in again, the ethernet connection is
> > "active", and my DSL is working fine.