I followed ur guide exactly but still getting low ids in emule. emule is using the standart ports and ive got no clue, where the mistake is. emule is running on a client in the domain. only the isa2k4 firewall is running. anyone has an idea?
On the client computer everything runs fine. outlook, messenger, internet explorer, ftp everything runs without errors. but i alway get the low id stuff in emule....
I am not 100% sure, but i think the configuration will work if you install FW client on the server and do all the configuration specified in the tutorial.
Re: mt247
It is good to here you got it working.
I have used this config for about 1 month myself and it working great, no problems no errors!
1. May I ask why should we choose anywhere in network settings? 2. Does it open security holes if we go wild like this? 3. Why just not create the rule and source will be local host and destination external client? Thank you
There is probably more secure and easier ways to config the use of Emule with ISA 2004, my goal was to get it working and get high ID.
If you you want a maximum secure server you will never give permission to access p2p network in the first place.
why should we choose anywhere in network settings?
You don't need to choose anywhere, if you wan't you can specify the the servers that you want to connect to.
Does it open security holes if we go wild like this? yes
You specify the port range that will be open, and it is up to you how wide that range will be, normally the donkey servers are within the port range of 4000-5000.
Why just not create the rule and source will be local host and destination external client?
It sounds easy, try and when you get it working post it here.
When I perform a port check from within Emule the site reports everything is OK, but in the emule gui when I try to connect to some server it reports: "fatal error while trying to connect. internet connection might be down"
There is absolutely not a secure way to get high id on emule. I tell you why. Any file sharing program including emule has a set of standard ports to use. As an example emule uses 4662 tcp and 4672 udp, but the problem comes when everybody in world start using a non standard port to run the application so we have no f* clue which ports to go get the chunk back. Run net stat in command line when you use emule and see that it opens whole amount of ports of machine( due to stay in queue ) and also is trying all different kind of ports out there since everybody has different settings. You canĘt have a secure access way like web access because http has a standard rule, tcp(80) and ftp(21) Think of a simple home router and why it allows access for emule. It allows any port from local to any port to outside. In that case you have to create a new rule which allows any access from any port inside to any host on internet on any running port. To make it safe that it is not being overwritten by other rules, you have to keep it in top and basically then what is the access control you have? Every body goes everywhere Unless you only create the rule for a specified machine and only allow incoming access for that machine to get high id, (which is absolutely a crazy idea in network) you are out of luck I have tested this on dmz so if something goes wrong then has less damage.
Again and again, the point is if you want to run emule under isa, then you are running it in business environment. Have you thought of possible legal problems? Use it at home with no problem
RE: Emule Configuration ISA 2004 - 17.Nov.2004 6:04:00 PM
Guest
Personnaly, I use Isa Server 2004 as a firewall in my house and another server as an eMule client.
I read the tutorial /EmuleIsa2004STDConfig.doc proposed at the beginng of that talk.
I think something is missing to get High ID... I'll try to explain :
When your eMule client connect to a server it contacts the server on the port that appear in the server list (usually 4661). Then the server connects a new TCP session back to your emule client to check if your client is well responding and if yes it give you a high ID, if no you have a low ID.
The emule server tries to open this TCP session on your TCP port you configured in emule client (usually 4662).
As it is a new TCP session coming from the emule server the firewall don't associate it as a part of the session you open on the server on port 4661. The firewall think it is an incoming connection and it is right, it's an incoming connection.
To have it work successfully you have to add a "server publish rule" on your ISA server and configure it to listen on port 4662 (the same TCP port than you configured on the emule client) and to transmit all incoming demands to the IP address of your emule client workstation.
I hope these explainations are easy to read. My english is poor... if you need more explainations about my ISA configuration you can mail at Alertes.ISA@pacimail.no-ip.info
RE: Emule Configuration ISA 2004 - 16.Dec.2004 12:35:00 AM
Guest
Hi people,
I installed ISA 2004 on windows 2003 server, I have emule on a client connected by LAN, I followed the guide of Hegris, but my emule still have the low id, so I tryed the tips of Bruno, about to add a server publish rule and now I have High id !Now I still have to configure the Kad server, anyone know how to add it to isa?
I'm using emule behind isa for a long time, so I also share my experience. My variant (slightly differs from Hegris'):
1. Create 4 protocols: a) TCP outbound (ports 4000-5000) b) TCP inbound (ports 4000-5000) c) UDP send receive (ports 4000-5000) d) UDP receive send (ports 4000-5000) You may choose different ports. You need more than 4661 and 4662 if many users want to use emule behind your isa server. Every one of them should use different port.
2. Create access rule action: allow protocols: all created at step 1. from: internal network to: external network users: users that allowed to use emule
3. firewall client parameters you just need to add 2 lines: a) app: emule key: ServerBindTcpPorts value: 4000-5000 b) app: emule key: RemoteBindUdpPorts value: 4000-5000
4. Client setup: a) Firewall client should be enabled b) setup emule connection settings to use unique tcp and udp ports in range 4000-5000 (unique in your local network)
That's all. Now you get HighId and full functionality of emule.
The same steps suits for isa 2000 (with minor differences).
Hi, Where/how do i edit these 2 line in firewall client? John.
quote:Originally posted by JesseA: I'm using emule behind isa for a long time, so I also share my experience. My variant (slightly differs from Hegris'):
1. Create 4 protocols: a) TCP outbound (ports 4000-5000) b) TCP inbound (ports 4000-5000) c) UDP send receive (ports 4000-5000) d) UDP receive send (ports 4000-5000) You may choose different ports. You need more than 4661 and 4662 if many users want to use emule behind your isa server. Every one of them should use different port.
2. Create access rule action: allow protocols: all created at step 1. from: internal network to: external network users: users that allowed to use emule
3. firewall client parameters you just need to add 2 lines: a) app: emule key: ServerBindTcpPorts value: 4000-5000 b) app: emule key: RemoteBindUdpPorts value: 4000-5000
4. Client setup: a) Firewall client should be enabled b) setup emule connection settings to use unique tcp and udp ports in range 4000-5000 (unique in your local network)
That's all. Now you get HighId and full functionality of emule.
The same steps suits for isa 2000 (with minor differences).
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA Server 2004 Misc.] >> Gaming >> Emule Configuration ISA 2004 
Emule Configuration ISA 2004 - 
![[Smile]](/image/smiles/smile.gif)
![[Confused]](/image/smiles/confused.gif)
![[Wink]](/image/smiles/wink.gif)
RE: Emule Configuration ISA 2004 - ![[Big Grin]](/image/smiles/biggrin.gif)
RE: Emule Configuration ISA 2004 - ![[Razz]](/image/smiles/tongue.gif)
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