Shareaza

According to the site and stuff, Shareaza uses port 6346. But according to my firewall (Comodo), it uses a hell of a lot more ports than that. Dozens in the 53xxx range. Is something wrong? I downloaded the software from Sourceforge, where I linked to this very forum. In fact, according to my firewall, port 6346 isn't even receiving traffic, it is just listening. Someone care to explain?

I set up my firewall and router to forward port 6346. But Shareaza keeps saying that my connection is limited (the home page) I tried the connection test and it fails. I am positive I forwarded my ports correctly. Do I need to forward and configure my firewall for other ports to pass the connection test?

Did you have turned off "Random" Port and "Use automatic UPnP settings" in the Shareaza Settings>Traffic>Network dialog?

BTW: Its recommend to not to use port 6346 since the most ISP's are throttling it.
Use a port between 49152-65535 for Shareaza.

I'll change ports. But still, Shareaza uses way more ports than just one. Also, I can't find Shareaza Setting > Traffic> etc. But, "Random" is not checked, and "Use UPnP Connection Device Setup" is not checked, if that's what you mean. Also, should I use a "Host" or "Dynamic" service when forwarding the ports?

Shareaza will open port 6346 (default) or whatever you specify as a listen port. This is where it will receive Gnutella file requests and perhaps other traffic such as incoming search results after you perform a search.

When it makes Gnutella download connections, it will open high-numbered ports. It may also make peer connections up there, and BitTorrent and ED2K connections.

The listen port is the only one that has to be forwarded correctly in your router, but both TCP and UDP must be forwarded. Your software firewall should be instructed to let all Shareaza traffic pass unobstructed.

Okay, gotcha. Thanks. I'm still having trouble with the connection. It is saying it is limited. But I have forwarded both TCP and UDP from my router. And my software firewall is set to fully allow the application. I disabled my software firewall to test, and the test failed, so that's not the problem. It's something with my router. But like I said, both TCP and UDP are forwarded for my listen port. It may be because it's a dynamic service. I'll change it to host and see of that helps. If not, what could be the problem?

See this wiki page for more information on how to configure your router and test connectivity.

Are you forwarding the port to the correct local IP address? For example, my router has local IP 192.168.1.1 and my machines, 192.168.1.100 and 192.168.1.101. The router has a network-facing IP in the 74.xxx.xxx.xxx range. My Shareaza port is forwarded to 192.168.1.100, since that's the local IP of the machine that I run Shareaza on.

Yes, my local IP is 192.168.*.**. That's what my port is forwarded to. And I've read all the firewall/router configuration stuff. Done all that. I"m still failing the connection test and Shareaza is saying my connection is limited. I can download stuff though. I'm downloading a large torrent right now, but the speed is nowhere near my max connection speed. Could be the torrent and sources, or could be my limited connection.

Yes. That page doesn't help me because the router I use runs different firmware. It doesn't matter though because I'm sure I forwarded the ports correctly. I've tried a host and a dynamic service. I've disabled both software and hardware firewalls. I've changed to a static IP. I've changed the default port Shareaza uses. Nothing allows me to pass that connection test. Should I set up a port trigger? The only thing I can think of is that Shareaza needs more ports forwarded than just the one. If so, which ports. Should I try a DMZ host configuration?

It doesn't, or at least the connection test doesn't. Only one port is tested. The other ports used are TCP connections started from your end and they work automatically. If they didn't your web browser and email would not work.

What firmware do you use?

I've tried port triggering, and port triggering and port forwarding at the same time. No go.

Well I guess there's nothing I can do. It's something with my gateway. I'll see what switching back to the old gateway does. As soon as I get it back.

Enter the web-based setup for the Versalink, Configuration, Services, and checkmark the box to enable uPnP.
Than enable uPnP in Shareaza and sing " Alleluia !"

Nope. That didn't work.