Re: [cobalt-users] (no subject)

[Tim Dunn <tdunn@xxxxxxxxxxxxxxxxxxx>]

> I tried to access the Qube 2 from my browser as I have obviously done many
> times and it starts trying to "open the page" and gets about halfway there
> according to the status bar in my browser and then no further.

You can 'cut out the middleman' (browser) by telnetting to port 80 of
your qube2 and seeing if the web server is up.  There's no prompt, so
type "GET /" and 2 returns.  If you get a response, you're in the clear.
If not, time to get on-site.

> FTP fails along the same lines. It says connected and the next step should
> be the login prompt but it never comes...

I'm guessing this to mean that there is network connectivity to your box,
but the daemons (inetd) may be boggled.

Word of caution - inetd is a 'superdaemon' - it is given a list of ports
(/etc/services) and daemons (/etc/inetd.conf) to fork on specific ports.
FTP is usually run out of inetd.  Web servers are not.  Thus, if you can
get to the web server, but not the ftp server, then you're probably in
a world of hurt.  However, if the web server is down, but ftp works, you
may still be able to remotely nurse the box back to health.

I don't know Q2's, but did you install SSH?

tim

-- 
Mechanical Engineers build weapons.  Civil Engineers build targets.