Basically, if you have multiple pop3 email boxes in different servers, you should specify the user id as login_id#remote_server. For example, if your login id is john and the remote pop3 server is mail.my_isp_server.net, your user id will be john#mail.my_isp_server.net. You should always have a default pop3 and smtp server in the Email Daemon Advanced Configuration window. For receiving mails in other pop3 servers, you can follow the above instructions to set up each mail box in the client email software. For sending mails, you will always use the default smtp server no matter how you set up your user id. The client email software should have the gateway's ip (i.g. 192.168.0.1) in its pop3/smtp mail server(host) field. You can find one example for the Eudora mail in the support page.
ComSocks v2.6 is a real DNS server for your local LAN. In order to improve the DNS resolving speed for the local hosts, please create or edit the HOSTS file in your gateway's Windows directory (there might be an example HOSTS.SAM). Add all local computers there. Here is an example:
Gatway's Hosts file in Windows directory: ---------------------------------------------- # This file contains the mappings # of IP addresses to host names. Each # entry should be kept on an # individual line. The IP address should # be placed in the first column followed # by the corresponding host name. # The IP address and the host name should # be separated by at least one # space. # # Additionally, comments (such as these) # may be inserted on individual # lines or following the machine name # denoted by a '#' symbol. # # For example: # #102.54.94.97 rhino.acme.com # source server #38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost 192.168.0.1 gate1 gate1.mycompany.com 192.168.0.2 baby2 192.168.0.3 baby3 192.168.0.4 baby4 192.168.0.5 baby5
From your client IE's menu bar, clickView->Internet Options. In the Internet Property window, click Connection Tab, check mark "Access Internet using a proxy server" AND uncheck"Bypass proxy server for local (Intranet) address". You may want to click Advanced button to verify your proxy settings. Please compare them to the setup question.
Normally, you need to have two NIC (Network Interface Card) in your gateway computer, one is for the cable modem, another for local network. It may be possible to use only one NIC if your ISP assigns more IP addresses for your local network.
Yes, we do. Enable the SOCKS daemon in ComSocks and configure ICQ to use SOCKS 5 and set the proxy host IP to the gateway's IP. Please refer to ICQ firewall support for more details. We DO support FTP from any client computer. When you ftp to Internet from your client computer, you ftp to the gateway first, ComSocks will prompt you to enter your user id, at that time, enter "remote_user_id@remote_host_name". You can configure WS-FTP client program to use proxy by enabling Firewall setting under Firewall Tab(put gateway's IP in the Host Name, ignore UserID and Password, select USER with no logon).
- You only need to run ComSocks in your main gateway computer.
- You should have no problem to access Internet from your gateway computer by its own.
- Ping your every computer from each other. If it doesn't work, it is a TCP/IP network setup problem. Make sure you only have TCP/IP in your Network property and remove any NetBEUI or IPX/SPX protocol binding. Make sure your subnet mask is 255.255.255.0 and every computer has a unique IP address in your local network(something like 192.168.0.x). Gateway may have multiple IP addresses, because it connects to multiple networks. You can run "winipcfg" to inspect the network setting from Windows 95/98.
- Ping an Internet IP (ig. www.yahoo.com) from your client computer. If you see the alpha IP is translated to a numeric IP (ig. 204.71.177.71) before you see "Request timed out", the DNS works in ComSocks. For client computers, always use your main computer's IP (running ComSocks) as its Gateway and DNS server. You can run winipcfg to verify it.
- In the proxy configuration in your client web browser, make sure you have seen the
following setting:
type Address of proxy to use Port HTTP: [your gateway ip] : 80 Secure: [your gateway ip] : 80 FTP: [your gateway ip] : 80 Gopher: [empty] : 0 Socks: [your gateway ip] : 1080
- Last resort is filling out our question form. Since we have a high volume of emails and questions every day, please select an appropriate priority for your question and attach the result of running "winipcfg" command.
You need to disable HTTP Daemon in ComSocks in the Daemon Tab. Add a new Port Mapping entry in the Port Mapping Tab. Here the proxy port 80 is the port which your client's browser will connect to and the dest port 80 is your isp's proxy port. After you have done this, you won't be able to do the remote dial control from any client. The Dial On Demand won't work for your browser. To work around this problem, you will use an email software to check your email in order to dial up your isp. BTW, if you are using our new v3.0 NAT, please ignore the above configuration. And set your browser on workstations (clients) to the same way as on the gateway, probably you need to set your browser's proxy settings for your ISP.
If you are running Windows 95, you need to download Microsoft latest WinSock 2 library from its web site. But you shouldn't install it on Windows 98 or Windows NT 4.0. If you are running Windows 95 with version earlier than OSR2 (OEM Service Release 2 version 4.00.950B ), you may also want to update Kernel 32 library from Microsoft. If you are running Windows NT 4.0, you need to update to the latest standard Service Pack 4 (Sp4i386.exe). Please don't use the Auto-Install because it may not update your kernel32.dll file. If you want to know more information regarding Microsoft Windows update, please visit Microsoft download site .
Enter your ISP's domain name without WWW in the front (ig. ISP.NET) into the following box or go to www.internic.net. Your DNS IP will be shown at the bottom. You may try to use a DOS command "winipcfg" in Windows 95/98 to display your default DNS IP.
If Webcam32 is executed on a machine which is LAN connected to the machine running ComSocks proxy server, the Webcam32 FTP upload mechanism must be altered to pass through ComSocks.
This is achieved very simply. To configure Webcam32 for ComSocks, you must first know the following information:
| IP address or hostname of the machine running ComSocks |
| FTP target server name or IP address |
| Userid on the target FTP server under which the Webcam32 image will be uploaded |
| Password for the target FTP server userid |
In the Webcam32 settings, enter the following:
For FTP Server, enter the IP address or hostname of the machine running ComSocks
For FTP Userid, enter <FTP Userid>@<FTP Server>
For FTP Password, enter the FTP password.
For example,
If ComSocks is running on a machine called Superman which is LAN connected to a machine called Boy and Webcam32 is running on Boy then if the FTP server were ftp.myserver.com and the userid was myuserid, then
FTP Server would be entered as Superman
FTP Userid would be entered as myuserid@ftp.myserver.com
FTP Password would be entered as the myuserid password
For more information on Webcam32 configuration, visit the Webcam32 home page
In ComSocks, add a new port mapping as follows:
| Port Mapping's Name | BattleNet Port Mapping |
| Proxy IP Address: Proxy Port | Gateway's IP:6112, i.g. 192.168.0.1:6112 |
| Destination Name | client' IP, i.g. 192.168.0.2 |
| Destination Port | 6112 |
| Sender's port and send port | 0 |
| Transport | udp |
| Bi-directional UDP mapping | Yes |
Enable this port mapping and apply the changes. In client computer running the game,
install SocksCap32 from http://www.socks.nec.com/sockscap.html.
Under the file menu, select setup using the following settings:
| SOCKS Server: [gateway's IP, i.g. 192.168.0.1] | Port: [1080] |
| SOCKS User ID: [nobody] | |
| Protocol: [Socks5] |
Name Resolution: [Resolve all names remotely] |
Next, select New and browse to the name of the executable file ( ie diablo.exe ) and click
Ok.
This information is provided by JCM
(jcm@multimania.com).
Network configuration for Linux includes network interface configuration, name resolver configuration, and routing configuration. Because of the variety of the distribution of Linux (i.g. Red Hat, Slackware, Caldera, etc...), the setup files are different. For detail information regarding network setup, please refer to the HOWTO article < Linux NET-3-HOWTO, Linux Networking>. Here I just list some files for Caldera Linux distribution (kernal 2.0.33) if assuming that 192.168.0.1 is my gateway's ip and 192.168.0.2 is my linux machine's ip.
| /etc/resolv.conf | list all nameservers here |
| /etc/sysconfig/network | list the host name for this machine |
| /etc/hosts | list all host names to ip mappings |
| /etc/sysconfig/network-scripts/ifcfg-eth0 | list the ip and network address,network mask, gateway ip, network interface device name eth0 |
Standard ComSocks v2.6 doesn't have its own cache system, which may be a performance issue for a large local network or a slow Internet connection. It doesn't support proxy cascading directly (you can do a http outbound proxy by using port mapping. See Q.7.). ComSocks doesn't support some Internet games( you might be able to do so by using a third-party SOCKS library, ig. Hummingbird's SOCKS library from http://www.hummingbird.com or NEC SocksCap from http://www.socks.nec.com/sockscap.html). Access control / authentication has been taken out and put into Pro version. ComSocks doesn't support Microsoft Netmeeting.
