| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2641.1 | What else has changed? | STAR::VATNE | Peter Vatne, VMS Development | Mon Apr 23 1990 18:16 | 8 |
| There is no access control list other than the one you get with the
Customize Security menu from the Session Manager. Does the server
machine in fact still have the node and user name authorized? Do
other applications other than DECwrite get the same error? Is the
user perhaps using a different node than the one that was authorized?
Please look in SYS$MANAGER:DECW$SERVER_0_ERROR.LOG on the server node to
see what node and user name the server thinks is trying to connect to it.
|
| 2641.2 | | STAR::MCLEMAN | Jeff McLeman, Just thinking... | Tue Apr 24 1990 09:11 | 1 |
| Also, is the client node defined in the server's DECnet database?
|
| 2641.3 | | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Mon Apr 30 1990 15:41 | 5 |
| If someone defined the client node/user in the "Customize Security" section of
the session manager but never saved the changes, you would see this behavior
after logging in and out, or after a reboot, etc.
Burns
|