| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi, I've a customer who installed TSAM 1.0 and cannot used it register
his terminal server. He kept received "Can't communicate with target". What
would be the possible reasons for these and how could I remedy this
problem ? Please advise. Thanks.
- Eng Huat.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3793.1 | Passwords correct? | TOOK::FONSECA | I heard it through the Grapevine... | Thu Sep 24 1992 15:29 | 14 |
A number of things could have resulted in this message coming back. Most obviously, the server must be up, and must be on the same extended LAN as TSAM. More likely, the terminal server has a non-default login or maintenance password. (Or the customer specified the wrong password(s) during the registration sequence.) If the login password on the server is not "ACCESS" or the maint. password is not all zeroes, then the registration will fail. The attribute names to set for these are "Login key" and Maintenance Key". They are stored during the registration, and the values will be used in ensuing registration commands for the same terminal server unless re-specified. -Dave | |||||