Problem: AcuServer establishes a connection with the client, but uses an unexpected user name (Local Username).
There are two common reasons for getting an unexpected Local Username on the server:
To investigate and correct this situation you must be familiar with AcuServer server access configuration, and have access to root or administrator privileges. Work with your AcuServer system administrator.
The diagnostic procedures include:
Is the user name returned the name you expected?
If a user is logged into a Windows NT/2000 workgroup or domain, AcuServer will use the user's log-in name. Otherwise, it uses the user name value that is set by the environment variable USERNAME. If USERNAME is not set, the runtime uses the value that is set by the environment variable USER. (The values of these variables are case-sensitive.) If neither of these environment variables is set, the runtime uses the literal string USER.
To confirm the presence (or absence) of the USERNAME environment variable, enter SET at the command prompt. SET will display the value of all environment variables.
COMSPEC=C:\COMMAND.COM PATH=C:\;C:\WINDOWS;C:\MOUSE; PROMPT=$P$G USERNAME=BERNIE
If USERNAME is defined, the value of USERNAME is the name passed to AcuServer. Otherwise, the variable USER is checked. (Both of these variables are case-sensitive.) If USER is not set, the literal string USER is passed.
The system will return its official network host name.
The name you specify for the Host Name entry is the one that the runtime uses.
The AcuServer system administrator should be able to determine whether this is the appropriate and expected access record for the client machine name/client user name combination and take any necessary steps to modify the record, or add a new one.