The simplest (most likely) and the surest way... at least for Windows-based clients.
It looks like even some of the experienced ones in this forum are confused a bit. You need to implement FIREWALL CLIENT. There are many other applications/games that work only under Firewall Client anyway.
"... Firewall Client: This client is the most capable of all, because it has the unique ability to decide on a "per-application" basis how it will act and what information the application has to operate with. Additionally, it is the only client that is able to use secondary protocols. It's the need for secondary protocols that make the FWC necessary for apps like Instant Messaging, streaming media, FTP, etc.... " - From Tutorials ISA Clients Part 3: The Firewall Client -
Under Client Configuration > Firewall Client, Properties > Application Settings
Application: emule (name of the actual executable file without ".exe")
Key: ServerBindTcpPorts -- Value: 4662,4711 (4711 is optional for Web Control Panel)
Key: NameResolutionForLocalHost -- Value: E
* Some people say it should be P, but P means the internal IP address of ISA server. (L = IP addr of client computer, E = external IP addr of ISA server) This is to TELL the P2P network the IP address of your eMule client inside the LAN, which should be your INTERNET IP address.
Key: KillOldSession -- Value: 1 (optional)
Key: LocalBindUdpPorts -- DOES NOT WORK! So, don't bother. Instead...
Under Protocol Definitions, create a new definition
Name: eMule (UDP) <-- up to you
Port #: 4672
Protocol Type: UDP
Secondary connections: 4672, UDP, Receive Send
You don't need to configure [you can't anyway] the Server Publishing Rules since the outbound connection will open the incoming connection. This is similar to Port Triggering of commercial routers like Linksys. Just let the client use the new protocol definition under Protocol Rules. [no need to add a new one if 'all IP traffic' is allowed]
Enable Kad network. The server status will now say 'Open' instead of 'Firewalled'. ['High ID' for eD2k]
- UPDATE Firewall Client on the local computer hosting eMule and RESTART the application once you make changes to Application Settings. Clicking 'Disconnect' and 'Connect' will NOT make it work!
- RESTART the Firewall service on ISA server, update Firewall Client, and restart the application once you make changes to others (protocol definitions, rules, etc.).
* You can apply this method to other P2P apps like Overnet, WinMX, etc. simply by substituting the port numbers.
PS: Since the above method does not specify any client IP address, you can "supposedly" run the same application on multiple computers in your LAN without changing the port numbers. I was not able to test it (I only have two computers at home), so let me know if anybody succeeds, please.
[ August 09, 2004, 04:04 PM: Message edited by: coldsweat ]