Re: Can't connect after ResetSysConf

Heh Dude!
     Just want to let you I have almost the same problem just that
after flashing Unslung-3.18-beta.firmware and running smoothly for two
days , the ready/status keep flashing all of a sudden after I power
off and on the third day, I tried to connect via the web on
192.168.1.77 and my previous ip setup 192.168.2.88  , it still cannot
find the server not sure which IP it is now running. The strange thing
is that the ethernet light is ok (constant light up green). Any one
knows what other ip it is running otherwise may have to resort to ip
scanner to find out the ip address, BTW i had a hard time trying to
log in via redboot and lots of time i cannot connect because I don't
know whether it is booting at 192.168.0.1 ??

Any body ?

Thanks
Hunter
--- In nslu2-linux-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx, "kbizz30" 
<kbizz30@xxxx> wrote:
> 
> My problem. After upgrading to firmware Unslung-3.18-beta-
> firmware.zip. I messed up and the Ready/status led started to flash 
> red/green and the slug was "dead". I enterd RedBoot by telnet and 
> did a ResetSysConf as described at "www.nslu2-
> linux.org/wiki/HowTo/ResetSysConf" and used orginal firmware 2.3R25
> 
> Ewerything went OK, no errors, but then i try to connect via telnet 
> or by webbrowser it can't find the slug. IP after reset should be 
> 192.168.1.77 but nope. My old IP 192.168.0.4 doesent work either...
> 
> What I can see from the leds it works OK but I can't connect to it!
> Is it possible to set another IP adress from RedBoot or is it 
> perhaps a SAMBA problem?
> 
> Anyone that can help me?
> 
> Thanks!
> 
> (PC XP SP2)





[ Moderator Note: All static information is slowly moving to the Wiki at 
http://www.nslu2-linux.org ]