A MultiNet enabled network comprises:
- A Single MultiNet Server
- MultiNet Enabled Workstations
- Any number of optional Administration clients.
The standard MultiNet distribution pack can be used to install all of these components.
Installing a MultiNet Server
The server should be the first MultiNet component to be installed. The only pre-requisite for the server computer is that it has access to the Internet via a modem, ISDN adapter, ADSL device or router.
On Windows 95/98/ME The MultiNet installation will automatically configure all the necessary networking components
On Windows NT/2000/XP you should ensure the following:
- TCP/IP has been installed (but not necessarily configured)
- NT Service Pack 3 or higher has been installed (NT only)
- You are logged in with administration privileges
Click on next to continue.
The installation will validate your TCP/IP configuration and prompt for any items which need to be reset for the server.
Installing Workstations
A workstation installation will validate the TCP/IP configuration and ensure that the server is addressable from the workstation computer. The installation will log-on to the server and automatically obtain the required settings and add a user to the server. The installation can automatically configure Internet Explorer and Outlook Express to access the server.
Installing Administration Clients
Administration Clients are optional. The server can be completely administered from the host computer. However, it is often beneficial to be able to administer the server from other computers on the network.
Terrapin MultiNet communicates with clients on your network using TCP/IP (Transmission Control Protocol / Internet Protocol). If your network is currently using NetBEUI or IPX/SPX then TCP/IP will need to be added for your network clients to have proxy access.
The addition of TCP/IP to your network will not interfere with your existing protocols and on Windows 95/98/ME computers will automatically be managed by the MultiNet installation.
Assigning IP addresses
On a TCP/IP network every device (computer, printer, router etc) must have a unique IP address. A device such as a router, or computer with a modem on it will need an IP address for each network that it is connected to and each IP address must be unique on its respective network. Note that a device connected to the Internet must have an IP address which is unique across the Internet. Usually this IP address is assigned automatically by the ISP to which the device is connected.
IP addresses on the Internal network need only be unique across the local network. So that there is no conflict between IP addresses used on private networks with those being used on the Internet, 3 ranges of IP addresses have been reserved for network use:
- 10.0.0.0 - 10.255.255.255
- 172.16.0.0 - 172.31.255.255
- 192.168.0.0 - 192.168.255.255
Any one of these ranges can be chosen for a network. If a network hasn't already been numbered, MultiNet will offer the 192.168.x.x range.
Dynamic v. Static Addresses
IP Addresses can either be specified for a device or they can be automatically obtained from a DHCP server each time the device is booted. A DHCP server is software which listens for requests from devices being booted and for each request it allocates an IP address 'dynamically'.
Dynamic allocation of IP addresses has advantages over static addressing. With dynamic addressing, it is not necessary for anyone to maintain the information as to which computer owns which IP addresses. Portable computers can also be moved between networks and automatically obtain a new IP address. The disadvantage of dynamic IP addresses is that on different occasions, different computers can have a particular IP address. For this reason the MultiNet server must be allocated a static address. The installation will test the IP address configuration and lock the address if it was dynamically obtained.
Only one DHCP server should be installed on a network. MultiNet offers a DHCP server. If your network already runs DHCP then you should decide whether to disable either the existing DHCP facilities or the MultiNet DHCP server. It is recommended that you use the MultiNet DHCP server as, unlike many others, it attempts to reallocate the same IP address to the same device on successive requests, resulting in a more static address scheme.
Index of Technical Papers
privacy policy
