since last December (was 1.4.7) there is no way to download files. Thanks for "0 uploads" fix in 1.4.9
Now I get "206 get error" or "timed out". My suspi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you clarify your post - I believe it got truncated. Particularly, what platform are you on (linux, cygwin,...)
I have been able to download files with nap 1.4.7 and above. "206 get error" means that the remote client has refused the download, and "timed out" means that there was no response from the server or remote client in a reasonable time (currently 90 seconds). This is not a bug. You may want to try downloading many files, as in "/get 1-20". A certain percentage will succeed. -- Peter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I'm on FreeBSD-4.5+nap-1.4.9. It worked like a charm back in November/December, it was then FBSD4.4+nap 1.4.7. I tryed conveyer way doesn't work either. Have no clue.
How could I catch nap connection logs ?
Thanks Vlad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there is another observation: all the uploads
from my libraries are timed out, as it was before though. Well, kinda to know how happy are the
Windowz users. Did they all upgraded to the new
napigator to share nothing (by default) ?
Thanks Vlad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am still not sure exactly what the problem is you are describing. If you want to get a log of nap's "traffic", you can set "/debug 2". Then you'll see all the napster protocol messages sent between nap and the server.
Are you unable to download any files, ever, or are you just saying that a large percentage of downloads do not succeed? The latter would be relatively normal, especially considering that many of the popular Windows clients tend to be crappy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the latter seems to be the case. I would get 2 out of 15, say, if I would at all. The number droped sharply since December, but could be there is
someth. server related too. My "lucky" connections were to high rank servers (which was 62.xxx AFAIR), all those fly now by "broken pipe"
or "timed out"for most time. Well, never mind. How do I get info about client's type (WinMX etc)?
Thanks, Vlad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
since last December (was 1.4.7) there is no way to download files. Thanks for "0 uploads" fix in 1.4.9
Now I get "206 get error" or "timed out". My suspi
Could you clarify your post - I believe it got truncated. Particularly, what platform are you on (linux, cygwin,...)
I have been able to download files with nap 1.4.7 and above. "206 get error" means that the remote client has refused the download, and "timed out" means that there was no response from the server or remote client in a reasonable time (currently 90 seconds). This is not a bug. You may want to try downloading many files, as in "/get 1-20". A certain percentage will succeed. -- Peter
Hi
I'm on FreeBSD-4.5+nap-1.4.9. It worked like a charm back in November/December, it was then FBSD4.4+nap 1.4.7. I tryed conveyer way doesn't work either. Have no clue.
How could I catch nap connection logs ?
Thanks Vlad
there is another observation: all the uploads
from my libraries are timed out, as it was before though. Well, kinda to know how happy are the
Windowz users. Did they all upgraded to the new
napigator to share nothing (by default) ?
Thanks Vlad
I am still not sure exactly what the problem is you are describing. If you want to get a log of nap's "traffic", you can set "/debug 2". Then you'll see all the napster protocol messages sent between nap and the server.
Are you unable to download any files, ever, or are you just saying that a large percentage of downloads do not succeed? The latter would be relatively normal, especially considering that many of the popular Windows clients tend to be crappy.
the latter seems to be the case. I would get 2 out of 15, say, if I would at all. The number droped sharply since December, but could be there is
someth. server related too. My "lucky" connections were to high rank servers (which was 62.xxx AFAIR), all those fly now by "broken pipe"
or "timed out"for most time. Well, never mind. How do I get info about client's type (WinMX etc)?
Thanks, Vlad