Hi,
I have probem with a custom software that is using LAT to connect to a bunch of DEC700 terminalservers. We have two identical machines, same OS, same software and configuration. One is supposed to be cold standby in case the other breaks. I re-configured the cold standby to do the same job, albeit with a different set of Terminalservers and physical location. I renamed some of the standby terminalservers and added them to NCP using their correct hardware address.
Due to Network port security I had to purge some lines since it was overwriting the Interface MAC addresses. Something went wrong - remote sessions started to hang right after login using telnet and set host, and I used @netconfig again, which seemed to have corrected the problem. I also renamed the computer and Decnet name.
Ever since the custom software does not seem to connect to the terminalserver anymore. I think I have compared everything between the still working and now not working, previous standby node checking things like: LAT$SYSTARTUP.COM where the interface and LAT ports are defined. I compared "mc ncp sho known circuit, lines and objects. Everything looks the same. I also compared the terminalservers and cannot see the difference.
I can connect to the Terminalservers using mc ncp connect node TS012, etc. on both computers, but there seems to be something missing. I have spend all weekend trying to find the reason....
On the node where it is not working: mc latcp sho ports shows:
_LTA1203: Application Connecting TS012/PORT_3/
_LTA1204: Application Connecting TS012/PORT_4/
_LTA1205: Application Inactive TS012/PORT_5/
_LTA1206: Application Inactive TS012/PORT_6/
The "connecting later changes to inactive"
On the node where it's working it shows:
_LTA1301: Application Inactive TS013/PORT_1/
_LTA1302: Application Inactive TS013/PORT_2/
_LTA1303: Application Active TS013/PORT_3/
_LTA1304: Application Active TS013/PORT_4/
working node>mc latcp sho port LTA1306
Local Port Name: _LTA1306: Local Port Type: Application (Queued)
Local Port State: Active
Connected Link: 1ST$LINK
Target Port Name: PORT_6 Actual Port Name: PORT_6
Target Node Name: TS013 Actual Node Name: TS013
Target Service Name: Actual Service Name:
not working node>mc latcp sho port lta1306
Local Port Name: _LTA1306: Local Port Type: Application (Queued)
Local Port State: Inactive
Connected Link:
Target Port Name: PORT_6 Actual Port Name:
Target Node Name: TS013 Actual Node Name:
Target Service Name: Actual Service Name:
not working node>mc ncp show node TS013 char
Node Volatile Characteristics as of 29-JUN-2009 09:25:33
Remote node = 1.1013 (TS013)
Service circuit = EWA-0
Hardware address = 00-00-F8-51-FB-15
Load file = MOM$LOAD:WWENG2.SYS
working node>mc ncp show node TS013 char
Node Volatile Characteristics as of 29-JUN-2009 09:28:12
Remote node = 2.1015 (TS013)
Service circuit = EWA-0
Hardware address = 08-00-2B-91-D6-AF
Load file = MOM$LOAD:WWENG2.SYS
working node>mc latcp sho con
ID Type Remote Node (Address) Sessions/Limit
---- -------- ------------------------------------- --------------
0230 Incoming TS011 (08-00-2B-91-D7-32) 6/ 64
04A0 Incoming TS013 (08-00-2B-91-D6-AF) 4/ 64
not working node>mc latcp sho con
%LAT-W-CMDERROR, error reported by command executor
-LAT-F-NOMORECONN, no more connections in database
not working node>mc ncp sho known lines
Known Line Volatile Summary as of 29-JUN-2009 09:28:30
Line State
EWA-0 on
working node>mc ncp sho known lines
Known Line Volatile Summary as of 29-JUN-2009 09:31:09
Line State
EWA-0 on
