>>We've noticed an unusual behavior with our Solaris boxes (various
>>mostly Solaris 8). Anytime we x-windows to one of them or open a session
>>to one of them via a NT box (for those unix servers running Samba, etc)...
>>...the unix box first does a reverse DNS lookup against the incoming IP
>>address. If the reverse lookup fails, then the session fails (or more
> This sounds like a TCP Wrappers option that you can disable.
>>Is there any way to stop this behavior? We do not want/need to put every
>>workstation in the reverse zone!
> Why not? Just create names like pc01, pc02, pc03, etc.
This can happen from tcpwrappers, as suggested above, but also happens
whenever you start a login shell because solaris logs the source machine
name and is trying to look it up. The session should eventually start but
it needs the DNS lookup to fail (a few times IIRC) before the session
starts and the wait is so long that the application making the connection
times out first.
At least that is the experience I've had with ssh. It works, but takes a
long time to get a login when connecting from another UNIX system but
windows systems timeout.
You pretty much have to have the reverse DNS entries in your DNS server (or
a hosts file). I haven't found any other way around it.
due to a significant increase in scams being sent to my e-mail address, I am
no longer makinging it available for direct replies.