By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your response...

Discuss This Question: 7 &nbspReplies

There was an error processing your information. Please try again later.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Can anyone explain why this port is opened?
Because something is listening on it. It went through a standard handshake, but either Nmap had no knowledge of what was expected or you weren't connecting from an appropriate source location.
As for "what" is doing the listening, perhaps only HP can answer.
Nmap reports it as 'tcpwrapped' to indicate that some type of security (or obscurity) is blocking access. Since a more normal RST wasn't returned and some handshaking succeeded, Nmap is notifying you that a TCP Wrapper is a likely explanation. It doesn't that that's what it is; it just has that kind of response profile.
HP might have a kind of service port that isn't otherwise useful. Or any number of other possibilities exist.
Tom

Tom, thanks for the response. I understand the tcpwrapper possibility, Nmap is just interpreting and it's probably wrong. But, the bottom line is that a port, 14000, is still open and listening. It fin-ack'd every attempt to connect. It didn't just sit there and not respond, it responded. I've googled for days looking for any references linking the port to HP and have found nothing. Regarding your comment, "either Nmap had no knowledge of what was expected or you weren’t connecting from an appropriate source location", exactly! Who or what is the appropriate source location? Is this a port that is used for firmware updates? I don't know, I just can't find any reference.
Thanks again.

...a port, 14000, is still open and listening. It fin-ack’d every attempt to connect.
That is, of course, the basic behavior that gets classified as "TCP Wrapper". Unless the correct form of authentication is provided, nothing will get through.
I did a cursory look for references to { HP port 14000 } and didn't see anything useful. Something like "firmware updates" came to mind, though I didn't really think that's what it was except that a 'fast FTP' function is sometimes expected to use port 14000.
Unless you get very lucky, I wouldn't expect an answer from anywhere but HP support. They ought to know what it is. (And if they don't know, they should be notified about it.)
Tom

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your reply...

Ask a Question

Free Guide: Managing storage for virtual environments

Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!

To follow this tag...

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy