This article applies to:

• WebMarshal

Question:

• How do I use WebMarshal with clients not running Windows?
• How can clients authenticate where there is no Windows or NDS domain available?

Procedure:

WebMarshal can be installed in an environment that does not include a Windows domain.

• WebMarshal must be installed on a Windows server. This server can either be a stand-alone server or a domain controller.
• Web browsing sessions can be authenticated by IP address or NDS account.
• Web browsing sessions can be authenticated by Windows account local to the WebMarshal server.
• Each user must have the user right, "log on locally", on the WebMarshal server.
• For each session you initiate to the Internet with a browser, you will be prompted for a user name and password. You may be able to set a browser to remember these credentials.
• If WebMarshal is installed as a stand-alone server, you must specify the WebMarshal machine name followed by a backslash and then the user name. For example:
  machine_name\user_name
• If WebMarshal is installed as a domain controller, you must specify the WebMarshal domain name followed by a backslash and then the user name. For example:
  domain\user_name
• For instructions on how to set a default domain in WebMarshal, so that you do not have to specify the domain name (or machine name) each time you log on, refer to Knowedgebase article Q10458.

Notes:

If the non-windows operating system used on the client machine supports logging on to a Windows domain, then you can configure the machine to log onto the WebMarshal domain. In this case if there is no other domain controller, the WebMarshal server must be installed as a domain controller. However, if the user changes his or her password, you may need to manually update the password on the domain so that WebMarshal can authenticate the user successfully.

This article was previously published as:

NETIQKB28933

Marshal KB206