[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] [Qube2] No Response
- Subject: Re: [cobalt-users] [Qube2] No Response
- From: Mike Vanecek <nospam99@xxxxxxxxxxxx>
- Date: Wed Apr 19 10:46:36 2000
- Organization: anonymous
Not sure I can offer much help - too new at this, but take a look at the
response I posted to the same question from "Gerald Waugh"
<gerald@xxxxxxxxx>. (Are you two related or using the same Qube2?)
On Mon, 17 Apr 2000 14:53:12 -0400, Jerry Waugh <jwaugh@xxxxxxxxxxx> wrote:
:>Help
:>I commissioned a new Qube2 Friday evening, entering the Primary IP, Subnet
:>Mask, and Gateway IP. Connected to the Qube2 via my Browser, everything
:>looked good. It was late so I quit working for the day.
:>The next morning I could not connect to the Qube2 with the browser, ping,
:>trace, telnet, ftp or anything. I rebooted the Qube2 and the LCD displayed
:>all the correct information except (it spent a long time looking for a DHCP
:>host?). It still did not work. The Ethernet indicators indicate that the
:>Ethernet card is functional.
:>Has anyone had this experience? What is wrong?
Do not know if it will help, but maybe try resetting the ip filters and
network settings from the LCD. Then see if you can start again??
:>I guess I need to connect to the serial port? Is there a good serial
:>communications app for Linux? what should I use? I tried minicom in Kermit
:>mode, but it did not seem to work.
See my post to Gerald about a recent post on capturing boot information from
the serial port in case it might help determine what is going wrong.