MSN messenger file transfer problem?1£$%
#1
Hi All
Ok my pc set up is as follows. 1 PC running win 2k and has a ADSL coming into it on the USB courtesy of NTL. This pc has a network card in it.
We have a hub and this pc plugs into it, along with another pc plugged into the hub running XP. So a pretty standard internet connection sharing thing is working pretty well.
Problem is, my pc running XP cant do the send a file to friend thing on MSN messenger. The pc with the USB connection going straight in however can!
I cant figure it out, my XP fire wall is turned off and the only other thing running on either pc is Norton 2003.
Any ideas folks!
cheers
Andy
Ok my pc set up is as follows. 1 PC running win 2k and has a ADSL coming into it on the USB courtesy of NTL. This pc has a network card in it.
We have a hub and this pc plugs into it, along with another pc plugged into the hub running XP. So a pretty standard internet connection sharing thing is working pretty well.
Problem is, my pc running XP cant do the send a file to friend thing on MSN messenger. The pc with the USB connection going straight in however can!
I cant figure it out, my XP fire wall is turned off and the only other thing running on either pc is Norton 2003.
Any ideas folks!
cheers
Andy
#2
Which direction are you attempting to send the file ?
Messenger sets up a fresh TCP connection direct from client to client to send the file. If at either end the Client is being "NATed" (Network Address Translated- its actual IP address is different to the Internet IP address - as happens with Windows ICS) then unless its possible to set some static configuration to work around it it wont work both ways as the device doing the NAT (your main PC in this case) doesnt know what to do with the new connection.
I *think* you should be fine if you attempt to transfer from the NATed (ICS) PC to somebody else but havenet tested it.
Microsoft KB article
Deano
Messenger sets up a fresh TCP connection direct from client to client to send the file. If at either end the Client is being "NATed" (Network Address Translated- its actual IP address is different to the Internet IP address - as happens with Windows ICS) then unless its possible to set some static configuration to work around it it wont work both ways as the device doing the NAT (your main PC in this case) doesnt know what to do with the new connection.
I *think* you should be fine if you attempt to transfer from the NATed (ICS) PC to somebody else but havenet tested it.
Microsoft KB article
Deano
#3
I used to get this issue talking to one of my mates - at his end he has XP, ICS and BT Openworld and at mine XP to Cisco router then ISDN/NAT to internet.
Since switching to MSN Messanger 5.0 the file transfer seem to work. I guess they have done some waccy tunneling over HTTP/existing connections. Then again I have had some other issues with the new app, so unless you REALLY need it, I would wait till Windows Messenger 5.0 comes out for XP.
Ids
Since switching to MSN Messanger 5.0 the file transfer seem to work. I guess they have done some waccy tunneling over HTTP/existing connections. Then again I have had some other issues with the new app, so unless you REALLY need it, I would wait till Windows Messenger 5.0 comes out for XP.
Ids
#4
Scooby Regular
Its true - I have WindowsXP and cannot send a file, BUT CAN receive one .................... I dont pretend to understand why?
So just e-mail instead
Pete
So just e-mail instead
Pete
#7
Sure, I believe it's the same way the conversation is initiated. Initiator sends IP address to respondent to set up the connection. Same for file transfer.
If the initiator has a bogus IP address (because of NAT) then there is no way of the remote client finding the correct return address. A lot of ISP's NAT ADSL connections.
If the initiator has a bogus IP address (because of NAT) then there is no way of the remote client finding the correct return address. A lot of ISP's NAT ADSL connections.
Thread
Thread Starter
Forum
Replies
Last Post