Re: [cobalt-users] We moved our RaQ4 and now we can't access it

["Joseph Lundgren" <josephl@xxxxxxxxxxxx>]

Problem solved.

It turns out that the virtual IP part of the configuration was still set to
the old IP address as listed below.  I configured the IP address and NetMask
properly via the front panel, but it wouldn't change the settings for
eth0:0... Why?  For system admins who ONLY use the GUI, this would have been
a disabling feature.

eth0      Link encap:Ethernet  HWaddr 00:10:E0:02:xx:xx
          inet addr:216.210.xxx.xxx  Bcast:216.210.xxx.xxx
Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5620 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4926 errors:0 dropped:0 overruns:0 carrier:0
          collisions:571 txqueuelen:100
          Interrupt:11 Base address:0x6200

eth0:0    Link encap:Ethernet  HWaddr 00:10:E0:02:xx:xx
          inet addr:206.58..xxx.xxx  Bcast:206.58..xxx.xxx
Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:11 Base address:0x6200

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:10029 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10029 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

Anyhow, on to the fix.  I finally got shell access (luckily, it turns out
that we did have telnet enabled for some reason) and executed the following
command:  /sbin/ifconfig eth0:0 216.210.xxx.xxx (the new IP address.)
Everything works properly now.  It was easier to fix than I'd have thought
it to be, especially considering that I'd probed it thoroughly, and come up
dry, prior to writing this list to ask for help.

Joseph Lundgren
Customer Service Support Representative
josephl@xxxxxxxxxxxx
Nu-World Communications
http://www.nu-world.com


> The problem is this:  We can ping the IP address.  We can FTP to that same
> IP address.  We can NOT SSH into that IP address (the SSH daemon was
working
> perfectly when the machine was in its previous location and had its
previous
> IP address.)  It WILL serve web pages, but only the page located at
> /home/sites/home/web/index.html.  It will NOT serve the administrative
> webpages which I would normally use to configure the system.  I cannot
> telnet (telnet is the DEVIL, and is thusly disabled, but I was desperate)
> into the machine.
>