• RSS
  • Twitter
  • FaceBook

Welcome to ISAserver.org

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Guide: eMule on and behind ISA Server

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [ISA Server 2000 Misc.] >> Gaming >> Guide: eMule on and behind ISA Server Page: [1]
Login
Message << Older Topic   Newer Topic >>
Guide: eMule on and behind ISA Server - 24.Jun.2003 9:48:00 PM   
Khadgar70

 

Posts: 3
Joined: 22.Feb.2003
Status: offline
How to get eMule working on and behind ISA server

This configuration works only WITHOUT using the Firewall Client (I believe this is called SecureNat mode).

It might be possible that some of these rules are not necessary but this configuration works and I havenĂt tried it yet with lesser rules.

I hope this manual will be useful to you.

Still working on the following issues:
- Getting Kazaa (lite) to work on and behind ISA Server. Should be easy but I havenĂt been able to get it working so far.
- Getting C&C Generals to work behind ISA Server !
Can get into the lobby, can use the communicator but after game is started the connection is lost.

Help and or suggestions are welcome, especially for C&C Generals.

Mail me at: lordaeron70@hotmail.com

If your looking for a word document version (include pictures) of this guide you can request it at the same e-mail address.

To get eMule working behind an ISA server:

Ports 4242 and 4661 are used by eMule servers. Sometimes servers use different ports like 8888. For these servers you will have to create additional Inbound and Outbound TCP protocol definitions.

Under ˘Policy Elements, Protocol Definitions÷ you need to create the following protocol definitions:


Inbound TCP:
Description Primairy connection Secundary connections
eMule - 4242 in 4242, TCP, Inbound 4242, TCP, Outbound
eMule - 4661 in 4661, TCP, Inbound 4661, TCP, Outbound
eMule - 4662 in 4662, TCP, Inbound 4662, TCP, Outbound



Outbound TCP:
Description Primairy connection Secundary connections
eMule - 4242 out 4242, TCP, Outbound 4242, TCP, Inbound
eMule - 4661 out 4661, TCP, Outbound 4661, TCP, Inbound
eMule - 4662 out 4662, TCP, Outbound 4662, TCP, Inbound




Inbound UDP:
Description Primairy connection Secundary connections
eMule - 4665 in 4665, UDP, Receive Send 4665, UDP, Send Receive
eMule - 4672 in 4672, UDP, Receive Send 4672, UDP, Send Receive




Outbound UDP:
Description Primairy connection Secundary connections
eMule - 4665 out 4665, UDP, Send Receive 4665, UDP, Receive Send
eMule - 4672 out 4672, UDP, Send Receive 4672, UDP, Receive Send




After these Protocol Definitions are created you have to create a Protocol Rule under ˘Access Policy, Protocol Rules÷.

Name this rule eMule (or whatever you want) and use Selected Protocols.
Select the procotol definitions you have just created.

Under ˘Applies To÷ you can use a Client Address Set.
I use a Client Address Set which contains the IP range for my internal network, e.g. Network, 192.168.0.1-192.168.0.254.


Finally you will need to create a Server Publishing Rule which will enable you to get an High ID in eMule

Go to ˘Publishing, Server Publishing Rules÷ and create a new server publishing rule called eMule 4662.
Under Action, IP address of internal server you fill in the IP address of the computer running eMule. External IP address on ISA Server is your external IP.
Choose ˘eMule ű 4662 in÷ as Mapped server protocol.



If you have more computers on which you want to run eMule then you will have to create additional rules like the 4661 rules, eg 4660 and Server Publishing Rules for these new port(s). Also you will have to change your settings in eMule to this port.

ISA Services should be restarted after these changes or if you want to run eMule on ISA Server itself you can wait till you completed the next section.


To get eMule working on an ISA server itself:

Since port 4662 is already in use for connection to the workstation I will use port 4663 for connection to eMule on the ISA Server itself.

Under ˘Access Policy, IP Packet Filters÷ you need to create the following (custom) protocol definitions:

TCP Outbound:

IP Protocol : TCP
Direction : Outbound
Local Port : All ports
Local Port Number : -
Remote Port : Fixed port
Remote Port Number : 4242



Repeat this step for ports for ports 4661, 4662 and 4663.

TCP Inbound:

IP Protocol : TCP
Direction : Inbound
Local Port : Fixed port
Local Port Number : 4662
Remote Port : All ports
Remote Port Number : -



Repeat this step for ports for port 4663.


UDP Send:

IP Protocol : UDP
Direction : Send only
Local Port : All ports
Local Port Number : -
Remote Port : Fixed port
Remote Port Number : 4665



Repeat this step for ports for port 4762.

UDP Receive:

IP Protocol : UDP
Direction : Receive only
Local Port : Fixed port
Local Port Number : 4762
Remote Port : All ports
Remote Port Number : -




Finally you will need to create a Server Publishing Rule which will enable you to get an High ID in eMule

Go to ˘Publishing, Server Publishing Rules÷ and create a new server publishing rule called eMule 4663.
Under Action, IP address of internal server you fill in the IP address of the computer running eMule. External IP address on ISA Server is your external IP.
Choose ˘eMule ű 4663 in÷ as Mapped server protocol.



ISA Services should be restarted after these changes.
Post #: 1

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [ISA Server 2000 Misc.] >> Gaming >> Guide: eMule on and behind ISA Server Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts