Re: [cobalt-users] qube2 busy, but inaccessible, huh?

["Per-Otto Lekare" <peo@xxxxxxxxxxxxxx>]

I experienced the same problem. When assigning the Qube2 lowest IP address
(example 192.168.0.2) and the other computers higher IP's (ex. 192.168.0.3,
.4 ,.5 and so on), i finally got it to work. Hope this helps!
Regards,
Per-Otto
----- Original Message -----
From: "isao" <isao@xxxxxxxxxxxxxx>
To: "cobalt user" <cobalt-users@xxxxxxxxxxxxxxx>
Sent: onsdag, januari 19, 2000 22:00
Subject: [cobalt-users] qube2 busy, but inaccessible, huh?


> I just bought a Qube2 and a Restore CD.
>
> I couldn't connect to it out of the box either over the LAN or directly
> w/ a crossover ethernet cable.
>
> Then I did a CD restore-- so at least the primary ethernet port works.
>
> I set the Qube's IP# (valid and unique) and subnet (255.255.255.0). Left
> Gateway setting untouched.  And I still couldn't connect to the Qube with
> a browser at the Qube's IP, even with the same crossover cable, the same
> subnet, different IP of course...
>
> Then I shut down and reconnected the primary Qube ethernet port to the
> LAN with a strait ethernet cable. The ethernet port yellow activity LED
> went ON solid for a while and blinked heavily.  But I still could not
> access the Qube via a browser using the Qube's IP#. The Qube's IP# is
> valid and unique.
>
> Here's the weird part-- the aforemention LED is STILL going crazy many
> hours after setting it up.
>
> What the hell is the Qube doing?  It has an assigned IP, and no gateway...
>
> Any guidance would be greatly appreciated.
>
> Isao
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>