| 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 |
Hello, I'm not sure if this should go here, if not please point me to the correct notes conference. I have a customer who is running MCC BMS v1.1 and ETHERnim v2.3 on a VAXstation 3100 running VMS v5.4-3. He has been having a problem running ETHERnim and monitoring protocols. It appears that if he has a remote console connection active (egg, connected to a DECserver remote console via NCP> CONNECT NODE), he can't issue monitor protocol types command. He receives and error that the protocol is active or in use. However if he starts the ETHERnim monitor protocols first it works fine and he then can connect to the DECserver without any errors. Has anyone seen this particular problem before ?? Thanks in advance, Dominick Garzaniti CSC/CS Networks
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3255.1 | ETHERnim shares remote console protocol | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Fri Jun 26 1992 21:03 | 9 |
I believe that V2.2 of ETHERnim was when they added sharing of remote
console protocol. I suspect that when you use NCP CONNECT NODE, you
are locking down remote console for your process only.
I've had to juggle use of remote console for TSM, RBMS, ELM_AM,
ETHERnim, DECelms, and NCP CONNECT NODE quite often. Some share it,
some don't.
-Dan
| |||||