Here is a description of all the files required for my sample configuration: NAMED.BOOT - Domain nameserver boot description file. Should be placed in the ETC\NAMEDB directory, which will need to be created. Required for BIND. NAMED.BT - Identical to NAMED.BOOT, but used by DNS Kit for TCP/IP on FAT systems. Must be placed in ETC\NAMEDB. NAMED.CA - Domain nameserver caching server definition file. Must be placed in ETC\NAMEDB. Used by both DNS Kit and BIND. NAMED.DOM - Domain nameserver domain name definition file. Must be placed in ETC\NAMEDB. Used by both DNS Kit and BIND. SOCKD.CFG - Permissions file for SOCKS server. Must be placed in ETC directory. Used by SOCKD. SOCKS.CFG - Warp 4 SOCKS client configuration file. Must be placed in ETC directory. Used by the TCP/IP in Warp 4 on client machines, to talk to the SOCKS server. SOCKS.ENV - Warp 4 SOCKS client environment file. Must be placed in ETC directory. Used by the TCP/IP in Warp 4 on client machines, to talk to the SOCKS server. RESOLV.LO - TCP/IP name server definition file for the SOCKS server. This indicates where the server should request TCP/IP domain names it receives from SOCKS clients. Must be placed in ETC directory. STARTSOK.CMD - REXX script that is run to "start" the SOCKS server. Must be edited to reflect the local setup, but can be placed anywhere. This script should be called by your dialer after an internet connection is established. HOSTS - This file is a HOSTS definition file that should be used when no DNS server is in use to resolve names for the private domain, such as when DNSPROXY is used instead of DNS Kit or BIND. This file should be placed in the ETC directory on all client machines and on the SOCKS server machine.