Kbase 18213: You Are Not Authorized To Use ProControl On <host>! ( 5306 )
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
SYMPTOM(s):
You are not Authorized to use ProControl on <NT machine>! (5306)
The possibility to remotely start and stop databases is an important part of ProControl. But setting the system up may cause the error message:
"You are not Authorized to use ProControl on <NT machine>! (5306)
FIX:
1) It is a requirement that the versions communicating are of the same level, so make sure to check the Progress.Cfg on both machines.
2) When ProControl/ProService is started it is possible to choose on which host ProControl should run. The communication with the remote host is done through named pipes and requires that the following services are running:
SERVER SERVICE
WORKSTATION SERVICE
3) The user accessing the remote host needs to have permissions to log on and use the computer. This is checked in the USER MANAGER (FOR DOMAINS) > POLICIES > USER RIGHTS. The user or group where the user is a member should be added to:
RIGHT: Access this computer from network
To check that the user has indeed been granted the right, log on to the remote host using the users name and password.
4) It is also vital that the rights on the remote host have been correctly set up, so if any rights have been assigned to the registry or files, these have to accommodate the user. If permissions are changed then it might be necessary to kick out the users logged on to the remote host so that they can be validated using the new information. This is done from the server manager.
5) The only users that are able to start and stop ProService are ADMINISTRATOR or members of the administrators group, members of the Power user group, the LOCAL SYSTEM account and the account to whom the LOG ON AS has been granted. (The LOCAL SYSTEM ACCOUNT on the local host will not be able to access the network, as it has no password.)
6) The ProControl Access Group found in the Options folder within ProControl gives the possibility to grant access to any group or user and is another way of increasing the security. So this has to be checked if the user is unable to start and stop a database.
7) Some special accounts like GUEST will not be able to use the ProControl on a remote host because of the special security that has been set for the account.
With the above things checked it should now be possible to use ProControl on a remote host. The user might be greeted with an "access denied" message in the ProService screen but this is because the user is unable to start and stop ProService.