|05 Nov 2010||#1|
| || |
Use of SOCKS5
I am wondering if anyone can suggest why, and it appears to only happen on Windows 7 x64 machines, all of a sudden a SOCKS based solution stops working.
Specifically it is Sockscap32, but my question focuses on the use of a particular port addressing for the Socks Server.
When it is addressed to 127.0.0.1, (IPv4 on, IPv6 off) port: 21552 it fails to function properly.
When it is addressed to 127.0.0.1 port: 1080 it functions correctly.
With no 3rd party firewall or AV in play, can any suggest what settings (perhaps at install or on firewall setting level) would result in port 21552 being blocked as a default.
Changing the port number fixes the issue, but it is specific to Windows 7 x64.
I would appreciate any suggestions. I am really looking for something that is part of a policy that might exclude high port ranges and make it difficult to unlock. As this is also a SOCKS proxy, I am unsure as to what elements of windows security might be at play.
|My System Specs|
|Similar help and support threads for2: Use of SOCKS5|
|Is there any browser can support Socks5 proxy with authentication?||Browsers & Mail|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 12:01 AM.