Set host via decnet over IP

[Michael LaRoche]

We have a system that we do a set host from one node a to node b that takes 35-60 seconds to connect. When we try the other way from b to a it's quick. We are running DecNet over IP with TCPIP vers. 5.4 eco 6. The systems are running OS 7.3-2. I've tried flushing the ncl cache on both systems but it still takes along time to get to the username prompt the one direction. Any help will be appreciated. TIA. Mike

[Jan van den Ende · Accepted solution]

Michael,

This sounds mightily like a DNS or Routing problem.
Could it be that, seen from the node where SET HOST lasts long, the first try to connect fails; waits for timeout; and then tries a second path, which responds?
Where the other direction, the irst try succeeds?

hth

Proost.

Have one on me.

jpe

[Hoff]

These are usually either a back-translate error somewhere or some sort of a related a DNS or BIND delay, or a case where a less-than-optimal transport choice was selected via DECNET_REGISTER and you're seeing what amounts to a transport-level timeout, and a fallback.

Try a numeric-address connect, too.

[Bill Hall]

Mike,

As Hoff suggested from node a try a $set host ip$xxx.xxx.xxx.xxx to node b's tcpip address. If this connects as fast as node b to a, then the problem is in name to address translation. If this is still slow, try a telnet from node a to node b by address. Try a telnet from node a to node b by hostname.

If name resolution is slow, compare the appropriate NCL files on the two systems, probably NET$DNS_CLERK_STARTUP.NCL and NET$SEARCHPATH_STARTUP.NCL. Does node a use an "off LAN" DECdns server by chance? If so, have you configured node a to be able to find the off LAN server by running SYS$MANAGER:DNS$CONFIGURE.COM?

Bill

[Michael LaRoche]

The solution was that the decnet address in the registry was pointing incorrectly. Thanks for all the good advice.