I am running MS ISA server for a firewall to my network. It is set to allow all incoming IP traffic basec on an internal request. I tried the "Force IP" option, but it did not help. Please advise.

Same here- no go

I have the same problem, someone has answered you?
I answer your message to see if it is put on the forum.

I personally don't used MS-ISA Server but the reason your gnutella software does work with it is pretty simple based on what I understand about proxy-servers in general.

Essentially you are attempting to proxy an application that makes requests for the the clients initiating the connection.

Client ==>Proxy ==> Internet

Your email and Web browsers can be configured to point to the proxy server and they will work correctly.

However Gnutella Application makes a request on the wire and is not heard or picked up by the proxy. (Remember the proxy server is listening on a specific port for request.)

If you tried to point your gnutella client to the proxy server in hopes that the proxy server would forward the request I'm relatively confident that this didn't work at least not correctly.

In ISA server you have the ability to create a firewall client. (I recommend that you read the documentation on how to do this)

You need to install this client on each machine running the gnutella application. I am assuming that you guys are not trying to run Limewire from the ISA server itself.

You will have to create the firewall client at the ISA server console so I am assuming that you have access to the ISA server.

Once you have sucessfully created /configured and installed the ISA firewall client on all of the machine you should be able to use limewire without issue.

Essentially the firewall client will funnel all of the traffic leaving the machine through the proxy server.

LocalMachineTx >Firewall_client ==>ISA-Server-Component==>Internet.

Again I don't know the specific details but this should solve your problem.

Hope this helps.

http://www.leeware.com

You need to start by creating 2 "Protocal Definitions" (YOURISASERVER/Policy Elements/Protocal Definitions)

Name
1. LimeWire-In
2. LimeWire-Out

Both use: port: 6346 & protocal: TCP
Set directions IN & OUT respectivly.

Now allow both "Protocal Definitions" in "Protocol Rules" (YOURISASERVER/Access Policy/Protocal Rules).

Restart Limewire and away you go

Attached Thumbnails

 

Open your port 6346 for UDP, too. The next versions are going to make use of it.

Next versions???.... Could that possibly mean the appreciated arrival of 2.8?

It would be nice to move on past these ever escalating version numbers of 2.7!

The first beta 2.8 is going to be released this week (according to Adam Fisk). It enables server-side UDP but does not actively make use of it yet.

Good to hear!

Cheers for the UDP note for the future

Andy