| |||||||||||||||||||||||||||||||||
SERVICES Does SiteStak support "virtual mailboxes"? Does SiteStak support e-mail capability? Can the SiteStak run NT's Server service? Does SiteStak support newsgroup capability?
FEATURES/HOW TO
ACTIVE CONTENT/DB SUPPORT
IMPLEMENTATION
SECURITY
UPGRADES/REPAIRS/TROUBLESHOOTING
SERVER TROUBLESHOOTING
PERFORMANCE TIPS
Services Does SiteStak support "virtual mailboxes"? For example, if someone creates a site called "www.samplesite.com", can they receive email sent to webmaster@samplesite.com or johndoe@samplesite.com? The SiteStak is a web server only. It does not run mail services such as POP3, IMAP4, and SMTP. However, it is a straightforward DNS configuration to identify the SiteStak as the box to serve www.samplesite.com and your mail server to process all mail messages destined for johndoe@samplesite.com. Does SiteStak support e-mail capability? SiteStak is not an e-mail agent; it is a web site-hosting appliance with no native e-mail facilities. However, the web sites on a SiteStak can have FrontPage components or CGI server-side HTML Form processors, which send e-mail to a known SMTP server. You can also merely include mailto: hyperlinks in your content, which initiate client-side mail agents. Can the SiteStak run NT's Server service? We do not support it. However, if you use URL http://<sitestakname>/admin/admws.exe?operation=openshare you can. However, by enabling Server service, site administrators may be able to perform systems operations normally reserved for the server administrator. Does SiteStak support newsgroup capability? SiteStak functions solely as a Web server and does not run a Usenet news server. Features/How To What are the SiteStak performance and capacity numbers?
For SPECweb96 details, please refer to the SPEC web page. How can I send mail from a CGI program running on a SiteStak?If your CGI program knows the name or address of a mail gateway, the program can connect to the sendmail port at the mail gateway to have the gateway machine send mail on behalf of the SiteStak. SiteStak includes a perl library that implements the SMTP (sendmail) protocol. To use the library from a perl CGI program, use code like
require 'smtp.pl';
# ...
$server = 'mail.mynet.net';
$mail = &smtp'open_port(
if ( $mail )
&smtp'print( $mail, "Here's the body of the message.\n");
&smtp'close( $mail ); Can we go into the filesystem and do special things as we see fit or need? For each site, the site or server administrator can copy, rename, delete, make a file executable, or examine the links of any of the files, as they see fit. This can be done via a web browser or any FTP client. How are backups done? SiteStak provides an File Transfer Protocol (FTP) function to perform backup and restore operations. You must FTP the backup set to a general-purpose computer in your environment and then backup that machine with whichever proprietary backup tool you employ in your organization. Single web site backup set contents: All of one site's files and directories, including FrontPage extensions, transaction log and security databases. Entire SiteStak backup set contents: All web sites' files and directories and all server configuration information. Do the sites ever expire without having to manually delete them, perhaps via periodic authentication against a RADIUS or NT server? There is no expiration date on sites. Your TW-150 says it is for corporate Intranets; does this specifically mean it was not intended as a ISP shared web server? The TW-150 will handle about 50-100 sites comfortably. Does SiteStak function in Macintosh environments? SiteStaks function in any environment using TCP/IP, HTTP, and FTP. Are there any provisions for increasing disk space? RAM? SiteStak adheres to the appliance concept and hence does not support hardware upgrades. To add capacity, just rack and stack another SiteStak! How do you move a site from one SiteStak to another or from a non-SiteStak web server to a SiteStak? To move a site from SiteStak A to SiteStak B, you need to create the site on B, and then upload the sites files from A to the site on B. Many FTP clients allow you to move an entire directory tree from one machine to another with one command. What are the available publishing methods? FTP Can I buy just your OS/Server package as a separate software product? SiteStak is both hardware and software. They cannot be separated. Does SiteStak support FrontPage 98? Yes it does. For units manufactured before March of 1998, you download the FrontPage patch using the "update server" function off of the server administration home page. When I ftp to my web site, I am put in the root level of the SiteStak. Is it possible to be put in the directory of the web site? No, unfortunately it is not. You are put in the directory of the SiteStak because you are actually ftp'ing to the SiteStak. However, you only have access to your web site and no other sites. Use the FTP CD command to change directory to your site before PUTing data to the server. I currently offer web pages based on static IP addresses, e.g., www.joe.com has an IP and www.sue.com has a different IP and www.bill.com has another IP. Can I continue to offer this configuration? Each site may have an IP address different from the server's IP address. Sharing a single IP address for multiple virtual sites is also supported. Does SiteStak support multiple vanity names? A web site can now have many vanity names. For units manufactured before March of 1998, you download a patch using the "update server" function off of the server administration home page. I understand it's possible to set the SiteStak to point www.yourdomain.com to home.aname.com/yourfolder. How is this task performed? If your SiteStaks name is home.aname.com and you create virtual web sites with a site name of yourdomain and a vanity name of www.yourdomain.com, the content will be browsable using either of the following URLs: http://www.yourdomain.com Modern browsers use the HTTP Host: header field. A SiteStak can tell, based on this header field, that a request for www.yourdomain.com is referring to home.aname.com/~yourdomain. Do I have to reboot when creating a web site? You only have to reboot when you create a web site that has a different IP address than the SiteStak Server. But note, one important design concept regarding the SiteStak product is that is was designed to save in the consumption of IP addresses when creating web sites. This is accomplished by specifying the host name (or vanity name) and the same IP address as the SiteStak. We use the HOST header in the HTTP request to distinguish between virtual web sites sharing the same IP address. Can IPs be added/removed on the fly? Site and server IP addresses can be modified, but the server must be re-booted. You say that I must use DHCP or RARP. Currently I don't support either so what else would I have to buy? Nothing. The SiteStak Setup Wizard can assign a SiteStak its initial IP address. You can download it from setup.thiin.com. It is a Windows 95/NT program. Can you stack or daisy chain multiple SiteStaks? Currently, the SiteStaks are all independent web servers unaware of each other. If you want to provide load-balancing, then you must either place your SiteStaks in a round-robin DNS configuration or purchase a traffic director product that sits between your router and the SiteStaks. Can we pull the web server site logs to a client workstation so we can write our own reporting tools? You can download the complete transaction log for a site or for the whole server. The download protocol is FTP. Is there a way to generate a log per day? Daily server-wide transaction logs are generated automatically. Is the Index Server on the SiteStak configured to split data by virtual domain? The Index Server does keep the data for the entire SiteStak however there are extensions added to the version we use that will only allow a site to access data within his own site. So this should provide you with the security you desire What languages does SiteStak support? English is currently the only language available. What should I name my SiteStak? Should I use my custom URL? We do not recommend giving a SiteStak unit a name that serves as a custom URL. Although this may work it presents many limitations on the active content you want to publish for your Custom URL. Essentially if your Custom URL was "www.mycompany.com" then your SiteStak name would be "www". Clients specifying your Custom URL would by default be presented the SiteStak site directory list. A better solution would be to treat the SiteStak as you would any new computer you are adding to your business. When selecting a name follow the strategy you would normally use in that case. Then add to that your Fully Qualified Domain Name (FQDN). For instance you could name your first SiteStak "sitestak1". In configuring it you would specify its FQDN as "sitestak1.mycompany.com". Your company’s custom URL is better utilized for your own web site. This most likely will be the first web site you create on your SiteStak. Give this web site your company’s custom URL and let it remain mapped to the SiteStak's IP address. Then clients specifying your custom URL would obtain your customized web page. Your web page could then make use of all the same features as other sites on your SiteStak. How can I get rid of that annoying tilda? If you are already hosting web sites that share the same hostname, but do not use the tilda character to distinguish between top-level root content and virtual web site content, then you have a problem when you transition to SiteStak. The problem is that you have to tell your customers that their URLs are now different. http://www.isp.net/fred on the old server becomes http://www.isp.net/~fred on the SiteStak. There are two solutions to this problem. Solution 1: DNS CNAMES to the rescue One such solution is to use DNS CNAMEs to create aliases for each
virtual web site, but do so using a common domain such as isp.net.
For example, you could create the following aliases to the same
IP address:
www.fred.isp.net You don't need to get InterNIC involved because they share the same domain. You don't need different IP addresses for each site because the HTTP 1.1 HOST header will help the server distinguish between each virtual site. The downside of this method is that your customer's URL still changes. http://www.isp.net/fred becomes http://www.fred.isp.net On the other hand, your customer may be very happy to have a much simpler URL. Solution 2: HTTP Redirects to the rescue The HTTP protocol provides a way to redirect one URL to another. So, it is possible to redirect http://www.isp.net/fred (the old URL) to http://www.isp.net/~fred (the new URL). The way to configure this on the SiteStak involves creating a directory off of the SiteStak content root directory. The name of the directory must match the name of the virtual web site (i.e., "fred"). Then, publish an index.htm file that contains the redirection code. You have to do this for each URL that you want to redirect. For example, here is the contents of a file called "index.htm"
that should be published to a new directory called "fred" off
of the root directory of the SiteStak responding to www.isp.net
<HTML> With this directory and file present, requests for http://www.isp.net/fred get a page that states that the URL has changed and the request will automatically get redirected in 4 seconds. That gives time for the client to change his bookmarks. The downside of this method is that the redirection only works for the top-level URL. Requests for http://www.isp.net/fred/sales/lit.htm will result in a server "404 file not found" error. The upside of this method is that your customers do not have to change their business cards (which typically would only have the top-level URL on them anyway) and you don't have to run another server that issues redirects. We are working on providing this redirection functionality automatically so that you do not have to publish a file at all. Also, we will automatically redirect longer URLs so that your customer's customer will never see a 404 error message. Active Content/DB Support How can SiteStak be connected to databases? The SiteStak 1.0 product (what you have) can be connected to back end databases in the following ways:
Do you support Active Server Components that connect to back-end databases using ODBC? Currently we do not provide this but are investigating it for a future revision. Can Cold Fusion be used to publish to the sites? SiteStak does not support Cold Fusion. Does the device support ASP pages? SiteStak will execute ASPs (JScript and VBScript), but not Active Server Components. Can I run the Lotus Domino Web server on SiteStaks? SiteStak does not run Lotus Domino. Does the SiteStak support ISAPI-compatible server-side applications? No. Does the SiteStak support NSAPI-compatible server-side applications? No. Do you sell these machines with a development mode, that is, do you have an option to use the machines as generic servers? No, but if you have a very large volume opportunity, please send e-mail to our OEM Sales department at sales@thin.com. The first line of Perl scripts on our Unix box should contain #!/bin/perl. What is the proper path to execute perl on the SiteStak? Perl scripts on Win32 systems don't need a #!/bin/perl line; instead, perl scripts must be named with ".pl" suffix. I noticed that there are no cgi-bin directories in the client's individual directories. Should I create these directories or do I just set the execute bit on any directory for CGI? You can place CGI executables in any directory, but you must set the executable bit on that directory using the file manager. Unless there is a compelling reason to do otherwise, publishers should put cgi programs in the site's "bin" directory, which already has the execute bit set. Do not use a directory named "cgi-bin". It is a reserved directory name for the common cgi-bin directory. The common cgi-bin directory can be used to place programs that any virtual web site can access (read-only). What scripting languages are supported? CGI 1.1 You should also be able to run any statically-linked Win32 application. There is no specifically designed documentation for this. You can use most any available documentation for Microsoft and Win32 programming languages. There are example scripts in .../<web site>/bin/search and /<web site>/samples/search. Do you support Tcl? SiteStak does not support Tcl, but you could do the following: 1.) "publish" the Tcl binary and library files into a directory within the site. I used site "~testsite" and put the files in /~testsite/tknt/bin and /~testsite/tknt/lib. 2.) access Tcl programs by wrapping a perl script around them; put the perl script in /~testsite/bin/ with a .pl extension. The perl script needs to include lines like the following: ( $TK_HOME = $ENV{ 'PATH_TRANSLATED' } ) =~ s:bin.*:tknt:; Then the script can exec the Tcl script like system( "$TK_HOME/bin/tclsh hello.tcl" ); There may be some limitations, but the above approach works for a simple "hello world" Tcl script. What should my scripts be named? The script extensions are important. Active Server Pages: Files in executable directories that end in '.asp' Server Side Includes: Files in executable directories that end in '.stm' Perl: Files in executable directories that end in '.pl' Win32: Files in executable directories that end in '.exe' Is it possible to add our custom data collection DLL to the SiteStak's Server filter list for more distinct live usage data collection? SiteStak is hosted on IIS 3.0 with some extensions we added for additional caching capabilities and secured access. On the data collection question, to introduce the filters you desire would have effects on the processing we do in collecting the data we display on our administrative screens. However, you can get to the logs yourself by downloading the complete transaction log using the Administrative login. Go to the "View Logs" panel and select "Download Complete Transaction Log Now" or "Download Yesterdays Transaction Log Now". This will allow the transaction log to be downloaded to your client workstation. From that you can run any kind of filters you want to capture and report data. What search engine does SiteStak employ? SiteStak runs the Microsoft Index Server. Directories and documents are indexed automatically and virtual web site indexes are separated from each other. Are there any rules of thumb regarding creating executable directories? Mark all directories that you want to be executable as such, during site creation time, rather than at a later date when the sites has a great deal of content. When a site changes a directory to executable, all sites on the box are unavailable while the server rebuilds the index base of virtual roots. This can produce especially unpredictable results if a client tries to run an ASP executable during that time. How does ASP know the browser's capabilities? ASP uses a file named browsecap.ini to determine the browser's capabilities. The most up-to-date version of that file can be obtained from CyScape: 800-web-6889, or www.cyscape.com. Data General Corporation makes no warranties or claims of fitness regarding CyScape's browsecap.ini. Installing their file is done solely at your own risk. Implementation What OS is on the SiteStak? A stripped-down version of Windows NT 4.0 Server with Service Pack 3.0 What version of IIS does Sitestak use? SiteStak uses version 3.0 of IIS with many extensions for additional caching capabilities, secured access, flexible virtual web site containment and management, headless support, and overall ease-of-use for the owner of the box and the owner of each web site. Is SiteStak Year 2000 Qualified? SiteStak TW-150 and TW-500 hardware and the software that ships pre-loaded by Data General Corporation are Year 2000 Qualified. Data General Products designated at the time of sale or licensed as being Year 2000 ready ("Year 2000 Qualified") will correctly process, calculate, compare and sequence date data from, into and between the twentieth and the twenty-first centuries, including leap year calculations, when used in accordance with the associated Data General product documentation and provided that all hardware, firmware and software used in combination with such Data General products properly exchange accurate date data in appropriate Year 2000 correct format with Data General Products. Security How can I host secure (SSL) pages/sites on the SiteStak? SiteStak does not support SSL. How has the issue of security been addressed, is there a back door? Security is addressed by removing all access to the server except HTTP, FTP, and FrontPage. HTTP Basic Authentication usernames and passwords protect all administrative tasks. Upgrades/Repairs/Troubleshooting Will we have to pay for future software upgrades? Currently, there is no policy for version upgrades, beyond patches that we continue to develop and offer. What is the warranty policy? 3 year return to depot, standard. If the SiteStak breaks, can I buy all the parts I need at a local computer store to fix it? You must return the unit for repair. It is an appliance and is not meant to be opened. I connected the SiteStak to my network, ran the Setup Wizard, which completed successfully. It rebooted and the first 3 lights are on. But I can't ping it. Is DHCP running on your network? If so, that server assigned an IP address. See your network administrator to determine what IP address it assigned to the SiteStak box. You will need to give him the Ethernet address of the SiteStak box. It is printed on the product label on the back of the enclosure. Currently the SiteStak has a default home page that lists all of the current pages set up on the SiteStak. Is it possible to change this web page? That page is generated dynamically by software when sites are added, deleted, or modified. It cannot be changed. How can I find the Ethernet address of the SiteStak unit? The Ethernet address can be found on a plate attached to the back of the SiteStak unit. Why won't my scripts execute? If you publish scripts in a directory other than /bin or /_vti_bin (which are executable directories), you should use the File Manager to enable execute permission on the directory. Put all executable files in a separate directory which is marked for execute access. Currently, for SiteStak a directory can contain either readable files or executable files, but not both. This is a security precaution to keep browsers from being able to see the source code of your executables (when the "executables" are actually interpreted files). Important Note: You can keep your scripts in any directory except one named CGI-BIN, which causes system failure. Also, if a user tries to run a script in a directory that is not executable, the script will not run and its code will display. In addition, any of your web site's active server pages (.asp) must reside in an executable directory. Also note that your scripts must be compatible with Win32 on Intel. For example, acceptable scripts are Perl5, ActiveX, and server-side "include" files, but a Solaris UNIX script will not run. How can I learn about patches before downloading them? Click on Patches at http://update.thiin.com I deleted a web site but it doesn't take effect until I reboot. Why? This is not a problem with the SiteStak software but rather a feature of NT. When files are deleted in NT, they are actually marked for deletion and deleted when the reference to the file is zero. Since IIS caches files that are requested, there will still be reference to the file and hence the file and directory cannot be deleted. There is no way to determine when IIS will clean the file out of its cache, so rebooting the system may be the quickest way to have the file and directory deleted. You'll notice that if you actually don't browse any files from a particular site, you can delete the site and immediately create a new one with the same name. How do I load patches to my SiteStak? Go to the Update Screen from the Admin page and click on Update Now. Make sure that the Update Provider is http://update.thiin.com/updates. My executable scripts aren't working. Check the File Manager to see if your scripts directory has execute permission (indicated by a green x next to the directory name). This applies to all scripts that execute on the server, including: .exe, .cgi, .asp, .pl, or others. Enable execute permission in the File Manager by choosing the exec operation for the directory. Important Note: You can choose to keep your scripts in any directory except one named CGI-BIN, which causes system failure. Move your executable scripts elsewhere and delete any directory with this name. You can also download your site transaction log from the View Log page and review it for potential debugging clues. Give special attention to the Win32Status field (12th field) when debugging your CGI programs. My active server pages (.asp) aren't working. Check the File Manager to see if the directory in which they reside has execute permission (indicated by a green x next to the directory name). All files with the special active server page extension of .asp must be in an executable directory. Enable execute permission in the File Manager by choosing the exec operation for the directory. Do not use a directory named CGI-BIN, which causes system failure. Move your active server pages elsewhere and delete any directory with this name. My log file won't download. Check the log size on the Configure Site page. It may be set to zero (0). Increase the log file to the default size of 2MB and download it later after transactions occur. Contact your server administrator to see if logging is turned off for the entire server. The server administrator can override your transaction log file setting. If logging is turned off for the server, then your log file will be empty. I can't upload new files to publish. You have reached your limit for disk space usage. You can request more disk space from your server administrator, or you can:
My Network Usage and hits/sec. values are a lot higher than usual. Your site may be getting more popular, or an attacker may be trying to flood the site with requests to make it unavailable for use by others. Download your transaction log to determine if there is any pattern, such as a particular client address that is generating much of the activity. If you find something suspicious, contact your server administrator. If a particular client is disrupting service to the site, consider applying access restrictions to prevent the client from retrieving site contents. The Link Map won't display and I've waited a long time. Your site is large, and though the Link Map is not available when you request it, the system continues to parse your site until it finishes. Refresh your browser or try accessing the Link Map again later. Another possibility is that your workstation may be hung—try opening a new browser window. I copied (or renamed) a file and now my site contains broken links. You may have inadvertently overwritten another file of the same name. Refer to the Link Map to locate broken links, then upload or recreate the overwritten file to re-establish the links. A file in the Directory List has a red asterisk (*), but I know it's linked. The red asterisk beside a filename indicates that no other web page is pointing to it. It can, however, point to other pages in the web site. There may be nothing wrong with this situation; you can ignore the red asterisk or use your text editor to link a page to it. The old home page keeps displaying, even though I know I changed it. The system is loading the first home page it can find according to its search rules, and the page is not the one you want to display. The system searches each directory for a home page in the following order: 1) index.htm When the system finds one of the above files, it loads it and ignores any others. So, if you have a home page that you want the system to load, make sure its name allows it to load first. This applies to all directories. One or more users say my site denies them access to some or all pages. The system is applying address or access restrictions for these users. Perform the following steps to isolate the cause. For detailed troubleshooting information, refer to the security flowcharts.
I set my users' address and access restrictions but they accessed my site anyway. What happened? Did you enable security? Confirm that the Security check box on the Restrict Access page is showing a check mark. You may have forgotten to set restrictions on your site's directories. Even if you complete all the necessary steps to create user and domain groups in their respective databases, you must still set the restrictions on the directories. The Directory Security table on the Restrict Access page allows you to do this. Or, you may have deleted one or more of the daccess.dat files that are necessary for enforcing security. These files reside in your site's root and top-level directories and contain critical access restriction information. If you delete a daccess.dat file, you must reset its access restrictions on the Restrict Access page. How do I restrict access for only one user? Create a user group and add the user to it, then set any access restrictions. For even just one user, you must still place the user in a group. Users say that it takes a long time for them to access my site. There can be many causes for this delay. Try changing any users' address restrictions or domain names to their equivalent IP addresses, which speeds up processing time. How can I set different access restrictions on a directory below a top-level directory? You can't, unless you move the directory up to the top level. Access restrictions are set only for the root and top-level subdirectories. When you do this, each lower-level directory inherits the same restrictions as its top-level directory above. However, if its top-level directory has no restrictions set, then it inherits any restrictions from the root directory. Server Troubleshooting The SiteStak server is not responding. What should I do? Check LED indicators on the SiteStak's front panel. Is the System OK LED (second light) off and the Network OK LED (third light) repeating a 10 second on and one second off pattern? If so, the SiteStak has detected an IP address that conflicts with another device on the network. Perform the following procedure:
"No DNS entry" error messages appear when trying to browse a new web site. The site may have been assigned a different IP address than the SiteStak web server. In this case, a separate DNS entry must be made for the site name and IP address. Check the site's configuration and the DNS addressing information on the local DNS server. One of my web site administrators forgot the site password. You must assign a new password. For security reasons, administrative pages do not display any passwords. I've lost the SiteStak server administrator password. How do I get it back?
I keep getting two authentication dialog boxes when I access the SiteStak administrative home page. Some browsers may prompt you a second time to enter a username and password. This can occur when using the short version of a hostname and omitting the last forward slash at the end of the URL. For example, this URL may cause the problem: http://sitestak1/admin. If you want to use a short hostname for the server and avoid the second dialog box, include the forward slash. For example, http://sitestak1/admin/. One of my publishers complains of slow load times for their web site. What can I do? Select Monitor Server from the task bar and check the server usage statistics. If the CPU is registering very high activity, the server could be reaching capacity. A low cache hit rate, indicating files are being retrieved mostly from disk, impedes server performance. If the server statistics look acceptable, click the Per-Site Statistics for the site registering the complaint. Too much CPU and too few cache hits could be affecting the site's load times. Web sites should use sound design principles for caching graphics and other large files and managing active content such as scripts. I'm getting a message that I can't modify my web site settings because the page is in use. If your web site has indexing turned on, it is possible that the server is reading a page at the time you are trying to modify it. Wait a moment and try again. I've made configuration changes, but the displays don't seem to be changing. Depending on the pages you are browsing, there could be a couple of reasons. First, use the browser to refresh or reload any page that seems to display old information. In the Monitor Site->File Manager utility, click <Picture: rescan> to see any changes. I'm trying to publish with FrontPage, but I'm getting a "disk full" error message. You have exceeded the site's hard disk space limit and the SiteStak web server is interrupting the publishing operation. Delete some files and try again. If the same message appears, wait another moment so that the SiteStak web server has a chance to update the new file structure. You should also probably request that the site's hard disk limit be increased. I've gone to one of the monitor pages and it has no navigation or task bar. Some administration pages spawn a new browser window. These pages in the new window have no navigation; they are for viewing while you navigate the task bar in your original browser window. My "Yesterday's Transaction Log" contains only a partial list of the day's transactions. Your log file size limit is too small to hold all the transactions for the day. Try enlarging it. My "Per-Site Statistics" screen shows one site getting much more CPU, net usage, and hits than usual. The site may be getting more popular, or an attacker may be trying to flood the site with requests to make it unavailable for use by others. Download the site's transaction log to determine if there is any pattern to the increased activity, such as a particular client address that is generating much of the activity. If a particular client is disrupting service to the site, consider adding access restrictions to prevent the client from retrieving site contents or reconfiguring routers to keep out packets from the client. My "Monitor Server" page shows rapidly increasing authentication failures. Someone may be trying to guess the publishing or administrative passwords for the system. Download the server's transaction log to determine if there is any pattern to the authentication failures, such as a particular client address that is generating many of the failures. If a particular client is generating many of the authentication failures, you can change server and site passwords to values more difficult to guess. If you need to remove the server from service temporarily to investigate the possible attack, you can use the Configure Server page to change the server's port number to a number other than 80. This restarts the server on the new port. You can still manage and publish to the server using the new port, and only browsers who know the non-default port number can browse the server's content. Once the situation is rectified, change the port back to 80 to resume normal operation. I've lost the ability to connect to the SiteStak server from another LAN. Your network mask is probably incorrect for the SiteStak's IP address. Access the Configure Server page from a computer on the SiteStak's LAN and double-check that your IP Address and Network Mask values are correct. If they are, also check the DHCP and ARP entries for the SiteStak. You can modify these values from the Configure Server page, but the modifications require a hardware restart before taking effect. My per-site statistics don't seem to be working. The message says the data are for the last 6 minutes but there is no information displayed. Check the server's transaction log file size from the Configure Server page. A file size of zero turns off performance monitoring for all web sites. Enlarge the file size to activate monitoring. From the "Configure Site" page for a web site, I set the transaction log file size to 5 MB. But the file remains at zero. What's wrong? Check the server's transaction log file size from the Configure Server page. A file size of zero turns off transaction logging for all web sites. Enlarge the file size to activate transaction logging. Performance Tips Set your transaction log size to zero (0). Turns off logging for your site and thereby allows the server to process other tasks. Reduce the number of entries in the user and group databases. Reduces the amount of processing time to manage and interpret the database names, passwords, and associated access restrictions; reclaims disk space. When setting up security, reduce the number of groups assigned restrictions on your site or directories' access lists. Reduces the amount of processing time to manage and interpret the database names, passwords, and associated access restrictions. When setting up security, apply fewer overall access restrictions to users. Reduces the amount of processing time to manage and interpret access restrictions. When setting up security, use numeric IP addresses instead of domain names for groups. The system can process IP addresses much faster because it does not have to look up domain names. When setting up access restrictions on web sites, use numeric IP addresses instead of domain names. The system can process IP addresses much faster because it does not have to look up vanity names. Advise the publisher to reduce the number of images and image maps, CGI or PERL scripts, audio and video clips, multiple framesets, forms, animations, etc. Reduces the amount of processing and download time. |
|||||||||||||||||||||||||||||||||
|
| |||||||||||||||||||||||||||||||||
