Home Up Search Site Map 

Ant Internet Suite

Up
Stand-alone version

This section describes how to configure the Ant Internet Server Suite for use in a Topcat system.    It applies to Topcat Version 1.4 onwards.   (These instructions have been tested using Ant Internet Suite version 1.29b.)

For advice on using the stand-alone version of the Ant Internet Suite with Topcat click here.

Server

Install the server on a machine with its own hard disc - ie use a machine which boots from its own hard disc rather than a machine booting using Topcat.   Do not attempt to install on a machine booting using Topcat.

Configure the Ant Internet Suite Server for LAN use.   Ensure all elements are working before proceeding.   See the documentation which came with the Ant Internet Suite and Paul Vigay's website for more information.    However, ensure that the Server is on the same network/subnet as the Topcat NTServer, and that its IP address and sub-net mask are compatible.   Ensure that the Ant Server's IP address and host name is in the Hosts file (in !InetSuite.Internet.Files) - see the Ant Inernet Suite FAQ.

Client

Install a copy of the Ant Internet Suite Client software on a machine with its own hard disc- ie use a machine which boots from its own hard disc rather than a machine booting using Topcat, perferably a different machine to the one running the Ant Internet Suite Server above.   Do not attempt to install on a client booting using Topcat.

Configure the client software and ensure all elements are working before proceeding.

Topcat System

Copy the following applications from the disc-based machine configured above into a suitable folder on the NTServer running Topcat.   (Log on as Topcat to the NTServer connecting to the share: Topcat$.)   You can either create a new folder - eg Internet in ...Topcat.Server.Network or copy the applications to the ...Topcat.Armboot.Apps folder - where they will then automaticaly appear in Apps:

!Fresco
!Logon
!Marcel

You may also copy over the Tools folder or (selected applications within Tools if copying to Apps) as appropriate.

Do NOT copy the !InetSuite application.

Configuration within Topcat

Name Server

The Ant Internet Suite provides its own Domain Name Server (DNS) or Name Resolver.    Topcat should be configured to use the Ant Server as its DNS Server, and the Ant Server should then forward any names it does not know about to the ISP's name server.   So, in the DHCP Manager, set the IP address of option 006 - DNS Server to be that of the Ant Internet Suite Server configured above.   (See the Topcat Installation Guide for instructions on how to do this.)     You will then need to delete the IDxxxxxxx folders in ...Armboot.!Boot.MchConfig so that the new settings take effect on next re-boot of the clients.

!Fresco

Provided the networking has been set up correctly in Topcat (see the Topcat Installation Guide and ensure that Patch3 at least has been applied) and that the Ant Server is in the same subnet (check IP addresses and sub-net masks), then no further configuration should be necessary.

!Marcel

Logon to the NTServer in Windows as Topcat or user with Administrator privileges.    Grant Everyone change permissions to the following directory and sub-directories:

...!Marcel.Resources.Trace

No further configuration should be necessary.

Using !Fresco or !Marcel from a Topcat Client

In order to run !Fresco or !Marcel, the user must first run the !Logon application to log on to the Ant Internet Suite Server, which of course must be running and accessible over the network.

Then !Fresco or !Marcel can be started in the normal way.

Disclaimer

Whilst every attempt has been made to ensure the above advice is accurate and is provided in good faith, Microlynx Software Engineering Ltd cannot be held responsible for any losses or problems as a result of following these instructions.

Home ] Up ] Stand-alone version ]Back ] Next ]

Send mail to webmaster@microlynx.co.uk with questions or comments about this web site.
Copyright © 1998-2001 Microlynx Software Engineering Limited   E&OE
Last modified: June 03, 2004