Topic: i need to open poort 1863 ???

[john vl]

Hi
I need to open that port want i need to send files by useing the microsoft messenger....
Or does anyone knows how to solve this problem......

Thanx
John

[john vl]

This is the story :
This topic describes the settings that Windows Messenger uses for file transfer. Perhaps they will be useful to you in configuring your firewall or proxy server.

For file transfer Both incoming and outgoing TCP connections use this range of ports: 6891 to 6900. This allows up to 10 simultaneous file transfers per sender. If you open only Port 6891, users will be able to do only one file transfer at a time.

The TCP ports must be configured so that sockets on a port remain open for extended periods of time


How do i do this on my esmith 4.1.2?????

[Michiel]

Hi John,

I've got exactly the same problem.

Browsing through the internet I've found two methods that *should* solve this but don't work for me. I'm probably doing something wrong, I just don't see it.

----------------------------------------------------------------------
MSN Messenger
NOTE: Shut off any personal firewall programs such as BlackIce, ZoneAlarm, etc.
Ports 6891-6900 enable File send, Port 6901 is for voice communications.
Allows Voice, PC to Phone, Messages, and Full File transfer capabilities.
 

TCP   6891 - 6900
TCP   1863
UDP   1863
UDP   5190
UDP   6901
TCP   6901
----------------------------------------------------------------------


Method 1:
ipmasqadm portfw -a -P tcp -L 6891 -R 6891
ipmasqadm portfw -a -P tcp -L 6892 -R 6892
ipmasqadm portfw -a -P tcp -L 6893 -R 6893
ipmasqadm portfw -a -P tcp -L 6894 -R 6894
ipmasqadm portfw -a -P tcp -L 6895 -R 6895
ipmasqadm portfw -a -P tcp -L 6896 -R 6896
ipmasqadm portfw -a -P tcp -L 6897 -R 6897
ipmasqadm portfw -a -P tcp -L 6898 -R 6898
ipmasqadm portfw -a -P tcp -L 6899 -R 6899
ipmasqadm portfw -a -P tcp -L 6900 -R 6900
ipmasqadm portfw -a -P tcp -L 1863 -R 1863
ipmasqadm portfw -a -P udp -L 1863 -R 1863
ipmasqadm portfw -a -P udp -L 5190 -R 5190
ipmasqadm portfw -a -P udp -L 6901 -R 6901
ipmasqadm portfw -a -P tcp -L 6901 -R 6901

Method 2:
Why both the 64.4.12.x and 64.4.13.x networks? They just popped up both with netstat...

ipchains -A output -p tcp -s 1023:65535 --dport 6891 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6891 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6892 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6892 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6893 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6893 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6894 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6894 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6895 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6895 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6896 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6896 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6897 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6897 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6898 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6898 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6899 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6899 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6900 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6900 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 1863 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 1863 -d 1023:65535 -j ACCEPT
ipchains -A output -p udp -s 1023:65535 --dport 1863 -j ACCEPT
ipchains -A input -p udp ! -y -s 64.4.12.0/24 --sport 1863 -d 1023:65535 -j ACCEPT
ipchains -A output -p udp -s 1023:65535 --dport 5190 -j ACCEPT
ipchains -A input -p udp ! -y -s 64.4.12.0/24 --sport 5190 -d 1023:65535 -j ACCEPT
ipchains -A output -p udp -s 1023:65535 --dport 6901 -j ACCEPT
ipchains -A input -p udp ! -y -s 64.4.12.0/24 --sport 6901 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6901 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.12.0/24 --sport 6901 -d 1023:65535 -j ACCEPT

ipchains -A output -p tcp -s 1023:65535 --dport 6891 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6891 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6892 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6892 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6893 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6893 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6894 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6894 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6895 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6895 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6896 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6896 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6897 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6897 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6898 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6898 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6899 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6899 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6900 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6900 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 1863 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 1863 -d 1023:65535 -j ACCEPT
ipchains -A output -p udp -s 1023:65535 --dport 1863 -j ACCEPT
ipchains -A input -p udp ! -y -s 64.4.13.0/24 --sport 1863 -d 1023:65535 -j ACCEPT
ipchains -A output -p udp -s 1023:65535 --dport 5190 -j ACCEPT
ipchains -A input -p udp ! -y -s 64.4.13.0/24 --sport 5190 -d 1023:65535 -j ACCEPT
ipchains -A output -p udp -s 1023:65535 --dport 6901 -j ACCEPT
ipchains -A input -p udp ! -y -s 64.4.13.0/24 --sport 6901 -d 1023:65535 -j ACCEPT
ipchains -A output -p tcp -s 1023:65535 --dport 6901 -j ACCEPT
ipchains -A input -p tcp ! -y -s 64.4.13.0/24 --sport 6901 -d 1023:65535 -j ACCEPT


I thought for sure the second method would work, but alas... it didn't
Could anyone point me (and John) in the right direction on how to get this working?!!??!

Thanks in advance,

Michiel

[Timothée]

Or is there anyone that kind to make us a working e-smith rpm?

[Timothée]

Oops...forgot to mention this link: http://home.tig-grr.com/mmsmasq.tar.gz
Maybe this might help you a little to create a rpm for us

[stephen noble]

i'll make the rpm if some one can patiently explain which files to add/edit
preferably you will already have your system working
and be aware of the security risks if any
i want to open a port for a web based chat

[Jeroen]

Couldn't you just use the portforward rpm (in the contrib area) and forward the ports  to you Win box???

good luck,

Jeroen

[Michiel]

Hi Jeroen,

Did you try that? did it work?

problem with that solution is that you can only use MSN's send and voice features from ONE pc on your internal network and not all of them.
The second message from Timothee points to a C Makefile to get it working automatically for ALL clients, but I've tried making that Makefile but couldn't get it to work and my linux knowledge is not that good.

Thanks for your tip, I'll try it right away...


Greets, Michiel

[PhalSe]

I tried that .rpm and used the directions in the how-to that go along with it but it didn't seem to work for me.

[john vl]

Not for me i can't get it work

[Jeff]

this seems to be a long-standing problem with now solution. I need to be able to open/close ports and can't fine a working method to do so. I dont want to forward them but open them so that each machine on the network can use MSN Messenger, Play internet games, etc. how can I do this ?

[nike]

Jeff wrote:
>
> this seems to be a long-standing problem with now solution. I
> need to be able to open/close ports and can't fine a working
> method to do so. I dont want to forward them but open them so
> that each machine on the network can use MSN Messenger, Play
> internet games, etc. how can I do this ?

Well said Jeff. and I'm dying to get an answer. I want to play any internet game without having to go through the hassle of finding out which ports, forwarding them to this or that machine to find out suddenly the other stuff doesn't work anymore... and since there are 5 comps to play with here I'd like them all to be able to play at the same time...

[nike]

Jeff wrote:
>
> this seems to be a long-standing problem with now solution. I
> need to be able to open/close ports and can't fine a working
> method to do so. I dont want to forward them but open them so
> that each machine on the network can use MSN Messenger, Play
> internet games, etc. how can I do this ?

Well said Jeff. and I'm dying to get an answer. I want to play any internet game without having to go through the hassle of finding out which ports, forwarding them to this or that machine to find out suddenly the other stuff doesn't work anymore... and since there are 5 comps to play with here I'd like them all to be able to play at the same time...