Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File transfer problem #285

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 10 comments
Open

File transfer problem #285

GoogleCodeExporter opened this issue Mar 14, 2015 · 10 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. You'll need 2 accounts which each one contains the other in its contact list.
2. Sign in with the first account using the test client
3. Sign in with the second account using WLM 2009
4. Try to send a file (a few MB) from the test client to the other account.

Only a few kb are sent and then the file transfer process stops. WLM stops 
updating it's file transfer progress bar.

What version of the product are you using? (MSNPSharp, OS, Mono etc.)
MSNPSharp 4.x Latest SVN version, Windows 7 x64, .NET 2.0

Original issue reported on code.google.com by corbitWi...@gmail.com on 19 Jul 2011 at 11:58

@GoogleCodeExporter
Copy link
Author

Another File transfer problem:

Client A: MSNPSharp 4.x, Client B: WLM 2009, OS XP SP3.
Client B send a big file to Client A, That is ok.
If client B send second file to client A when the first file is transferring, 
Client A can't be prompted there is a new file need receiving. At the client B 
side, the second transferring is never start.

Original comment by aj.q...@gmail.com on 25 Jul 2011 at 1:18

@GoogleCodeExporter
Copy link
Author

Original comment by freezing...@gmail.com on 25 Jul 2011 at 10:44

@GoogleCodeExporter
Copy link
Author

[deleted comment]

1 similar comment
@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Is there any progress regarding the bug? It seems that still exists...

Original comment by corbitWi...@gmail.com on 29 Nov 2011 at 3:32

@GoogleCodeExporter
Copy link
Author

Hi,

We actually know what cause this bug, but due to our limited resource, fixing 
this issue is in low priority (It needs kind of a lot of code). I know it is 
frustrating to hear this, but please understand the current development (And 
almost the whole project as well) were done by only to volunteers. There is 
people trying to fix this (me), but currently he is working over 90 hours per 
week. We appreciate your patience and time.

Original comment by freezing...@gmail.com on 29 Nov 2011 at 11:40

  • Changed state: Accepted
  • Added labels: Priority-Low
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

Thanks! :)

Original comment by corbitWi...@gmail.com on 30 Nov 2011 at 9:44

@GoogleCodeExporter
Copy link
Author

Hi guys,

I don't know if my problem has the same cause as the problem mentioned above 
but i think it is so i post it here.

I created a handle to the event "P2PHandler.InvitationReceived" and i 
immediately call a decline.

I connect to wlm 2011 with account A and connect to my own client with account 
B.

1) I send a file from WLM to my client.
I see the transfer is declined by my client in WLM.

2) I send a file again (doesn't matter if it is a different file or not) from 
WLM to my client.
I don't see anything happen and the file is waiting for acception in WLM.

Is this working as it should be or is there something wrong? 

Original comment by freakysm...@gmail.com on 10 Dec 2011 at 5:59

@GoogleCodeExporter
Copy link
Author

In the example client the same thing happens.
The weird thing is it works when running in debug mode but not when running in 
release mode.

by the way... im talking about 4.5.1.2582

I've also updated from svn (5.0.0.2612) and the same thing happens.
It works in debug but not in release.

Original comment by freakysm...@gmail.com on 10 Dec 2011 at 9:35

@GoogleCodeExporter
Copy link
Author

I'm developing a MSN proxy. And my proxy is having the same problem that 
occured on attachment "log.txt". 
After the client receives this command:
801 $trId $payloadSize $secondsToWait $unknown %unknown
It wait $secondsToWait seconds to send a new message with trId + 1.
Sometimes before my proxy send this command "801", it has already received a 
command from the other side. So after the proxy send the client command after 
"801"(received from the server), the server returns a command "800 $trid 0" 
referring the last command sent. When that happens, the download bar at msn's 
client stop. Is my assumptions right? Do you know how to fix that? Do you know 
how 801 and 800 commands work?

Original comment by vro...@gmail.com on 12 Apr 2012 at 3:12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant