PDA

View Full Version : shareaza behind firewall



victory28
September 9th, 2003, 10:08 PM
does anyone know how to get shareaza to work behind a firewall, even if I have to use http-tunnel, I can't find the option in shareaza to allow me to put in the SOCKS5 server... thanks

aqlo
September 9th, 2003, 10:12 PM
You have to get stuff "pushed" to you by UDP. You can't get it from anyone who is behind another firewall. I'll fetch the setting for you in a minute. If you figure out that Socks thing please post it out here.

OK in the settings under network pick connection. There are some checkboxes, one of them says like "I can accept incoming connections." Turn it off.

You will have to fix the port to be one that is open on the firewall.

KurtCocain
September 10th, 2003, 06:21 AM
Shareaza cant really push the damn firewalls. I have tried everything... Well it all depends how restricted your traffic is from the firewall ... but generally If you set the port 80 in Shareaza and chec the box "..Cant accept incoming connections ..? and does not connect -- forget it . On my coll campus .. the only thing that sneaks around the firewall is Kazaa ..a nd now when its down .. it sucks ... PLus Kazaa does not have the quality files like emule..

victory28
September 10th, 2003, 12:53 PM
Shareaza does not seem to like any of the 4 open ports:
Port 135 Open (epmap)
Port 445 Open (microsoft-ds)
Port 1025 Open (blackjack)
Port 5000 Open (commplex-main)

Kazaa works by using http-tunnel, and I think eMule should work using it as well, but neither of those stand to the quality of the files I get by using shareaza. Im gonna try to get a BitTorrent program working, Im sure other people will want to know how to get around their college as well.

aqlo
September 10th, 2003, 12:57 PM
Yes please anything you learn is gold.
Note than when it does work it is still not as good as it should be.

Dividend
September 10th, 2003, 02:36 PM
Shareaza will work with port 135, but you have to get Windows' deathgrip off of it first. In the administrative tools -> services, disable "Task scheduler" and "Distributed Transaction Coordinator". Then you have to run this tool (link (http://grc.com/dcom/)) and disable DCOM, restart your computer, set port 135 in Shareaza and restart Shareaza. If port 135 were truly open on your firewall, this would now let any P2P program listen on it.

Also, I believe port 5000 can be set free whem you disable UPnP in the service window.

stealthspy
September 11th, 2003, 12:17 PM
Shareaza does not yet support Socks5 Proxys.

Why use a random port? What's really that wrong with 6346 as a standard port?