Hosting Windows 2000 web sites in a stable, shared environment imposes a number of limitations on the configuration of each web site. This is a short list of the limitations that we currently impose in our Windows 2000 environment.
We do not allow user-supplied executable files, DLLs, ISAPI plugins or COM objects in our shared Windows 2000 environment.
All new Windows 2000 domains are being created using the W3C Extended Log File format.
We currently do not support the WebTrends Log Analyzer extended plug-ins in our shared Windows 2000 environment.
We do not support the Visual InterDev development extensions, because they allow individual virtual domain users to register COM/DCOM objects with the core system, which could easily cause our shared server environment to become incredibly unstable. Please note that Visual InterDev is still fully compatible with the standard Frontpage 2000 extensions and Active Server Pages development does NOT require that the Visual InterDev developer extensions be loaded.
We do not run MS Index Server because of catalog problems occurring in the shared environment that Microsoft refuses to fix. Our suggested work around is to use Frontpage's WAIS search functionality instead. Customers could alternately program an Active Server Page to implement a custom search algorithm.
Directory Browsing is turned off, this is done to improve the security of your web site.
The root level directory for your web hosting account contains the following files and directories:
_private |
This directory is automatically created by FrontPage. It contains files that are not browse-able by Web users. DO NOT DELETE OR MODIFY THESE FILES. |
_vti_* |
All files with the _vti_*
prefix are FrontPage configuration files. DO NOT DELETE OR MODIFY THESE
FILES. |
images |
This directory is automatically created by FrontPage. It contains your site's image files. FrontPage automatically stores images in this directory. |
logs |
This directory contains your web site's Log files. Log files contain access and error records in a machine readable form. DO NOT DELETE OR MODIFY THESE FILES. |
postinfo.html |
This Is a FrontPage configuration file. DO NOT DELETE OR MODIFY THIS FILE. |
|
Deleting and/or modifying these files or directories can cause errors in your site's operation. Junctionbox will charge for time and materials used to fix problems caused by your changes.
We currently run the Frontpage 2002/XP server extensions on our Windows 2000 shared servers.
Frontpage permissions for our Windows 2000 virtual domain users are set as author and browse. Administrator access must be explicitly requested by the user. We do this to help users avoid corrupting their Frontpage virtual domain extensions.
Corrupting the FrontPage extensions will cause problems with publishing to your web site to the features on that site. Junctionbox charges for time and materials used to fix your FrontPage extensions.
More information can be found on our Windows 2000 SQL support page.
Customers wanting to create System DSNs for development, etc. on their
local machines may do so by creating an ODBC connection from their machine.
The server's location is: ntsql.junctionbox.net
Customers are responsible for all of their own data, including backups, extractions, and transformations. We will charge at our hourly consulting rate for customers insisting on Junctionbox doing their data manipulation.
An excellent resource for customers wishing to implement Active Server Pages on their web sites can be found at http://www.LearnAsp.com
We do not allow Windows 2000 users to directly access the ActiveX MAPI components on our shared servers. Instead we recommend using the mail forms built into FrontPage or use another type of ASP script.
You may use CDO to send e-mail from your account using smtp.junctionbox.net mail server. Use the following script from the Microsoft Q286431 KnowledgeBase article. The script should be named with a .vbs extension.
The Windows 2000 web servers have ASPEmail installed. Here is a sample script for using ASPEmail with the external smtp.junctionbox.net mail server.
We are currently running ActivePerl build 613 on all of our Windows 2000 shared servers. This build number implements the functionality of the standard Perl 5.6.0.613 distribution and all of the modules which that release contains. It is the policy of Junctionbox Online Services to not include commonly used external Perl modules as part of our offered libraries. We have many users within our shared Windows 2000 server environments, and each of the Perl users within those environments may be using any number of different revisions or versions of a particular Perl module for web scripting functionality. Adding to the standard library presents the possibility of breaking a user script by using the incorrect module version/code due to the precedence of the standard library in the hierarchy of the path search. We therefore ask all users to run additional modules within the context of their own path.
Perl tends to work best in our environment when used as a scripting language embedded within an Active Server Page. If used as a stand-alone script, the file must have an extension of .pl to function correctly.
Also, Windows 2000 Perl users don't need to call the bash shell in their scripts. Overzealous scripters doing so may be beaten soundly about the face and neck to remind them that they aren't using Unix. =8)
We are currently running PHP version 4.2.2 on all of our Windows 2000 shared servers. This allows our servers to run all php commands and allows for connections to MYSql which is not loaded on our shared server environment but can be loaded on a managed server if this is something you might desire.
Junctionbox does not support Microsoft Access in our shared Windows 2000 environment. The security risks associated with running Access in a shared virtual domain are significant. We cannot stop users from attempting to use Microsoft Access in our Windows 2000 environment, but we will not offer technical support to individuals attempting to use Microsoft Access in our environment. Users attempting to use Microsoft Access for Web database solutions are on their own.
Customers are responsible for all of their own data manipulation, including backups, extractions, and transformations. We will charge at our hourly consulting rate for customers insisting on Junctionbox doing their data manipulation.
If you encounter a problem with your domain not covered by support documentation, please mail a problem report to support@junctionbox.net. Please include the following information with your request:
Please be as descriptive as possible in your message. The more details you provide, easier it will be for us to diagnose and solve the problem.
Copyright © 2001 Junctionbox Online Services, Inc. All rights reserved.
info@junctionbox.net /
support@junctionbox.net
Junctionbox and the Junctionbox logo are registered trademarks of Junctionbox
Online Services. Certain other names, logos, designs, titles, words or phrases
on this site may constitute trademarks, servicemarks or tradenames of
Junctionbox or other entities which may be registered in certain jurisdictions.