0 Members and 1 Guest are viewing this topic.
What im suggesting is killing the HTTPtunnelClient.exe and just using the socks4 address from their website in the winmx settings.or if the HTTPtunnelClient.exe has a section to remove programs from the tunnel then remove winmx from it.
Theres not much way to tell if the person on that forum who tried to help you use winmx without even googling it is employed by the tunnel website or not.
It is appearent you need to continue to study on what a proxy is because you seem to be confused on how your own set up works.
Using socks5 through an http-tunnel proxy is overkill.its surprising you ever connect at all with the networks timeout setting.The main difference between socks4 and 5 is all dns queries go through the proxy with 5 this is why winmx benefits from using socks4
Actually, I'm just trying to find the cause of this mysterious problem that suddenly occurred, i.e. if this is related to the HTTP-tunnel servers (which I primarily suspect based on what I see in log files and other behaviours) or not.....