Yes.
It has nothing to do with what address/name you are telneting to. It has
everything to do with the IP/Name of the host you are telneting from.
UNIX/Linux trys to do a reverse lookup on IP addresses for logging and other
reasons. It will not "complete" the telnet session, e.g. present you with
login: prompt until it times out the reverse resolve.
Try the test I posted before, it takes only a couple of minutes and is
definitive as it being a DNS reverse resolve problem or not.
HTH
--
John Hardman CCNP MCSE
""Luis Oliveira"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Should the logon time be so long even if I telnet by numeric address, say
> telnet xx.yy.zz.ww ?
>
>
>
> Regards
>
>
> // luis oliveira
>
>
>
> > At 04:27 PM 4/12/01 -0400, Luis Oliveira wrote:
> >
> >> Our machines have fixed IP addresses. We are experimenting a problem
when
> we
> >> try to telnet a Unix machine. It takes forever (almost half a minute).
The
> >> same problem with e-mail checking ( 30 seconds to logon on the server).
> >> Before we had just two subnets. Now we have more (private networks),
and
> the
> >> mail server is on a public network (DMZ) separated from us by a
firewall.
> We
> >> think that the problem is related with the Ciscos or the implementation
of
> >> the VLAN's. The company that implemented our network (which is a sister
> >> company of my company) until now as not found a solution to our problem
> and
> >> the mail users, which is everyone is becoming very upset with all this.
> >> Everything else works fine on the network works fine (copying files,
> browse
> >> the internet, that kind of stuff).
> >>
> >> Anyone have seen this kind of trouble before ? Can give some advice or
> steps
> >> to follow to eliminate this ?
> >>
> >> Sorry for the long post.
> >>
> >> Thanks
> >>
> >> // luis oliveira
> >
> > Hm. It sounds a lot like DNS issues. Do you have guys pointing to an
> > internal DNS server? Does your mail server resolve to an internal IP?
If
> > you do internal DNS, I can see where you might have "inside has
problems",
> > "outside is dandy" problems. Can you time the telnetting to the Unix
> > box? Are you sure it is not 75 seconds? (If it is, it is almost
> > definitely DNS issues). Have you tried doing "ping" floods to those
hosts
> > just to see what % of packet loss occurs, if any? It could very well be
> > other issues, but check your DNS setups to see if anything seems fishy
with
> > your internal DNS.
> >
> > -Carroll Kong
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=418&t=392
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
