Well, I doubt you'll get a passive result after leaving the hub....
Aww.... I really don't want to go checking the code or protocol right now so I might be just talking BS, but here goes anyway...
If hub has multiple IPs or ports, the SRs coming in will contain the IP:port where that user has connected to. If local client is connected to another address/port, like private IP of the hub, (it's the same hub still) obviously the IP:port won't be found by ClientManager. (Can you even download those results, if the client doesn't know the hub?)
If I'm correct, this really isn't fixable. At best the default hub encoding could be used instead systemCharset, but that was GUI only?
Well, I doubt you'll get a passive result after leaving the hub....
Aww.... I really don't want to go checking the code or protocol right now so I might be just talking BS, but here goes anyway...
If hub has multiple IPs or ports, the SRs coming in will contain the IP:port where that user has connected to. If local client is connected to another address/port, like private IP of the hub, (it's the same hub still) obviously the IP:port won't be found by ClientManager. (Can you even download those results, if the client doesn't know the hub?)
If I'm correct, this really isn't fixable. At best the default hub encoding could be used instead systemCharset, but that was GUI only?
--RZ