Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - Linux
- >
- General
- >
- Delay After Connection To Linux Server
General
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2002 10:17 AM
12-09-2002 10:17 AM
Delay After Connection To Linux Server
Hi there,
I have a server running Red Hat Linux 7.3 with two ethernet interfaces. Each interface is connected to a separate network. The network on the first interface is an exclusive network to a small group of servers and has its own ip address and domain name. The second interface is connected to the company's network and has a company ip address and domain name. The problem that I am encountering is the following: After establishing a telnet connection to either one of the interfaces, there is about a one minute delay before a a login prompt is displayed on the screen. After it appears I am able to log into the system succesfully. The /etc/hosts file has the ip addresses and the respective domain names for each of the interfaces. The /etc/resolve.conf file has the ip address of the DNS servers the company uses and the hostname and ip address of the server in question has been added to the DNS server of the company. Is there a setting that needs to be modified to correct this problem?
I have a server running Red Hat Linux 7.3 with two ethernet interfaces. Each interface is connected to a separate network. The network on the first interface is an exclusive network to a small group of servers and has its own ip address and domain name. The second interface is connected to the company's network and has a company ip address and domain name. The problem that I am encountering is the following: After establishing a telnet connection to either one of the interfaces, there is about a one minute delay before a a login prompt is displayed on the screen. After it appears I am able to log into the system succesfully. The /etc/hosts file has the ip addresses and the respective domain names for each of the interfaces. The /etc/resolve.conf file has the ip address of the DNS servers the company uses and the hostname and ip address of the server in question has been added to the DNS server of the company. Is there a setting that needs to be modified to correct this problem?
A Journey In The Quest Of Knowledge
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2002 01:36 PM
12-09-2002 01:36 PM
Re: Delay After Connection To Linux Server
Once on the linux box, do a simple 'nslookup' of the host IP address you're telnetting *FROM* (not too).
It really does sound like there's an issue with the reverse lookup that gets performed when you telnet to the machine.
In older versions of the tcp wrappers, this was a configuruable flag in the /etc/hsots.{allow,deny} files (PARANOID lookup, tries to match forward/reverse lookups). By default, the RH tcp wrappers do a minimum of look the address up.
It's possible that whilst there's forward DNS lookup, there's no reverse for your IP range, thus causing the delay.
If this isn't it, then you'd best start looking at firewalls, and routing tables.
It really does sound like there's an issue with the reverse lookup that gets performed when you telnet to the machine.
In older versions of the tcp wrappers, this was a configuruable flag in the /etc/hsots.{allow,deny} files (PARANOID lookup, tries to match forward/reverse lookups). By default, the RH tcp wrappers do a minimum of look the address up.
It's possible that whilst there's forward DNS lookup, there's no reverse for your IP range, thus causing the delay.
If this isn't it, then you'd best start looking at firewalls, and routing tables.
One long-haired git at your service...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP