That just means that the person she is exchanging files with has a public address and goes right along with my explanation. The person sending here a file actually tells her MSN client to pull the file from the sending PC.
This MS technote explains it quite well. http://www.microsoft.com/technet/prodtechnol/winxppro/evaluate/worki01.asp?f rame=true#d Check the NAT and messenger topic heading. [PS: My daughter is just as frustrated! she wants 2 do voice/video] on 17/12/2002 00:18, Gerry Doris at [EMAIL PROTECTED] wrote: > On Mon, 16 Dec 2002, Thomas V. Fischer wrote: > >> This actually only works on older versions of MSN Messenger (pre 4.x). Now >> MSN uses UPnP which is only supported by Microsoft ICS type firewalls. >> >> You wonąt be able to initiate any video/audio or file transfers from behind >> a linux NATed firewall. MSN has changed its method considerably. The >> initiator of the connection actually tells the receiver to pull (there is no >> more push). The initial communication is done through the exchange of http >> commands via the MSN main server. Inside this http command is your internal >> IP address and port. Unless you have application level filtering and NATing >> you wonąt be able to change this information as it is done from with in the >> MSN client. >> >> rgds > > I just checked with my inhouse MSN guru (my daughter) who is using V5. > She says that she can accept files from others but is unable to send them > files. When she tries she gets a service not available message. > > She thought it was something I had done. Frankly, I wish it were the > other way around...can send but not accept. She's never tried to use > voice. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
