> What happens if you telnet into it with the numeric IP address (i.e. > 10.10.11.2, etc)? Don't mean jack. The remote tcpd wrapper, telnetd, sshd, ftpd, food may (will likely these days) attempt to perform DNS lookups (reverse and/or forward) on YOUR (the client's) IP address/FQDN. For example, in tcpd's PARANOID mode, if the forward and reverse DNS entries don't agree with each other (which seems to be about 95% of the time for the Internet at large), tcpd will drop the connection. D * On Fri, Sep 15, 2000 at 10:52:03AM -0700, Jason wrote: > sinck@ugive.com wrote: > > > > \_ For some reason when people try to telnet into our Solaris box from > > \_ outside our firewall it takes an incredibly long time to get the > > \_ login prompt. I have seen this issue before but I can't remember how > > \_ the hell I fixed it. At first I thought it was a reverse DNS lookup > > \_ failure and so I setup DNS correctly on the client machine and it has > > \_ no problem doing an nslookup, nor does it take a long time to do a > > \_ traceroute or ping to the server with IP or name. > > > > Like you noticed, it smells like a reverse DNS issue. Reality check > > all the reverse DNSs of the boxes between the Solaris box and > > 'outside' and see if they come through ok on the Solaris box. It > > could be that your firewall isn't reverse DNS and the Solaris box > > can't get it....? > > > > Also, if you just adjusted the DNS, it might be in DNS propagation > > hell. > > What happens if you telnet into it with the numeric IP address (i.e. > 10.10.11.2, etc)? > > -- > jkenner@mindspring.com __ > I Support Linux: _> _ _ |_ _ _ _| > Working Together To <__(_||_)| )| `(_|(_)(_| > To Build A Better Future. | > > > ________________________________________________ > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail. > > Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss