Printable View
I was downloading a few files (different sizes, type, user and different dates) and they both stopped at the same size 16384 KB! Then from then on it was 'More soureces needed'.
Anyone else had this, 'cause it's happened twice now - though I can't be sure of what file size it stopped at last time, though 16384 sounds about right.
As i said... Weird..
could be a bad download, what version of kazaa lite are you using
Kazaa Lite K++ -> Version 2.4.3
Build date -> September 24th 2003
Build number -> 1
Had it since it came out, also noticed the 'connecting...' thing since i got B'band.
Just to forestall questions about my system...
1Mb cable dsl - ethernet, winxp home, 512 ddram, 2.66 ghz P4, 129 BG HD.
ZoneAlarm Pro with Web Filtering version 4.5.530.000
Symantec antivirus corp edition version: 8.1.1.314
how long has it been since you went to broad band, and how long have you been using zone alarm, did you give access to kazaa lite in zone alarm to allow it. Who is your internet provider, the could be blocking P2P, are you on a school or business connection.
Find more sources for the file.
or
Use KaNAT
6 months on BroadBand, used ZA for about 18 months, home connection Kazaa++ configured correctly in ZA has access (ports 3079 - TCP and UDP, incoming and out).
What's KaNAT? what does it do and where can I get it?
The vast majority of the time I have no problems downloading, just these two occasions. Whenever I tried looking for other sources, it searched for a few seconds and then trid connecting to the original user.
I deleted the files, I'll probably try downloading them again from another source (if I can find one*lol*).
Thanks for Your help guys!
everything you wanted to know about KaNat but was afraid to ask :D
now that is very strange
Hi ........... I'm having the same problem ........ 4 different size files all from same user, all stopped at 16384kb. And of course there appears to be no other users with these wanted files. I have tried the suggested defrag ... no workie!Quote:
Originally posted by wipe709@10 March 2004 - 04:58
[SIZE=4] Kazaa Lite K++ -> Version 2.4.3
Build date -> September 24th 2003
Build number -> 1
Had it since it came out, also noticed the 'connecting...' thing since i got B'band.
Rather than repeat my same lengthy posts (again) all the details are in the Problems & Questions board under the 'Help...more Sources Always Pops Up' thread. Yep, seems the wrong thread for the problem, but someone in there was already discussing it, so that's where I dived in. :P
If anyone has answers to this problem I'd appreciate you having a look at my other post(s).
Thanks ...... Lysdexic
Try jumping supernodes.
Thanks, but it doesn't alter anything. I use that function often.Quote:
Originally posted by Mik3ll@11 March 2004 - 10:04
Try jumping supernodes.
It happened again ... 16384 KB! I hope this isn't a trend.
have you tried defraging yet??
The problem is that you simply cannot connect to that one source you have for the file. That is because the source is behind a router.
If you view the .dat file with K-Dat you'll probably see that the source has an 192.168.x.x or 10.x.x.x IP address. Those are internal network addresses of the source's network to which you can''t connect.
There is no solution other than finding additional sources.
But there was only one source, and I managed to download 16384 KB (and why this specific file size every time? - the 'weird' part).Quote:
Originally posted by Error403@13 March 2004 - 22:39
The problem is that you simply cannot connect to that one source you have for the file. That is because the source is behind a router.
If you view the .dat file with K-Dat you'll probably see that the source has an 192.168.x.x or 10.x.x.x IP address. Those are internal network addresses of the source's network to which you can''t connect.
There is no solution other than finding additional sources.
Why was I able to download that amount and then have it stop?
Isn't the firewall filter setting supposed to block these? It is checked.
The initial contact with that source works as it should be, but Kazaa doesn't store the NAT IP of that user, but the source's internal IP instead (blame the creators of Kazaa/FastTrack). So whenever a new connection attempt is made, a wrong IP is used.
The reason why it is exactly 16384 (2^14) is because the data is send in blocks (with the size a power of 2). After sending a block the connection is dropped and has to be re-established, which doesn't work.
Looks like one, doesn't it!Quote:
Originally posted by wipe709@14 March 2004 - 06:07
It happened again ... 16384 KB! I hope this isn't a trend.
I have sort of solved *some of that* problem. I read in another thread (No idea now which one sorry) about changing K-Lite's incoming port to > 32656 < in "Options > Firewall".
The point of the whole thread was to greatly speed up incoming files, which it did for me:)), but an unexpected bonus was that my 4 files that had 'hung'at 16,384kb for months!! resumed downloading. Two finished, two still waiting, but all of them
did move past the initial point where they were stuck.
Try it, hopefully will work for you too.
Lysdexic