Common 1.0beta1, 11 March 1996 Copyright ©1996 by Equivalence, equival@ozemail.com.au |
Follow these steps to install a minimum configuration which will get you cruising the 'Web as soon as possible:
1. | Make sure that the Windows/NT host on which you wish to run Fire Door has the TCP/IP procotol and Remote Access installed. | |
2. | Make sure that the client machines which will be using Fire Door to access the Internet have the TCP/IP protocol installed. | |
| ||
3. | Ensure Remote Access on your Fire Door host can dial and autoconnect to your Service Provider | |
4. | Add the name of the Remote Access configuration found in step 3 to the list of remote systems using the Dialup Configuration page | |
5. | Find the IP address of the Domain Name Service (DNS) Name Server provided by your Internet service provider . | |
6. | Add a Fire Door relay for the "name/tcp" service which connects to the name server IP address found in step 3 using the Relay Agents page. | |
7. | Configure a SOCKS enabled browser (e.g. Netscape Navigator) | |
or non-SOCKS browser (Microsoft Internet Explorer) | ||
8. | Add security restrictions for all local clients | |
You should now be able to run your Internet browser on any client machine and have Fire Door automatically dial your service provider. Note that only one user at a time will be able to access this feature unless you register your copy of Fire Door. |
If you are on a Unix host, then you will have TCP/IP installed. For Windows/NT you may have to install TCP/IP via the Control Panel using the Network applet. Consult your Windows/NT manuals for more information on configuring a Windows/NT TCP/IP network.
When installing the client software, be sure to assign the IP address of the Fire Door host as the Domain Name Service (DNS) server. If you have another machine that is already a DNS server then that should remain the DNS server for the clients. However, the dial on demand feature may not work properly in this environment.
It is recommended that all of your client machine be allocated IP addresses on the 10.x.x.x network. These IP addresses have been specifically set aside for local networks and using them will improve the security of your network.
If the Remote Access System is not already installed on Windows/NT, you will have to install it via the Control Panel using the Network applet. Consult your Windows/NT manuals for more information on configuring a Windows/NT Remote Access System.
When setting up a Remote Access host, make sure that it can log in without user intervention. This usually involves setting up the SWITCH.INF file to script the log in sequence. If you can simply press the Dial button in the RAS Dialler program to connect to you ISP, then this will be suitable for Fire Door.
Press the button labelled "Accept", and a new page will be displayed confirming that the new configuration has been added. Use the "Back" button on your browser to return to the Fire Door Home Page.
See also Help on Dialup Parameters
Press the button labelled "Accept", and a new page will be displayed confirming that the new relay has been added. Use the "Back" button on your browser to return to the Fire Door Home Page.
NOTE - you should not install a DNS relay agent if your Fire Door host is already running a DNS server.
See also Relay Agent Help.
Select "Options" from the Netscape Navigator menubar, and then select the "Network Preferences" item. A tabbed dialog box will then appear. Select the "Proxies" tab.
On the 'Proxies" dialog, make sure then "Manual Proxy Configuration" radio button is set, and then select the "View..." button. In the field labelled "SOCKS host", type the IP number of the Fire Door host. In the adjacent "Port" field, enter the value "1080".
Press the "Ok" button to dismiss the "Proxies" dialog, and then the "Ok" button to dismiss the "Network Preferences" dialog.
You may use the name of the Fire Door host instead of the IP number, but only if that name is in the clients local hosts file. If this is not the case then the system will attempt a DNS look up, resulting in a superfluous dial up of the ISP to consult its DNS server, which will not know that name!
See also Relay Agent Help and Relays for World Wide Web clients
Press the button labelled "Accept", and a new page will be displayed confirming that the new relay has been added. Use the "Back" button on your browser to return to the Fire Door Home Page.
If the system refuses to accept the www/tcp service name you can either use 80/tcp instead or edit you services file (eg C:\WINNT\SYSTEM32\DRIVER\ETC\SERVICES) and add the www service name to it, setting it to the value 80.
See also Relay Agent Help and Relays for World Wide Web clients
If you have used the recommended practice of allocating IP addresses in the 10.x.x.x address space for your clients, then you will need to add a single access restriction of the form:
10.255.255.255 : 255.255.255.255
From the Fire Door Home Page, select on the hyperlink to the Security page and go to the Add New Access Restriction form. In the field labelled "Originator", enter the IP address of client, or a wildcard specification specifying multiple clients. In the field labelled "Destination", enter the wildcard value "255.255.255.255" to allow access to all Internet addresses, or any other IP address to the restrict access to that particular host (for example, your service provider proxy server).
Press the button labelled "Accept", and a new page will be displayed confirming that the Access Restriction has been added. Use the "Back" button on your browser to return to the Security page and confirm that the new retriction has been added to the Restriction List.
See also Security Help