On Friday 22 Oct 2004 01:00, Carroll Grigsby wrote:
> On Thursday 21 October 2004 12:42 pm, Anne Wilson wrote:
> > On Thursday 21 Oct 2004 16:50, David Johnson wrote:
> >>> snip
> >>>
> > > As for my replyto: address, what should it be set for?
> >
> > For mailing lists it should be set to blank.
On Thursday 21 October 2004 12:42 pm, Anne Wilson wrote:
> On Thursday 21 Oct 2004 16:50, David Johnson wrote:
>>> snip
> > As for my replyto: address, what should it be set for?
>
> For mailing lists it should be set to blank. It is often a good idea to
> have a new 'account' or profile set up
> Maybe I should qualify my previous statements. After boot, ifconfig
> indeed, shows that ETH0 is UP, however it does not get an IP address
> from the DHCP server. I have not yet tried it with a static IP
> address. In order for me to do any network communication, I must su
> to root and execut
Anne, my DHCP server is local. My modem/gateway is handling that job.
I have modified my replyto: address to be blank. Hopefully that will
make things easier for everyone. Thanks all for the advice.
On Thu, 21 Oct 2004 13:21:44 -0400, Edgars Smits <[EMAIL PROTECTED]> wrote:
>
>
> leave the
On Thursday 21 Oct 2004 16:50, David Johnson wrote:
> Maybe I should qualify my previous statements. After boot, ifconfig
> indeed, shows that ETH0 is UP, however it does not get an IP address
> from the DHCP server.
Is that a local dchp server, or your isp?
> I have not yet tried it with a st
Maybe I should qualify my previous statements. After boot, ifconfig
indeed, shows that ETH0 is UP, however it does not get an IP address
from the DHCP server. I have not yet tried it with a static IP
address. In order for me to do any network communication, I must su
to root and execute an 'ifup
Ever since I went to 10, now 10.1, same issue, on bootup eth0 shows as
failed, yet a few lines later when it does a time check it succeeds, and
when I log in the network is up and running. I seem to recall others
mentioned the same thing when 10 came out. Are you sure that it isn't
just slow to
No, it's not a 3com card and it is definately plugged in. It may help
to mention that this is a VM running under VMWare workstation. I have
compiled and installed the VMWare drivers. Now that I think about it,
could it be because the VMWare drivers don't load until after the NIC
would initialize
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 21 October 2004 05:46 am, David Johnson wrote:
> I'm having an issue with a machine that I just built using ml10.0
> where eth0 shows as having [Failed] the initialization at boot time,
> but if I su to root after boot and do an 'ifup eth0'
I'm having an issue with a machine that I just built using ml10.0
where eth0 shows as having [Failed] the initialization at boot time,
but if I su to root after boot and do an 'ifup eth0' it comes up with
no problem.
Can anyone explain why this might be happening and how to fix it?
Thanks
--
Dav
10 matches
Mail list logo