Problem after transfert firmware sl-15-2 telnet connection
Posted: Sat May 17, 2014 9:12 amhello all, I have a problem with telnet unable to connect after transferring the firmware strandlone xfvdw-sl-15-2-cloudbox-30mar2014.
Telnet starts well after the file transfer tftp, but telnet does not connect to the network drive, and after 30 seconds timeout.
Ping works yet.
Do you have a solution for me? I did the same with the 199 firmware but same problem.
When i try it with putty, is the same problem of timeout.
I turn around,
instructions :
Switch off your NAS and follow the instructions that will appear in the main fvdw-sl console window, below some extra information:
(1) Answer the question in the dialog boxes that will popup.
First question will be if you are sure to do this, next if your device is a networkspace 2 classic or Lite, 5big_v2 or 2big_v2.
If you answer "no" the process will be aborted.
(2) Select the kernel file to be loaded
The file must be present in the directory used by the tftp server, a window will popup to let you choose a file.
It will have name like this "UIMAGE-26394-NWSP2CL-STANDALONE-xx". In future release this name may change.
(NWSP2CL means it is for lacie V2 family, STANDALONE means it is a kernel that will run from RAM, xx is a version number)
(3) Start your NAS as soon as a window pops up with the remark that it waits for u-boot.
When the NAS is starting it will be detected by the program and it will interrupt the boot, you will see two red flashes of the led's of the lacie nas indicating this.
After that it will transfer the kernel to the NAS and tries to load and start it.
(4) Wait until this command windows closes automatically.
(5) Wait for telnet client to start up
The script will wait for 12 seconds to start a telnet client enabling you to log in to the NAS.
The telnet window will pop up automatically after 12 seconds.
(6) Log in using the telnet client -------- impossible for me...
____________________________________________________________________________________________________________________________________
Log text tftp :
Connection received from 192.168.1.252 on port 2130 [17/05 09:52:31.593]
Read request for file <nwsp2\UIMAGE-395-NWSP2CL-199>. Mode octet [17/05 09:52:31.593]
OACK: <timeout=5,> [17/05 09:52:31.625]
Using local port 1576 [17/05 09:52:31.625]
<nwsp2\UIMAGE-395-NWSP2CL-199>: sent 8437 blks, 4319736 bytes in 48 s. 0 blk resent [17/05 09:53:19.296]
Connection received from 192.168.1.252 on port 1766 [17/05 10:29:59.750]
Read request for file <xfvdw-sl-15-2-cloudbox-30mar2014.bin>. Mode octet [17/05 10:29:59.750]
OACK: <timeout=5,> [17/05 10:29:59.750]
Using local port 1946 [17/05 10:29:59.750]
<xfvdw-sl-15-2-cloudbox-30mar2014.bin>: sent 138561 blks, 70943067 bytes in 783 s. 0 blk resent [17/05 10:43:02.968]
Telnet starts well after the file transfer tftp, but telnet does not connect to the network drive, and after 30 seconds timeout.
Ping works yet.
Do you have a solution for me? I did the same with the 199 firmware but same problem.
When i try it with putty, is the same problem of timeout.
I turn around,
instructions :
Switch off your NAS and follow the instructions that will appear in the main fvdw-sl console window, below some extra information:
(1) Answer the question in the dialog boxes that will popup.
First question will be if you are sure to do this, next if your device is a networkspace 2 classic or Lite, 5big_v2 or 2big_v2.
If you answer "no" the process will be aborted.
(2) Select the kernel file to be loaded
The file must be present in the directory used by the tftp server, a window will popup to let you choose a file.
It will have name like this "UIMAGE-26394-NWSP2CL-STANDALONE-xx". In future release this name may change.
(NWSP2CL means it is for lacie V2 family, STANDALONE means it is a kernel that will run from RAM, xx is a version number)
(3) Start your NAS as soon as a window pops up with the remark that it waits for u-boot.
When the NAS is starting it will be detected by the program and it will interrupt the boot, you will see two red flashes of the led's of the lacie nas indicating this.
After that it will transfer the kernel to the NAS and tries to load and start it.
(4) Wait until this command windows closes automatically.
(5) Wait for telnet client to start up
The script will wait for 12 seconds to start a telnet client enabling you to log in to the NAS.
The telnet window will pop up automatically after 12 seconds.
(6) Log in using the telnet client -------- impossible for me...
____________________________________________________________________________________________________________________________________
Log text tftp :
Connection received from 192.168.1.252 on port 2130 [17/05 09:52:31.593]
Read request for file <nwsp2\UIMAGE-395-NWSP2CL-199>. Mode octet [17/05 09:52:31.593]
OACK: <timeout=5,> [17/05 09:52:31.625]
Using local port 1576 [17/05 09:52:31.625]
<nwsp2\UIMAGE-395-NWSP2CL-199>: sent 8437 blks, 4319736 bytes in 48 s. 0 blk resent [17/05 09:53:19.296]
Connection received from 192.168.1.252 on port 1766 [17/05 10:29:59.750]
Read request for file <xfvdw-sl-15-2-cloudbox-30mar2014.bin>. Mode octet [17/05 10:29:59.750]
OACK: <timeout=5,> [17/05 10:29:59.750]
Using local port 1946 [17/05 10:29:59.750]
<xfvdw-sl-15-2-cloudbox-30mar2014.bin>: sent 138561 blks, 70943067 bytes in 783 s. 0 blk resent [17/05 10:43:02.968]