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:
1. The client machine/client user combination isn't matching the expected access record.
2. The client machine/client user combination matches an access record that specifies an unexpected Local Username (perhaps the name of a group account, or an account with restricted privileges).
To investigate and correct this situation you must be familiar with AcuServer server access configuration, and have access to root or Administrator privileges. We recommend that you work with your AcuServer system administrator.
The diagnostic procedures include:
1. confirming your client user name
2. confirming your client machine name
3. looking up your client user name/client machine name combination in the server access file
Diagnostics:
1. Confirm your client user name.
On UNIX clients:
Log onto the client system using the same user name and UNIX environment that resulted in the unexpected user name.
If the system is a UNIX system, enter "who am i" at the UNIX prompt.
Is the user name returned the name you expected?
On Windows and DOS clients:
The runtime uses the user name value that is set by the environment variable USERNAME. If USERNAME is not set, then 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, then the runtime uses the literal string "USER".
To confirm the presence (or absence) of the "USERNAME" environment variable, enter "SET" at the DOS prompt. SET will display the value of all DOS environment variables.
COMSPEC=C:\COMMAND.COM PATH=C:\;C:\DOS;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, then the literal string "USER" is passed.
2. Confirm the name of the client system.
On UNIX clients, enter:
hostname
The system will return its official network host name.
On DOS clients, enter:
pctcpcfg general host-name
The system will return its official network host name. If it is not correct, modify the "hosts" file in the directory where PC/TCP was installed.
For Windows 95/98 clients:
Under Windows 95 and Windows 98, the runtime uses the host name that is set in the Control Panel in the following menus:
Control Panel/Network/Configuration
Select TCP/IP, then choose:
Properties/DNS Configuration/Host
The name you specify for the "Host" entry is the one that the runtime uses.
For Windows NT/2000 clients:
Start/Settings/Control Panel/Network/Protocols
Select TCP/IP, then choose:
Properties/DNS/Host Name
The name you specify for the "Host Name" entry is the one that the runtime uses.
3. On the server, examine the server access file for the record that matches the client machine name/client user name combination. This requires root privileges on a UNIX server, and Administrator group privileges on a Windows NT or Windows 2000 server. It should be done by the AcuServer system administrator.
Run the server access file manager utility:
acuserve -access
Be sure to enter the name of the working server access file when prompted.
Select menu item [4] - "Display one/all security records." Respond "N" to the prompt: "Display all records?" To the next two prompts provide the client machine name and client user name respectively. The matching record will be displayed.
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.