I'll pay someone if they can give me the answer

  • Thread starter Thread starter thedave
  • Start date Start date
T

thedave

Hi I've left messages in here before but the questions fall dead.
My file transfer rate Goes fantastic for about 20 seconds then they
practically stop dead. Like 0.5k a sec tops.

Here's the dialogue already had about this:

QUESTION: "If you click the Tools menu, then Options, then click the
Connection category, does it indicate that you're using a UPnP NAT?"
ANSWER:
It says:
You are directly connect to the .NET Messenger Service.
You are connected to the Internet through wired network connection. and...
You are connected to the Internet through a UPnP port restricted NAT.

I basically know what that means, but don't know if it's bad or not..
I've added many UPnP port forwards to my router settings.. directed at my
machine's LAN IP and it's still virtually halting aftter 3 seconds


QUESTION:
are you sending to the same person in particular? I ask because if they're
in some environment where outgoing connections are restricted, they would
see this problem which would be unrelated to you.
ANSWER:
-- The answer would be "no" - The transfer speed ALWAYS drops from regular
speed to about 0.5k/s after a few seconds no matter who I'm sending it to -
even if I send it to another MSN account on the same computer... (I loaded a
NG stuffplug's polygamy patch just to try it)

I've tried Forums, I've tried no router, I've tried no firewall, I've tried
uninstalling everything.. I've tried reinstalling. But the fuggin program
will NOT send files properly. What the HELL? (As you can see it's bee
going on for some time now and it is really starting to piss me off.)

And go.
 
Hmm.. if you can't send to your own PC it sounds like it's being blocked at the PC, thus
meaning there is some piece of software that's blocking the connection, even to your own PC.

To be fair, file transfer has never been of Messenger's strong points (although MSN Messenger
5 had things done pretty well) but it sure sounds from your evidence that things are being
blocked on the PC.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.
 
To be fair, file transfer has never been of Messenger's strong points

yes but now messenger live will have P2P folder transfer, a technology they
bought from foldershare and now is pesenting it as their own "magical"
innovation and idea....

Most people will never know, and MS will never tell...
 
but it sure sounds from your evidence that things are being blocked on the
PC.
Click to expand...
Which only begs the question.. what "blocks" a transfer? especially
since it was working fine a couple weeks ago.. It's still "leaks", it's
not completely blocked.. what on earth does that?

Confused as all hell....
 
Hi Kenny,

Not really, it's still the same thing with some synchronization.

I believe they had this support done before they even bought FolderShare as it's not exactly
difficult. For instance, you can make your own rather quickly using the FileSystemWatcher
class in the .NET framework.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.
 
Hi,

It's not "leaking" -- Messenger [obviously] is able to connect. After failing a direct
connection between you and your contact it then uses your existing connection to Messenger to
push through the file through (at a slow throttled rate) -- that's what you're seeing.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.
 
Then why buy foldershare? It is illogical.
I read that they would impliment the techology in the next messenger, and
they seem like they are doing it.
 
Hi Kenny,

The same reason why they bought two VoIP companies when there's already a dedicated group
within Microsoft that's been doing VoIP for years [and was included in Messenger for ages as
well].

Sometimes you buy companies for people, sometimes for technology and sometimes just to
eliminate competition ;)
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.
 
oh.... just like the borg assimilate biological entities..
I see now...


Jonathan Kay said:
Hi Kenny,

The same reason why they bought two VoIP companies when there's already a
dedicated group within Microsoft that's been doing VoIP for years [and was
included in Messenger for ages as well].

Sometimes you buy companies for people, sometimes for technology and
sometimes just to eliminate competition ;)
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

kenny said:
Then why buy foldershare? It is illogical.
I read that they would impliment the techology in the next messenger, and
they seem like they are doing it.
Click to expand...
Click to expand...
 
It's not a fix, but it may be a workaround. Try using Trillian. It'll
connect to MSN, but I think it uses different ports. My org doesn't
allow MSN Messenger to connect, but Trillian will connect. Worth a
shot...
 
Resistance is futile!
:)
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

kenny said:
oh.... just like the borg assimilate biological entities..
I see now...


Jonathan Kay said:
Hi Kenny,

The same reason why they bought two VoIP companies when there's already a dedicated group
within Microsoft that's been doing VoIP for years [and was included in Messenger for ages
as well].

Sometimes you buy companies for people, sometimes for technology and sometimes just to
eliminate competition ;)
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

kenny said:
Then why buy foldershare? It is illogical.
I read that they would impliment the techology in the next messenger, and they seem like
they are doing it.


Hi Kenny,

Not really, it's still the same thing with some synchronization.

I believe they had this support done before they even bought FolderShare as it's not
exactly difficult. For instance, you can make your own rather quickly using the
FileSystemWatcher class in the .NET framework.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

To be fair, file transfer has never been of Messenger's strong points

yes but now messenger live will have P2P folder transfer, a technology they bought from
foldershare and now is pesenting it as their own "magical" innovation and idea....

Most people will never know, and MS will never tell...

Hmm.. if you can't send to your own PC it sounds like it's being blocked at the PC,
thus meaning there is some piece of software that's blocking the connection, even to
your own PC.

To be fair, file transfer has never been of Messenger's strong points (although MSN
Messenger 5 had things done pretty well) but it sure sounds from your evidence that
things are being blocked on the PC.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

Hi I've left messages in here before but the questions fall dead.
My file transfer rate Goes fantastic for about 20 seconds then they practically stop
dead. Like 0.5k a sec tops.

Here's the dialogue already had about this:

QUESTION: "If you click the Tools menu, then Options, then click the Connection
category, does it indicate that you're using a UPnP NAT?"
ANSWER:
It says:
You are directly connect to the .NET Messenger Service.
You are connected to the Internet through wired network connection. and...
You are connected to the Internet through a UPnP port restricted NAT.

I basically know what that means, but don't know if it's bad or not..
I've added many UPnP port forwards to my router settings.. directed at my
machine's LAN IP and it's still virtually halting aftter 3 seconds


QUESTION:
are you sending to the same person in particular? I ask because if they're in some
environment where outgoing connections are restricted, they would see this problem
which would be unrelated to you.
ANSWER:
-- The answer would be "no" - The transfer speed ALWAYS drops from regular
speed to about 0.5k/s after a few seconds no matter who I'm sending it to -
even if I send it to another MSN account on the same computer... (I loaded a
NG stuffplug's polygamy patch just to try it)

I've tried Forums, I've tried no router, I've tried no firewall, I've tried
uninstalling everything.. I've tried reinstalling. But the fuggin program will NOT
send files properly. What the HELL? (As you can see it's bee going on for some time
now and it is really starting to piss me off.)

And go.
Click to expand...
Click to expand...
Click to expand...
 
Spyware software, Anti Virus software or indexing (Desktop Search) could slow
the transfer rate. In this case it's not blocking but your system is not
allowing the file to save as quickly as one would like. Try an FTP
connection and see if you get simmilar results. I'm not sure if MSN
MEssenger uses TFTP but if it does it could also be a local port sharing
issue.
 
Back
Top