HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Unable to Connect to Specific Port
Operating System - Linux
1829332
Members
2087
Online
109989
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
- Report Inappropriate Content
04-25-2005 05:48 AM
04-25-2005 05:48 AM
Unable to Connect to Specific Port
Hi there --
We have a server running Fedora Core 3 and I have modified the /etc/services file to open port 5666 to allow TCP connections. The syntax of the newly added line is as follows:
nrpe 5666/tcp # NRPE
After the line was added I stopped and restarted xineted via the startup script /etc/init.d/xinetd. After that, I tested the port's accessibility via telnet from a Windows 2000 workstation. The command syntax used there was:
telnet 5666
The result was an error message saying connection could not be established. I verified the system could be pinged and also was found via nslookup.
What else do I need to check for in order to correct this problem? Thanks.
We have a server running Fedora Core 3 and I have modified the /etc/services file to open port 5666 to allow TCP connections. The syntax of the newly added line is as follows:
nrpe 5666/tcp # NRPE
After the line was added I stopped and restarted xineted via the startup script /etc/init.d/xinetd. After that, I tested the port's accessibility via telnet from a Windows 2000 workstation. The command syntax used there was:
telnet
The result was an error message saying connection could not be established. I verified the system could be pinged and also was found via nslookup.
What else do I need to check for in order to correct this problem? Thanks.
A Journey In The Quest Of Knowledge
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2005 06:03 AM
04-25-2005 06:03 AM
Re: Unable to Connect to Specific Port
/etc/services is simply a translation map between service names (nrpe) and port numbers (5666). Putting a line in that file does not open a port.
What opens a port is either running a program that listens on that port, or adding an entry in /etc/xinetd.conf (or an appropriate file in /etc/xinetd.d), then restarting xinetd.
From a quick read of the documentation, it looks like you just run it:
/usr/local/nagios/bin/nagios -d
What opens a port is either running a program that listens on that port, or adding an entry in /etc/xinetd.conf (or an appropriate file in /etc/xinetd.d), then restarting xinetd.
From a quick read of the documentation, it looks like you just run it:
/usr/local/nagios/bin/nagios -d
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2005 11:53 AM
04-25-2005 11:53 AM
Re: Unable to Connect to Specific Port
The other thing you need to do is ensure it's allowed through the system's firewall.
Use 'iptables -nvL' to see what's currently allowed/not allowed.
Use 'iptables -nvL' to see what's currently allowed/not allowed.
One long-haired git at your service...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2005 01:11 AM
05-09-2005 01:11 AM
Re: Unable to Connect to Specific Port
Check whether port no 5666 is listening for telnet connections by using
netstat -nlp |grep 5666,
there should be xinetd listening on this port.
netstat -nlp |grep 5666,
there should be xinetd listening on this port.
Be Always Joy ......
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP