I was successfully connected to Phex 3.2.0.102, and STUPID ME decided to update to Phex 3.4.0.110. WRONG!!!!! 3.2 was working beautifully, NOW 3.4 will not connect. I have tried everything. Why in the Hell, does this happen? Limewire, Frostwire, Cabos all work excellent.

It maybe something simple like re allowing it access through your firewall.

__________________
If it ain't broke, fix it till it is!

Phex - Reviews and free Phex downloads at Download.com this is the site to install Phex 3.2.0.102. This is the only way I could get a connection in Vista Premium. EVERY TIME I update Phex to a newer version, I have a problem, no more for me until Doomsday. IF you have Phex 3.4.0.110 installed, don't uninstall it, it messes up the 3.2.0.102 version. What a mess!!!!!!!!

Thread merged to avoid confusion

All older Phex versions are available from here:
SourceForge.net: Phex - P2P Gnutella filesharing program: Files

I will look into this problem, not sure why there are bootstrapping problems. Usually it should be enough to find one working host and you should be fine.

If anyone like to experiment with a daily build, you can contact me via PM.

__________________

I have tried the following that GregorK emailed me:

http://phex.sourceforge.net/snapshot..._3.4.0.114.exe

and it works!

(although it is not an official release so it may contain other bugs)

-Raffy

Thanks for helping me, I appreciate it one million times. >>> Ronn

I too am having trouble connecting. Handshakes time out. Firewall adjusted for access and server rights. Tried the variant above and still no go

Please update to Phex 3.4.2

__________________

The default Phex GWC is old, if possible, the developers should either replace it or remove it. The GWC should probably just be upgraded to a different GWC software.

Anyways, I wrote my own GWC code that handles much better and is written in PHP 5. Beacon Cache II ( SourceForge.net: Beacon Cache ( Multi-Network Web Cache ): Beacon Cache ( Multi-Network Web Cache ) ) should be used instead of the much outdated GWCs. Don't worry, beacon cache handles spec 1 and spec 2 requests and updates, so nothing needs to change in request handling.

Beacon Cache II has options to weed out updates from banned IP addresses, block 'fake' GnucDNA clients, block Vendor Codes, and block User Agents, as well as operate between flat-file and MySQL.

Example (And working) Beacon Cache II GWCs Running:

Beacon Cache II 0.2.3.1
Beacon Cache II 0.2.3.1
Beacon Cache II 0.2.3.1
Beacon Cache II 0.1.19.1
http://gwc.dyndns.info:28960/gwc.php

hmm
Also, another thing: The bishopston.net UHCs are blocked by peerguardian for some reason, so someobdy should look into that too.