That covered alot, yeah, but that didn't really answer the quesiton I asked - let me clarify:

(Of Course I'm guessing at all this so my apologies if I'm wrong)

When I talk about an person's ISP blocking you, I mean that they've blocked out the publicly established port 6346... meaning you can't make any outgoing or incoming connections on 6346. This would not effect connecting to clients and hosts that know your 'forced IP' which would be some odd port like 27015 (heee heee)... I'm sure even other hosts would eventually catch on via hosts that already know you, and ask for you on that port instead of 6346 so incomings would work fine too.

What I'm saying is regarding that very first connection you make to any host listening on 6346... Its my understanding that since they're listening on 6346 that you can't make a connection to them on anything else, because they're only listening on 6346. Making those first connections would be blocked by your ISP since router.limewire.com:6346 and such all have to be on 6346. So what I'm saying is how would you get on the network that uses 6346 if you use 1000? ... Maybe write down a few servers you know of that use an odd port and connect to them first, so they can spread the word for more incomings for you? Also, if someone is on dial-up wouldn't no other server even consider incoming them?

I would appreciate all the chiming in possible, as a thread like this only promotes learning for all who read it. Thanks for the feedback, unregistered.

Mike

I can't say I really understood the logic of making the default port 6346.

At the time it came out, one of the advantages Gnutella boasted was that you could change the port to whatever you wanted so that it couldn't be blocked simply by the network admin blocking the application port. This was a good idea.

Unfortunately, almost everyone kept the default of 6346. There is no real reason for this, since it works quite well on whatever port you use. Personally, I normally use port 80 whenever I run it, since I WANT my ISP to think I'm only running a web server.

Meridun, you say you connect normally via port 80. How do you establish an initial connection though?
I've been connecting through my work T1 line with no problems, until recently when they must have blocked access to port 6346 (probably after seeing me downloading all day). I get timed out when trying to connect to the routers, and IPs I find from web pages are all on the same port, so I have the same result.
unregistered "If you can web browse, your ISP isn't blocking you, Gnutella will work fine" doesn't make sense, and "gnutellahosts 6346 is too busy" is not the case because I connect at home through netzero in 10 seconds. And "7. This is not rocket science" maybe applies to you since you're probably on the computer 24/7, but for normal users like myself that just want to share it's a @#$% pain in the *** to figure this **** out. So, I'm about to try Mike's lengthy remedy, anyone else have any suggestions or input on this problem that I'm sure many many people are having??

My Reply to this Problem is to tell the deverlopers of the Gnutella-software like limeware that the update hers software with this feature:

Every start of the Gnutella Client, the program must changed automatically the listing incoming port to an another randomized port like 25468 or 80 or each other port until 65536 for instance.

With the same manner must work all Gnutella Clients around the net.

if the hostlist (Gnutella.NET) is update, you can see many hosts with different kinds of Port.

I hope it is manageable.


Sorry about my english. I come from Germany. :-)

Email: chatcafe@firemail.de

got Juno on my system now, and I connected with no problem. I got my searches done, then kept Bearshare up and got back onto my work T1 line. I read Mike's suggestion for forcing an IP, but it's not clear to me where and how to get this to happen. Which IP? I get the picture with two compuers, but it's not clear to me how to do it with one.
Anyone that can help at this point?
>>L