IceBox2 FTP Help

Started by sambo, September 05, 2006, 07:21:15 PM

Previous topic - Next topic

sambo

I have had my Toppy Masterpiece for a month now and have been reading this forum with great interest.

Thanks to all you Toppy Gurus for all your tips.

I just received my IceBox2 last night and got it up and running with no problems.

I have a problem I hope you can help me with - I am trying to download some recordings (.REC Files) but my FTP Client SmartFTP keeps giving me an error 550 and will not download!

I have tried just changing some file names but get the same error message.

I am logging into the IceBox2 with the Static IP address I have given it, and the login and password are anonymous.

Is there something I am doing wrong?
:(

srto2

G'day Sambo,

I replied on The Topfield forum as well.

I think you just need to connect to 127.0.0.1 (localhost).  Give it a go.

Cheers,
Rob

peteru

Don't listen to Rob :D

Using 127.0.0.1 (localhost) is not going to work for a device on a network.

Chances are that your FTP client is trying to connect more than once. You will need to disable that feature, so that your PC only uses a single connection to the IceBox2 FTP server.

srto2

Quote from: peteru on September 05, 2006, 07:36:52 PM
Don't listen to Rob :D

Using 127.0.0.1 (localhost) is not going to work for a device on a network.

Chances are that your FTP client is trying to connect more than once. You will need to disable that feature, so that your PC only uses a single connection to the IceBox2 FTP server.

Hah!  I'm trying mine tomorrow-ish, so I was probably talking out of my ar$e.   The Guru might be right  ;D   

Cheers,
Rob

vincent

I downloaded smartFTP - I have WS_FTP on my computer but this would not connect.  D/L smartFTP, ran, typed in the IP address and pick anonymous and it worked.  Suggest you give smartFTP ago - goggle smartFTP for the web site.

sambo

peteru

I was told by IceTv help line that you cna help me with this?

As I said before, It starts downloading, but fails after 1-10 minutes! So I tried the transfer Queue with auto resume but after it resumes 3 times it can not reconnect again.

I looked on the Info page on the IceBox2 and the USB connection had FAILED.

So I rebooted the IceBox, tried again but it did the same thing!!!!!

The Ice help line said to post my system log from the IceBox 2 and you can tell me if the a hardware problem?????

Sep 9 06:27:20 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:27:22 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:27:24 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:28:28 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:28:30 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:28:32 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:29:03 (none) syslog.info -- MARK --
Sep 9 06:29:36 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:29:38 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:29:40 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:30:44 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:30:46 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:30:48 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:31:52 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:31:54 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:31:56 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:33:00 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:33:02 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:33:04 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:34:08 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:34:10 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:34:12 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:35:16 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:35:18 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:35:20 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:36:24 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:36:26 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:36:28 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:37:32 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:37:34 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:37:36 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:38:40 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:38:42 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:38:44 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:39:48 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:39:50 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:39:52 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:40:56 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:40:58 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:41:00 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:42:04 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:42:06 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:42:08 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:43:11 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:43:13 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:43:15 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:44:20 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:44:22 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:44:24 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:45:28 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:45:30 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:45:32 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:46:36 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:46:38 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:46:40 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:47:44 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:47:46 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:47:48 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:48:52 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:48:54 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:48:56 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:49:03 (none) syslog.info -- MARK --
Sep 9 06:50:00 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:50:02 (none) kern.debug udhcpc[834]: Sending discover...
Sep 9 06:50:04 (none) kern.debug udhcpc[834]: Sending discover...

this is just a sample of my system log for the IceBox2, there aare hundreds of lines like this.

so what do you think Peter?

peteru

Powercycle the Toppy.

The Toppy USB implementation suffers from many issues, you are experiencing one of them. Put the Toppy to standby by using the remote control or the button on the front. Wait for about 5-10 seconds, then unplug the the Toppy from the powerpoint. Wait 20-30 seconds, then plug the Toppy back in.

Toppy USB lockups can be solved by restarting the IceBox2 about 75% of the time, but the remaining 25% will require the Toppy to be restarted.

Also ensure that you have a good quality USB cable and that it is properly inserted on both ends.

The system log looks good.

vincent

System log looks like mine - I get the same message ever ~30sec from memory

sambo

Hi Guys and Gurus,

Just an update-

Thanks to Daniel at IceTv who not only replaced my Icebox but also upgraded me to the WL-500g Premium :D

Still called the IceBox2 but with an upgrade wireless card (same firmware)

I am now downloading my recording wireless   :D

I would like to thank Daniel for all his help and great service from IceTv.

Sambo