how to test if can connect to port in rhel 7 (telnet client?)
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
On my local machine some network application is launched on port 3333 and I want to check that it "accepts connections". In this case in Windows I just type telnet to launch telnet client, and then o localhost 3333 to test if I can connect.
How can I do the same in RHEL 7? Should I also use telnet or probably there is another tool? This article suggest to execute yum install xinetd telnet telnet-server but I'm afraid if this will open any ports? I don't want to install any "server" functionality, only "client" telnet application. And definitely I do not want telnet to open any ports.
networking rhel
asked Nov 12 '14 at 19:55
javapowered
2592519
add a comment |Â
up vote
0
down vote
favorite
On my local machine some network application is launched on port 3333 and I want to check that it "accepts connections". In this case in Windows I just type telnet to launch telnet client, and then o localhost 3333 to test if I can connect.
How can I do the same in RHEL 7? Should I also use telnet or probably there is another tool? This article suggest to execute yum install xinetd telnet telnet-server but I'm afraid if this will open any ports? I don't want to install any "server" functionality, only "client" telnet application. And definitely I do not want telnet to open any ports.
networking rhel
asked Nov 12 '14 at 19:55
javapowered
2592519
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
On my local machine some network application is launched on port 3333 and I want to check that it "accepts connections". In this case in Windows I just type telnet to launch telnet client, and then o localhost 3333 to test if I can connect.
How can I do the same in RHEL 7? Should I also use telnet or probably there is another tool? This article suggest to execute yum install xinetd telnet telnet-server but I'm afraid if this will open any ports? I don't want to install any "server" functionality, only "client" telnet application. And definitely I do not want telnet to open any ports.
networking rhel
asked Nov 12 '14 at 19:55
javapowered
2592519
On my local machine some network application is launched on port 3333 and I want to check that it "accepts connections". In this case in Windows I just type telnet to launch telnet client, and then o localhost 3333 to test if I can connect.
How can I do the same in RHEL 7? Should I also use telnet or probably there is another tool? This article suggest to execute yum install xinetd telnet telnet-server but I'm afraid if this will open any ports? I don't want to install any "server" functionality, only "client" telnet application. And definitely I do not want telnet to open any ports.
networking rhel
networking rhel
asked Nov 12 '14 at 19:55
javapowered
2592519
asked Nov 12 '14 at 19:55
javapowered
2592519
asked Nov 12 '14 at 19:55
javapowered
2592519
asked Nov 12 '14 at 19:55
javapowered
2592519
asked Nov 12 '14 at 19:55
javapowered
2592519
2592519
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
You can install just the telnet package and have telnet client functionality. Alternately, you can use the nc command to test port connectivity if you'd rather not mess with telnet at all.
answered Nov 12 '14 at 20:01
John
11.3k11630
thanks, tried that. by some reasonnc localhost 3333tells "Connection refused", but when I executetelnetando localhost 3333i'm able to connect. Do you know whatncdoesn't work?
– javapowered
Nov 12 '14 at 20:13
@javapoweredncortelnetmight be using IPv4 or IPv6, or might be making different DNS or /etc/hosts lookups. We'd need more information, such as fromnetstatand so forth.
– thrig
Sep 13 at 21:42
add a comment |Â
up vote
2
down vote
echo -n > /dev/tcp/[hostname/ip]/[port]
return errorcode 0 if successful
edited Sep 13 at 18:31
RalfFriedl
4,1251625
answered Sep 13 at 18:20
notmyitblog
212
I don't know why this was downvoted. I was going to mention the same thing. (I've upvoted.) It's a Bash feature; I believe it was introduced in Bash 4. Welcome to the site; thanks for posting this!
– Wildcard
Sep 13 at 18:57
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You can install just the telnet package and have telnet client functionality. Alternately, you can use the nc command to test port connectivity if you'd rather not mess with telnet at all.
answered Nov 12 '14 at 20:01
John
11.3k11630
thanks, tried that. by some reasonnc localhost 3333tells "Connection refused", but when I executetelnetando localhost 3333i'm able to connect. Do you know whatncdoesn't work?
– javapowered
Nov 12 '14 at 20:13
@javapoweredncortelnetmight be using IPv4 or IPv6, or might be making different DNS or /etc/hosts lookups. We'd need more information, such as fromnetstatand so forth.
– thrig
Sep 13 at 21:42
add a comment |Â
up vote
1
down vote
accepted
You can install just the telnet package and have telnet client functionality. Alternately, you can use the nc command to test port connectivity if you'd rather not mess with telnet at all.
answered Nov 12 '14 at 20:01
John
11.3k11630
thanks, tried that. by some reasonnc localhost 3333tells "Connection refused", but when I executetelnetando localhost 3333i'm able to connect. Do you know whatncdoesn't work?
– javapowered
Nov 12 '14 at 20:13
@javapoweredncortelnetmight be using IPv4 or IPv6, or might be making different DNS or /etc/hosts lookups. We'd need more information, such as fromnetstatand so forth.
– thrig
Sep 13 at 21:42
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You can install just the telnet package and have telnet client functionality. Alternately, you can use the nc command to test port connectivity if you'd rather not mess with telnet at all.
answered Nov 12 '14 at 20:01
John
11.3k11630
You can install just the telnet package and have telnet client functionality. Alternately, you can use the nc command to test port connectivity if you'd rather not mess with telnet at all.
answered Nov 12 '14 at 20:01
John
11.3k11630
answered Nov 12 '14 at 20:01
John
11.3k11630
answered Nov 12 '14 at 20:01
John
11.3k11630
answered Nov 12 '14 at 20:01
John
11.3k11630
11.3k11630
thanks, tried that. by some reasonnc localhost 3333tells "Connection refused", but when I executetelnetando localhost 3333i'm able to connect. Do you know whatncdoesn't work?
– javapowered
Nov 12 '14 at 20:13
@javapoweredncortelnetmight be using IPv4 or IPv6, or might be making different DNS or /etc/hosts lookups. We'd need more information, such as fromnetstatand so forth.
– thrig
Sep 13 at 21:42
add a comment |Â
thanks, tried that. by some reasonnc localhost 3333tells "Connection refused", but when I executetelnetando localhost 3333i'm able to connect. Do you know whatncdoesn't work?
– javapowered
Nov 12 '14 at 20:13
@javapoweredncortelnetmight be using IPv4 or IPv6, or might be making different DNS or /etc/hosts lookups. We'd need more information, such as fromnetstatand so forth.
– thrig
Sep 13 at 21:42
thanks, tried that. by some reason
nc localhost 3333 tells "Connection refused", but when I execute telnet and o localhost 3333 i'm able to connect. Do you know what nc doesn't work?– javapowered
Nov 12 '14 at 20:13
thanks, tried that. by some reason
nc localhost 3333 tells "Connection refused", but when I execute telnet and o localhost 3333 i'm able to connect. Do you know what nc doesn't work?– javapowered
Nov 12 '14 at 20:13
@javapowered
nc or telnet might be using IPv4 or IPv6, or might be making different DNS or /etc/hosts lookups. We'd need more information, such as from netstat and so forth.– thrig
Sep 13 at 21:42
@javapowered
nc or telnet might be using IPv4 or IPv6, or might be making different DNS or /etc/hosts lookups. We'd need more information, such as from netstat and so forth.– thrig
Sep 13 at 21:42
add a comment |Â
up vote
2
down vote
echo -n > /dev/tcp/[hostname/ip]/[port]
return errorcode 0 if successful
edited Sep 13 at 18:31
RalfFriedl
4,1251625
answered Sep 13 at 18:20
notmyitblog
212
I don't know why this was downvoted. I was going to mention the same thing. (I've upvoted.) It's a Bash feature; I believe it was introduced in Bash 4. Welcome to the site; thanks for posting this!
– Wildcard
Sep 13 at 18:57
add a comment |Â
up vote
2
down vote
echo -n > /dev/tcp/[hostname/ip]/[port]
return errorcode 0 if successful
edited Sep 13 at 18:31
RalfFriedl
4,1251625
answered Sep 13 at 18:20
notmyitblog
212
I don't know why this was downvoted. I was going to mention the same thing. (I've upvoted.) It's a Bash feature; I believe it was introduced in Bash 4. Welcome to the site; thanks for posting this!
– Wildcard
Sep 13 at 18:57
add a comment |Â
up vote
2
down vote
up vote
2
down vote
echo -n > /dev/tcp/[hostname/ip]/[port]
return errorcode 0 if successful
edited Sep 13 at 18:31
RalfFriedl
4,1251625
answered Sep 13 at 18:20
notmyitblog
212
echo -n > /dev/tcp/[hostname/ip]/[port]
return errorcode 0 if successful
edited Sep 13 at 18:31
RalfFriedl
4,1251625
answered Sep 13 at 18:20
notmyitblog
212
edited Sep 13 at 18:31
RalfFriedl
4,1251625
edited Sep 13 at 18:31
RalfFriedl
4,1251625
edited Sep 13 at 18:31
RalfFriedl
4,1251625
4,1251625
answered Sep 13 at 18:20
notmyitblog
212
answered Sep 13 at 18:20
notmyitblog
212
answered Sep 13 at 18:20
notmyitblog
212
212
I don't know why this was downvoted. I was going to mention the same thing. (I've upvoted.) It's a Bash feature; I believe it was introduced in Bash 4. Welcome to the site; thanks for posting this!
– Wildcard
Sep 13 at 18:57
add a comment |Â
I don't know why this was downvoted. I was going to mention the same thing. (I've upvoted.) It's a Bash feature; I believe it was introduced in Bash 4. Welcome to the site; thanks for posting this!
– Wildcard
Sep 13 at 18:57
I don't know why this was downvoted. I was going to mention the same thing. (I've upvoted.) It's a Bash feature; I believe it was introduced in Bash 4. Welcome to the site; thanks for posting this!
– Wildcard
Sep 13 at 18:57
I don't know why this was downvoted. I was going to mention the same thing. (I've upvoted.) It's a Bash feature; I believe it was introduced in Bash 4. Welcome to the site; thanks for posting this!
– Wildcard
Sep 13 at 18:57
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f167628%2fhow-to-test-if-can-connect-to-port-in-rhel-7-telnet-client%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password