It helps if you've set your domain and domain server correct!
These machines were originally "staged" in the US and then moved to the UK.
I didn't get the correct domain and domain server until today. Once I
changed these the delay and timeouts disappeared.
(sorry for the delay on the summary, Bank Holiday and all...)
Thanks to:
Sean O'Connell
Arrigo Triulzi
grabow_at_imk.fzk.de
Michael James Bradford
Roger Leonard
----------
From: Eiler, James A.
Sent: Sunday, April 25, 1999 12:57 PM
To: 'tru64-unix-managers_at_ornl.gov'
Subject: in a BIND?
This falls into a category I've seen in the archives, but the archived
solutions don't work for me.
I've got several systems, all running 4.0D with Patch Kit 3, on different
hardware platforms (some small servers, some workstations). When I telnet
to all but two of the systems from my PC, I get almost immediate response
with a login: prompt.
Two of the systems will timeout on my telnet request and I cannot connect.
(Note that both of these systems are side by side in the same sub-net.
The other systems are at various locations throughout our company's WAN,
each with different sub-net's, etc. Once-upon-a-time, these two systems
resided within a different LAN with the same problems.)
It used to be that I couldn't even telnet between these two systems without
excessive delays. But I put each other's system name/IP address in each
other's /etc/hosts file (from a recommendation I saw in the archives) and
this resolved that problem.
In order to telnet to these two rogue systems, I must first telnet to an
intermediate remote system, and then telnet to one (or the other) of these
problem children.
I set up all of the machines over the past several months - I must have
missed something on these last two.
Any suggestions?
Thanks,
Jim Eiler
Received on Tue May 04 1999 - 11:18:08 NZST