set the appropriate port adress with your ip address
HTTP is 6588
In case you are unfamiliar with what a Proxy Server is (which is probably
unlikely, since you downloaded this), what it basically allows you to do is
share one internet connection with all the machines on your network. For
example; my main computer is the only one which has internet access, but I
have several other machines on my local network. By running the Proxy Server
on the machine that has the internet connection (my main machine), and setting
all the other machines to use a proxy, I can browse the web from them, just
like I can from the machine actually connected.
AnalogX Proxy is designed to be simple, small, and easy to use. It currently
only supports the following protocols:
HTTP (web browsers) (port 6588)
HTTPS (secure web browsers) (port 6588)
SOCKS4 (TCP proxying) (port 1080)
SOCKS4a (TCP proxying w/ DNS lookups) (port 1080)
SOCKS5 (only partial support, no UDP) (port 1080)
NNTP (usenet newsgroups) (port 119)
POP3 (receiving email) (port 110)
SMTP (sending email) (port 25)
FTP (file transfers) (port 21)
it does NOT work with ICQ, which really requires full Socks5 or a complicated
mess of UDP port mapping - but AIM and MS Messenger both work fine. Future
versions will include more protocols, but for most people this shouldn't be
a big deal.
:::Configuration:::
All configuration is done through the 'Configure' menu... When in this menu the
proxy is disabled (you'll notice the tray icon will be red), and when done, it
will automatically start back up.
:::Configuring your local network:::
In order to use this on your local network, you must be using TCP/IP as one of
the methods the machines have to talk to each other (this can be found inside
the Settings->Control Panel->Network, if you see TCP/IP, you're good to go).
If for some reason it doesn't work, ie, the other machines can't see the Proxy,
the most common problem is the IP addresses you have the network configured to.
There are only a couple that are valid to use on a local network, I would
recommend you use 10.0.0.x (where x is a number between 0 and 255 that will
be specific to each machine). Try changing the IP and then using the
Proxy again. Also, just because your machines can see each other, doesn't mean
that TCP/IP is configured properly; if you are unsure of whether or not this
is set up properly, do the following: Choose 'Run' from the start menu, and
type 'ping [IP]', so if the other machine has the IP of '10.0.0.1', you would
type 'ping 10.0.0.1'. If the machines can see each other, this will say some-
thing like 'Reply from...' blah blah blah; if they can NOT see each other, this
will say something like 'Request timed out.'
Unless you have your local IP address assigned to you, there are only three
groups of IP's that are valid for you to use on a machine that's connected to
the net (that won't collide with other machines). They are:
10.0.0.0 to 10.255.255.255 (Class A)
172.16.0.0 to 172.31.255.255 (Class B)
192.168.0.0 to 192.168.255.255 (Class C)
So make sure your LOCAL network IP's fall within one of these three ranges, or
you're more than likely going to have problems.
If you don't know your IP address, the simplest way to get it is to choose
'Run' from the system menu, and type 'winipcfg'. Make sure you do this when
you are NOT connected to the internet, otherwise you will just end up getting
your temporary internet IP address. Another method, is to go into the network
area (as outlined above), select TCP/IP, and it's in the IP Address Tab!
If you don't have TCP configured, here's what I would recommend setting your
local IP address's to; for the server, set it's IP to '10.0.0.1' and subnet
mask to '255.255.255.0'. Then, just increment the last number of the IP by
one for each remote machine; so the next machine would be IP '10.0.0.2' and
the subnet mask would remain '255.255.255.0'. Then, on the remote machine
you would configure the Internet Options (as mentioned above) to use the proxy
server IP of '10.0.0.1' at port '6588'; and you're done!
One more thing to note about the TCP configuration; once it's completed you'll
have TWO TCP configs - one that's used for your internet connection (which you
shouldn't have to change), and one that's used for communicating across your
local network (the 10.0.0.1 example). For some reason if you use Dialup
networking, and ADD another TCP/IP protocol, Windows binds it to the modem, and
there doesn't appear to be any easy way of changing this - if this happens to
you, I normally recommend removing the dialup networking configuration, then add
everything to get the local network going, then re-install the dialup networking
configuration.