Technical Note #1401
Internal Guide to the SITES.INI file
Application affected: Highway 101 Date Created: 7/19/96 Version Number: 1.0, 1.1, 2.0, 3.0x Last Modified: 7/2/97 File Date(s): All Created By: Mike Rimov Type of Note: Tech Guide Related Info: TN 1400
Keywords: guide highway sites.ini sites ini configuration fileSummary: Many users have expressed an interest in finding out more information regarding the configuration files SITES.INI and SETTINGS.INI. These files are covered here and in Tech Note #1400.
Details:
Below is a sample configuration of a typical sites.ini entry:
Section Header [My Service]. This is the name that will appear when End Users pick which site they wish to install to. If you have several branches with quite different settings, then we suggest that you might want to create a new section for each entry. For example:[My Service] NameServer=144.14.0.14 POPHost=mail.myservice.net SMTPServer=mail.myservice.net ReturnAddress=myservice.net DomainSuffix=myservice.net CompressedSLIP=1 HardwareHandshake=1 NNTPServer=news.myservice.net TimeHost=0.0.0.0 Netmask=255.255.255.0 Gateway=0.0.0.0 HomeWeb=http://www.centercomp.com/ SLIPLoginCMDName= PPPLoginCMDName= SLIP Offered=0 PPP Offered=1 Direct Offered=0 LowerCaseLogin=1 Phone1=123-4567,Local Dialup Number Phone2=1-503-123-4567,Long Distance Number DirectLoginCmdName= WinsockStack=Shiva IsFixedIP=0 SlipOffered95=0 PPPOffered95=1 SLIPLoginCmd95= PPPLoginCmd95= RNA LogOntoNetwork=1 RNA SoftwareCompression=0 RNA EncryptedPassword=0 RNA IpHeaderCompression=0 RNA UseDefaultGateway=1 RNA TerminalBeforeDial=0 PPPPrefix= PPPSuffix=[My Service - Oregon]This will give the end user the choice of connecting to either "My Service - Oregon", or "My Service - New York".
….
….[My Service - New York]
NameServer. The I.P. Address of your primary Domain Name Server. Highway 101 does not support at this time a secondary name server.
POPHost. Name of the POP3 Mail Server. The Eudora Light Mail Program does not currently support POP2.
SMTPServer. Name of the SMTP Server. On most systems, this will be identical to the POPHost, but for high volume mail loads, certain configurations might have a dedicated SMTP Server.
ReturnAddress. The portion of your customer’s return email address that is located to the right of the "@". For Example, a provider might have the configuration of the mail server being mail.myservice.net. However, any email being addressed to users on the service will be simply joe_user@myservice.net. In this case ReturnAddress is myservice.net.
DomainSuffix. The domain name that is registered with the Internic Database.
CompressedSLIP. Determines if Van Jacobsen CSLIP compression is to be used. The values are 1 for use CSLIP, 0 for no CSLIP. This is mainly used in the 16-bit Trumpet Winsock Stacks.
HardwareHandshake. Set to 1 if Hardware Handshaking is enabled, or 0 if this is disabled. Like Compressed SLIP, this is mainly used in the 16-bit Trumpet Winsock Stacks.
NNTPServer. Name of the USENET News Server on your site.
TimeHost. IP of the local Time Server. This is only used in 16-bit Trumpet Winsock Stacks, and as of this writing, has not been fully developed. This may be left blank.
Netmask. Netmask of your local dialup system. IP Value only.
Gateway. Default gateway IP number on your remote system. This is only used when using Trumpet Winsock as a Winsock Stack for LAN connections. This value is irrelevant for PPP/SLIP connections and may be set to 0.0.0.0
HomeWeb. Default location to start up Web browser. The starting page should be prefixed by http:// just to ensure compatibility with the widest range of Web browsers currently on the market.
SLIPLoginCMDName. The name of the script file to use to log in using SLIP for 16-bit Winsock stacks. This is only used in Trumpet Winsock Stacks. SLIP is not supported with SHIVA based Winsock stacks. If you require SLIP for 16-bit customers, you will need to contact Trumpet or other Winsock Stack vendors to inquire about licensing.
PPPLoginCMDName. The name of the script file to use to log in using PPP for 16-bit Winsock Stacks. This may be left blank. Please note that some versions of SHIVA based stacks on the market do not support scripting. To log in, Highway 101 automatically configures the winsock stack to open a terminal window after making a modem connection so the end user may log in.
SLIP Offered / PPP Offered. Set these entries to 0 if you do not want to offer either SLIP or PPP respectively, for your 16-bit Winsock Stack users. Set these entries to 1 to enable these options for your end-users.
Direct Offered. Set this entry to 1 if you have customers that connect to your network via LAN. In most cases this will not be needed, and the disabling value can be overridden by launching the Highway 101 setup with the /n option.
Phone##. These entries in the sites.ini file are consecutively numbered starting at phone1, then phone2, phone3, etc. The format of these entries is <PhoneNumber>,<Description> . If you wish to be able to have customers connect to your service via long distance, then you will need to create a separate entry for your long distance numbers in the same manner shown in the ini file excerpt above.
DirectLoginCmdName.Trumpet Winsock users only: script name to log onto LAN with TCP/IP. This may be left blank if this feature is not needed.
WinsockStack. Tells Highway which 16-bit Winsock Stack to expect when installing under Windows 3.1. The values are either Trumpet when installing Trumpet Winsock, or Shiva if using Shiva-PPP based Winsock Stack. The Winsock Stack that comes with both Microsoft Internet Explorer and Netscape Navigator Personal Edition is Shiva-PPP based.
IsFixedIP. Trumpet Winsock and Dial-Up Networking Users only. This is used if the end user has a fixed assigned I.P. number over a SLIP connection.
SlipOffered95. Do you wish to offer SLIP connections to your Windows 95 users. Highway 101 installs the SLIP and Scripting Tools for Windows 95 to make this possible. However, you will need to provide a Login Script for your users so that Windows 95 can automatically switch I.P. numbers upon SLIP login. Set this value to 1 if you wish to offer SLIP access to Win95 users, 0 if not.
PPPOffered95. Do you wish to offer PPP connections to your Windows 95 users. Set this value to 1 if you wish Win95 users to use Dial-Up Networking to be able to connect via PPP to your service, 0 if not.
SLIPLoginCmd95. The name of the script file to be used with Windows 95 Dial-Up Networking when connecting via SLIP. This is required for SLIP connections.
PPPLoginCmd95. The name of the script file to be used with Windows 95 Dial-Up Networking when connecting via PPP. This entry is not required. If it is left blank, Dial-Up Networking will open up a terminal window after it has connected. If the word "None" is entered then Windows 95 Dial-Up Networking will attempt to automatically negotiate Network Security. This will only work for systems that require login name and password input to log in. Systems that allow more complex login procedures will need a script if you wish to provide your customers with automatic login.
New Entries:
The following entries have been added to sites.ini as of version 3.03.
RNA Entries. These entries correspond to different TCP/IP Settings under Windows 95 Dial-Up Networking.
Figure RNA-1 - Dial-Up Networking Options RNA LogOntoNetwork. Set this to 1 if you want the "Log on to network" box checked.PPPPrefix: If your users require a special prefix to their login name, then enter that here. For example, if your client's login name is joe, and his PPP dial-in name is P.joe, then enter P. as the PPPPrefix. If there is no special prefix needed, then leave this entry blank.RNA SoftwareCompression: Set this to 1 if you want the "Enable software compression" box checked. If you have Windows NT as a Dial-Up Server, you should have this box checked. Otherwise, you should leave it set to zero.
RNA EncryptedPassword: Set this to 1 if you want the "Require Encrypted Password" box checked.
Figure RNA-2 - Other Dial-Up Networking Options RNA IpHeaderCompression: Set this to 1 if you want the "Use IP header compression" box checked. If you are having repeated connection problems with several clients, turn this off to try to increase the reliability of your connections.
RNA UseDefaultGateway: Set this to 1 if you want the "Use default gateway on remote network" box checked. This should be set to one in most cases.
RNA TerminalBeforeDial: Set this to 1 if you want the option "Open terminal window before dialing" turned on. Unless you are attempting to use custom init strings before dialing, you should leave this set to zero.
PPPSuffix: If your users require a special suffix to their login name, then enter that here. For example, if your client's login name is joe, and his PPP dial-in name is joeP, then enter P as the PPPSuffix. if there is no special suffix needed then leave this entry blank.
Note: If you require a special PPP login name that cannot be determined simply by a login name and either a prefix or suffix, then enter ? as both the PPPPrefix and PPPSuffix. Highway 101 will then prompt the end user for their PPP login name.Entries no longer needed:
The following entries in sites.ini are not being currently used by Highway 101.
SLIPMSS, SLIPMTU, SLIPRWIN, PPPMSS, PPPMTU. PPPRWIN, DIRMSS, DIRMTU, DIRRWIN. These entries were only useful under Trumpet Winsock which is not currently being supported.
HomeGopher. When the gopher client program is launched, what location should it start up at? The format of the entry is simply the name of the gopher server to start up with. Highway does not currently support gopher default selectors, so the gopher clients can only be configured by default to start at the root directory on the remote gopher server. Highway 101 currently is not shipping with a gopher client.