mp4um x+
SocksCap v2.1   

by   Networking Systems Laboratory, NEC USA, Inc

Screenshote :   1   2   3   4


SocksCap automatically enables 32-bit Windows-based TCP and UDP WinSock
client applications to traverse a SOCKS firewall.  SocksCap intercepts
the networking calls from a client application and redirects them through
the SOCKS server without any modification to the original application or
to the operating system software or drivers.

SocksCap centralizes SOCKS client configuration, eliminating the need
to individually configure each network application�s firewall or proxy
setup.  SocksCap can be configured to connect directly to some addresses
(for example an Intranet) while redirecting all other connections through
the SOCKS server.  Direct connections based on application name can
also be configured.


Requirements
==========
- A PC running Windows 95, Windows 98, Windows NT 4.0, or Windows 2000

- Properly configured TCP/IP network settings

- A functioning SOCKS server

The e-Border(tm) Server (includes a fully SOCKS-complient server) 
is available from   http://www.eBorder.nec.com/

- Properly configured DNS. For SOCKS version 4, the PC must query
a DNS server that can resolve all inside and outside names. 
SOCKS version 5 supports remote name resolution.

- TCP/IP networking applications. SOCKS version 4 only supports TCP.
SOCKS version 5 supports TCP and UDP applications.


Possible Problems
=============
SocksCap is easy to use and works well with most applications.
But, there are some important issues to note.

- You can only use one method of socksification at a time. You should
not use SocksCap with other SOCKS-enabled stacks or applications.
For example, if you plan to use Netscape through SocksCap, be
certain Netscape's SOCKS capabilities are disabled.

- Since SocksCap is a generic solution that is unaware of the stack
and application that it runs between, it may not work with some
combinations of applications and stacks.

- SocksCap supports UDP traffic as specified RFC1928 -- SOCKS Version
5 Protocol.  The RFC has some known limitations for use with UDP
streaming applications.  Due to those limitations, not all
applications' UDP implementation can be proxied through SOCKS.

- Use SocksCap's logging facility to help debug connection and
application startup issues.


Hosted by www.Geocities.ws

1