Browse Host from Upload tab
 

I'd rather assume that many of the hosts just aren't browsable - most aren't these days (reason: fear).

I tested with two computers on different networks. The listening port was set for 44444 but after a completed upload I tried to browse back and Phex tried to connect to port 2404.

Clearly from the screen capture above, there is no indicated port in the log. It looks as though Im only getting half of the conversation? There should be an "X-node" or something similar indicating the correct listening port.

That sounds like Phex somehow getting the wrong information.

From Phex to Phex it worked for me, though (got the correct port).

How did you try it?
Are you firewalled?

@Gregor: Can you check it?

Both boxes are firewalled however I was able to browse and download back and forth (both using Phex 3.2). When I select "browse host" of one of the remote hosts in my uploads list, it simply is trying to connect to the port specified for the upload in the handshake rather than identifying the listening port.

I just installed the latest Phex and just happened to have an upload from another Phex user with ver 3.2.6. When I clicked "browse host" for him, the same thing happened. Phex tried to connect to his upload port rather than his listening port. Not sure why this isnt working for me.

When I download from a remote host (using a network data analyzer) Im sending the following info to him. As you can see from the following paste, the "X-Node" entry shows my correct ip address and listening port in the header. Im transmitting the info but when a host downloads from me, Im unable to see his correct port.

GET /uri-res/N2R?urn:sha1:KW2ZKRTFLA4PRABKO6WPCKTH7JRNGTTV HTTP/1.1
User-Agent: Phex 3.2.6.106
Host: 192.168.24.71:2998
Range: bytes=196608-212991
X-Queue: 0.1
Connection: Keep-Alive
X-Node: xx.xx.141.176:64000
Chat: xx.xx.141.176:64000



HTTP/1.1 206 Partial Content
Server: LimeWire/4.12.15 (Cabos/0.7.9)
Content-Type: application/binary
Content-Length: 16384
Date: Wed, 15 Oct 2008 19:39:05 GMT
Content-Disposition: attachment; filename="KarakuriCircus18_004.jpg"
Content-Range: bytes 196608-212991/490546
X-Gnutella-Content-URN: urn:sha1:KW2ZKRTFLA4PRABKO6WPCKTH7JRNGTTV
X-Push-Proxy: 98.19.156.18:50759
X-Create-Time: 1061272810000
X-Features: fwalt/0.1, fwt/1.0, browse/1.0
X-Thex-URI: /uri-res/N2X?urn:sha1:KW2ZKRTFLA4PRABKO6WPCKTH7JRNGTTV;VVJB 64FVS2VG6C7AJJSJVQWYYX5HJ4EPUCI6UJY

Im not sure that anyone cares about this thread and Ill try not to beat this issue to death...

I tried "browse host" on the uploads tab with remote hosts using several versions of LW, Phex, Shareaza, Frostwire, and Gift.

The only time browse host worked on the listening port is when the line "X-Node" appears in the header. In my case it only worked for a 4.12 and 4.14 version of LW. I included screen captures for several versions of LW to compare. If it didnt say "X-Node", the browse would try the wrong port and would fail.

I care about this problem, but I can't fix it myself.

I'm not sure if Gregor can (might be misbehaviour of other clients), but I assume it can be fixed at least for inter-Phex uploads.

Many thanks for gathering such exhaustive information about it!

I guess this is one of the most changed headers I remember... Phex checks all these header to find the listening port:
X-Node, X-Listen-IP, Listen-IP, X-My-Address

Over the years every one or the other client used one of the headers, and they were changed multiple times forth and back. To my knowledge the last officially specified header to use is X-Node. But I could be wrong.

Apparently Limewire again changed the header and kept it as always as there personal secret. I assume the new header Limewire is using is X-FW-Node-Info, the new format is of course not specified anywhere else then in the source....
I guess the header change was done to support push proxy, which would help to make browse more reliable. But it won't help if only Limewire knows how it works...

Should we just ask in the_gdf and see if they reply with useful info?