Author Topic: MSN Messenger  (Read 1245 times)

Offline SeCrEt_NiNja

  • stranger
  • Newbie
  • *
  • Posts: 35
  • Karma: +0/-0
    • View Profile
MSN Messenger
« on: July 09, 2003, 04:13:00 AM »
Hey guys,

Umm ok the layout of this problem is as follows:

I am on a home network with all the computers using windows XP Pro SP1. We have a gateway IP address 192.168.0.1 and my computer 192.168.0.254 I am using MSN messenger 6 now, and the problem is that I can't get it to send files.

I mapped the port 6891 TCP on the gateway to my computer which is what every thing that I have read says is the the port for MSN file sends and I have confirmed this with a port program but my sends still don't make it. I know that the other person is accepting the send and both of us don't have a firewall running. The person that I am trying to send to is not on a network.

Does anyone have any ideas that I could try to fix this?

Cheers,

Secret Ninja

Offline Josetann

  • admin
  • Administrator
  • Hero Member
  • *****
  • Posts: 10136
  • Karma: +0/-0
    • View Profile
MSN Messenger
« Reply #1 on: July 09, 2003, 12:04:20 PM »
I haven't used MSN Messenger much so this might not help.  In other software I have had to tell it what IP to use so sends would work.  Look for such a configuration option.  Basically you have to tell the software what the "real" IP is instead of the "fake" IP because it sends the PCs IP to the receiver.  If they receive a request from IP 192.168.0.254, they will never be able to acknowledge it.  If the request has your real, internet accessible IP, then it should work.

Offline SeCrEt_NiNja

  • stranger
  • Newbie
  • *
  • Posts: 35
  • Karma: +0/-0
    • View Profile
MSN Messenger
« Reply #2 on: July 09, 2003, 08:57:01 PM »
hmm worth a thought Josetann, but I was thinking that it would be much the same as setting up so that I could DCC send on IRC using MIRC. I had to tell the windows ICS software that any request for data on a port of 1024 was to be sent to my home (Fake) IP address, as people that I was sending stuff to where receving requests from my "real" IP address and because that machine wasn't sending anything I didn't get a reply and so both people just timed out.

From what I understand people will only be seeming my "real" IP address not my "fake" one which I use on the network and as such I would have to map a port that says for data on 6891 TCP port should be send to my computer.

Offline neldog2

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
MSN Messenger
« Reply #3 on: July 10, 2003, 08:23:24 AM »
That is correct. That is whole basis behind NAT and PAT that goes on in bigger networks.  The gateway maps a port to your IP address and anything that comes in on that port is relayed to your IP address.

Offline SeCrEt_NiNja

  • stranger
  • Newbie
  • *
  • Posts: 35
  • Karma: +0/-0
    • View Profile
MSN Messenger
« Reply #4 on: July 10, 2003, 06:03:31 PM »
I was pretty much sure that was the case neldog2, but I still can't send a file using MSN messenger on my network I have mapped the port. The strange thing is that I can start whiteboard shairing, which in theory needs the same kind of port mapping to work
« Last Edit: July 10, 2003, 06:03:54 PM by SeCrEt_NiNja »

Guest

  • Guest
MSN Messenger
« Reply #5 on: July 14, 2003, 10:48:19 PM »
My kid had the same problem even when he was going straight to the net on his own. He yanked 6 and re-installed 4.6 and his troubles went away. I don't have first-hand experience with it since MSN is not allowed anywhere near my machines. I keep his security holes away from me with a firewall.