Vigay.com24
Nov
Search Vigay.com
 
 

Section 13 - ANT Internet Server Suite

Q13.1) How can I install the Server Suite on my LAN?
Q13.2) What do the different types of user mean?
Q13.3) Is there any feature I should disable for a user?
Q13.4) How can I get a PC or another machine to use the ANT Server?


Q13.1) How can I install the Server Suite on my LAN?

I haven't finished updating the server suite FAQ, so please check back soon.
 

Q13.2) What do the different types of user mean?

There are four types of user within the Server Suite: Guest, Pupil, Teacher and Admin.
Guest
Guest users have the unique property of being able to log in to the ANT Server from multiple machines simultaneously. For this reason it is strongly recommended that Guest users are not granted any Email or News access.
It is intended that Guest users are set up primarily for demonstration access to the World Wide Web. As such, Guest users should be created and deleted (or disabled) as and when required.
Pupil
The majority of your users should be of type Pupil.

Once a Guest or Pupil user is created, changes to their Internet access can only be made by Teacher or Admin users (from a client machine) using !UserTool.
Teacher
Teacher users can use !UserTool for almost all features; only the facility to add, edit or delete WWW pagesets is disabled. However, it is possible for such users to assign existing WWW pagesets to users (and vice versa).
Admin
Admin(istrator) users have ultimate power over all other users. Using !UserTool it is possible to use all the features to add, edit and delete both users and WWW pagesets. It is recommended that you keep the number of Admin users to an absolute minimum (1 or 2) and that they are not used on a regular basis.
Unlike all others, Admin users home directory for internal FTP access is the $ directory of the hard drive containing the ANT Server software. As such, the default settings created when the user is created do not work for remote web publishing.

 

Q13.3) Is there any feature I should disable for a user?

Of all the facilities provided in !UserTool for controlling a users' Internet access, Internal telnet access is the one you should be most aware of. This feature gives direct access to the machine running !InetSuite and !ANTUsers, so it's possible for a user who can do this to:
Use full command line access on your ANT Server.
Anything from disabling modules required for the machine to restart, through disabling the ANT Server software or reading other users email, to deleting the entire installation and/or reformatting the drive.
Access other machines on the Internet
Once a user has telnetted to the ANT Server it would be possible for them to bypass the restrictions offered by the Server Suite and telnet to other machines beyond your LAN.
Note this can be avoided by renaming or moving !InetSuite.Internet.Bin.telnet on the ANT Server.

For these reasons it is strongly recommended that Internal telnet access is only granted to one or two users - and only if they explicitly require it.
 

Q13.4) How can I get a PC or another machine to use the ANT Server?

Please do the following:
  1. Gathering information for configuring the new machine.
    1. From a machine running the ANT Client software load !InetConfg and, from within the LAN setup window, you'll need the Host name, Gateway and IP Mask.
    2. The Host name is of the form <client-host-name>.<domain>. For your new machine you'll need to use something similar, but the <domain> part should be the same for all machines on your LAN.
    3. If the IP Mask was displayed as Acorn Access, you should use 255.0.0.0 on the new machine.
    4. On the new machine, the Gateway and Name server should be same as that used by the ANT Client.
    5. The IP Address used on the new machine must be both unique to all machines on your LAN and fall within the IP Mask used. If you're unsure about this please contact your supplier.
    6. In !InetSuite.Internet.Files.Hosts on the ANT Server, you'll need to add an entry for the new machine of the form:
      <IP Address> <client-host-name>.<domain> <client-host-name>

    Once you have the IP Address, IP Mask, Name server and Gateway information, you can configure the TCP/IP software on the new machine.
  2. Allowing the new machine to access the ANT Server
    1. Using !UserTool, create a user whose Username is the new IP Address. The Real name could be something to describe the name, type and/or location of the machine.
    2. The User type can be left at Guest.
    3. Select Edit internet access and enable all the options required before clicking on Save.

  3. Configuring client software on the new machine
    For WWW access, you'll need to configure your browser to use the HTTP proxy server on the ANT Server. The easiest way to get this information is to use an existing ANT Client machine to log on to the ANT Server. Once done, load !Fresco, click Menu on the !Fresco icon and, from the Fresco choices window, select Proxies.
    To read email (for any user who has the permission to do so), you'll need to use an email client application which supports IMAP. If the machine is only being used by one person then it would be OK for the IMAP client software to download the mail from the server. However, it would be best if the IMAP client software can manage the mail on the server (in the same way as is done by !Marcel). An example application which can do this is Outlook Express.
    To configure both an email client and a news client, you'll need to use the name of the ANT Server for the IMAP, SMTP and NNTP servers.
    When an existing client user wishes to use the new client machine to read email from the ANT Server, they'll need to use their username and password. If they wish to send email they'll also need to amend their email address details.


Email Email this page to a friend

Last edit: 10th Apr 2016 at 1:56pm
(593 days ago)

Bookmark with:What are these?
delicious Deliciousdigg Diggreddit redditfacebook Facebookstumbleupon StumbleUpon

RSS Feed

Viewed 1199 times since 5th Aug 2006,
~ 0 views per day

^
 
Valid HTML 4.01!
Valid CSS!
Best viewed with a cup of tea Crafted by RISC OS