Unable to manually start upload

[BernardP]

When I try to manually start the upload of someone who is in my upload queue (using Openap), I will get a "Disconnected" message. But the user is still connected and we can still exchange messages. He will retry, re-enter the queue and, as soon, as I right click "Start transfer now", he will appear as disconnected again.

Anyone else has seen this?

I have 3.3, cable modem and Win 98 SE

[PiRaNeTuS]

It could also depend on whether or not you have some sort of firewall or router or anything of that nature. If you do, this likely isn't the reason, but still, it COULD be the reason. Messages are sent in a different protocol from actual files, so that could be a reason why you can talk to him, but can't upload. If you are not under any type of firewall, maybe the other person is.... Also, what program are you using? WinMX or something else?

[BernardP]

I am using winMX 3.3. To offer decent up load speed, I am allowing 2 uploads at a time. Other uploaders are put in queue.

Usually, I can manually start a third or fourth upload, by right-clicking "Start transfer now" when I see that my first two uploads are slow (56 K).

But sometimes, when I do that, the "user disconnected" message appears instead of the uploads starting, even if the user is in fact not disconnected. I have observed this with openap servers, not with the WinMX protocol.

I use Zone Alarm, on Medium setting. It does not seem to cause any problem.

[SiANiDE]

BernardP,

There are a few of reasons why you could be getting a "Disconnected" message when you try and start an upload. Normally I have found it's the user who is trying to download off you's fault. They may have:

1. More of the file than you do (ie when incomplete).

2. A corrupt file and hence cannot resume.

3. Simply run out of disk space!

Does it happen to every user who you try to start? Or is it a particular file which you have problems with?

[BernardP]

It happens only from time to time, and not always with the same file or user.

I will try to see if version 3.31 has somehow solved this.

Thanks