apt-get fails from embedded linux board

I am running Virtual Box Ubuntu Linux 2.6.
Connected to my PC is an embedded board running debian 2.6.32.
I have ip forwarding on at my virtual box.

From my embedded board I can successfully ping www.google.com.

I want to download and install some packages but when I try apt-get I get the following:
I've flailed away at this for most of the day and am out of ideas.

I am, as is probably obvious rather a newbie...
Suggestions?


unknown:~# apt-get install ftp
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
ftp
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 58.7kB of archives.
After this operation, 168kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
ftp
Install these packages without verification [y/N]? y
Get:1 http://ftp.debian-ports.org/debian/ unstable/main ftp sh4 0.17-23 [58.7kB]
Err http://ftp.debian-ports.org/debian/ unstable/main ftp sh4 0.17-23
Could not connect to ftp.debian-ports.org:80 (193.93.126.140). - connect (110: Connection timed out)
Failed to fetch http://ftp.debian-ports.org/debian/p....17-23_sh4.deb Could not connect to ftp.debian-ports.org:80 (193.93.126.140). - connect (110: Connection timed out)
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

nslookup both addresses.

Sorry but I don't see how nfslookup helps.
There is no problem in my system deriving the actual IP address from the name.

I want to know why this is failing:

Could not connect to ftp.debian-ports.org:80 (193.93.126.140). - connect (110: Connection timed out)



In fact it appears that it actually connects and pulls some data down and then stops as I see the following.

2% [1 ftp 1211B/1240B 97%]

which is then overwritten with
Could not connect to ftp.debian-ports.org:80 (193.93.126.140). - connect (110: Connection timed out)

Suggestions?

Thank you!

Mark

You may be correct. If you had tried it, and it then did as you suspect, I'd have felt better about you claiming it was a stupid test.

Most posts point to proxy issues but I guess on an embedded board it can't support enough ram space or such and fails like that.