SocksCap is an application wrapper developed by NEC. SocksCap allows Windows users to enable their Winsock applications to traverse a SOCKS server. SocksCap does not require modifications to the Winsock applications or the Winsock stacks. However, due to the multitude of available Winsock stacks, SocksCap may not work in every situation. On a SOCKS-enabled firewall, SocksCap offers a client-only solution.
Using SocksCap with Proxies-R-Us proxies
This guide is designed to help you set up SocksCap with a Proxies-R-Us proxy. If using this guide to setup D2 to run over an open/public proxy, ignore the parts about user authentication. Remember that using open proxies could allow the owner of the proxy to steal both your cd key and account information, so be sure you trust the source of your proxies.
1. Run SocksCap and goto the settings menu:
2. In the settings dialog, make sure your settings match the image below. Replace the "SOCKS Server" entry with the IP or hostname of your proxy, and set the port to the port of your proxy if it isn't 4000. Note that the direct UDP port should always be 4000 even if your proxy port isn't.
3. When you press OK, you should get asked for a username and password. Enter your username (usually proxy) and password into this dialog.
4. Press 'New' from the toolbar to create a new application profile. This is where you choose the program that will run through the proxy. Browse to the program you want to use and enter any extra command line options you need. If you want to run Diablo II through the proxy, you can simply copy and paste the 'Target' from one of your Diablo II shortcuts into the 'Command Line' box.
5. Press 'Run' to run the selected application profile through the proxy!
Using SocksCap with Proxy Servers
SocksCap allows Windows 95/98/NT users to enable their Winsock applications to traverse a SOCKS server. SocksCap does not require modifications to the Winsock applications or the Winsock stacks. On a SOCKS enabled firewall SocksCap offers a client-only solution.
SocksCap allows Windows users to enable their Winsock applications to traverse a SOCKS server. SocksCap does not require modifications to the Winsock applications or the Winsock stacks. However, due to the multitude of available Winsock stacks, SocksCap may not work in every situation.
How Does SocksCap Work?
1. SocksCap is a Microsoft Windows DLL that extends the functionality of the Windows Socket (Winsock) stack, allowing it to work successfully in the SOCKS5 environment. SocksCap intercepts calls from Winsock applications to the Windows Socket (Winsock) stack and converts them to calls that support SOCKS protocols.
2. SocksCap resides between non-SOCKSified Winsock applications and a non-SOCKSified Winsock stack. It converts socket calls to communicate through a SOCKS V4 or SOCKSv5 server. You can configure SocksCap to connect directly (not through the SOCKS server) to some addresses and to use proxy connections (through the SOCKS server) to all others.
Who Can Use SocksCap?
1. Users behind corporate proxy firewalls that are SOCKS-capable.
2. Users running SOCKS servers or SOCKS daemons that serve as firewalls.
In Windows Vista (or Windows 7) If sockscap loads WoW with no ping change. If you are Not Disconnected it means you were not connected via the server. You will need to go to your Sockscap install directory (e.g. C:\Program Files\SocksCapV2.) Right Click on your sc32 or sc32.exe. Then click PROPERTIES then under the COMPATIBILITY tab at the bottom, TICK "Run this Program as an Administrator" then click APPLY. If you cannot tick the box (greyed Out) your User Access Control may be turned off (UAC can be turned On in Your user accounts area.) After that reopen the putty session and Sockscap as normal and reconnect.
The license of this software is Freeware, you can free download and free use this proxy software.