Can ping by hostname, can RDP by IP, but cannot RDP by hostname?
up vote
0
down vote
favorite
I'm trying to Remote Desktop to another Windows PC. Both computers are in the same WORKGROUP. I can ping the remote computer by its hostname, which responds with its IPv4 address. I could get that work after running Prefer IPv4 over IPv6 in prefix policies EasyFix from Microsoft. Before running the EasyFix, pinging remote host responded with IPv6.
I can also connect with Remote Desktop Connection using IPv4 and it works, however, trying to Remote Desktop with hostname gives me this error:
Remote Desktop can't find the computer "OTHERWINPC". This might mean that "OTHERWINPC" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.
What can be the issue?
networking dns remote-desktop ipv6 windows-networking
asked Jul 24 at 5:54
orad
18912
add a comment |
up vote
0
down vote
favorite
I'm trying to Remote Desktop to another Windows PC. Both computers are in the same WORKGROUP. I can ping the remote computer by its hostname, which responds with its IPv4 address. I could get that work after running Prefer IPv4 over IPv6 in prefix policies EasyFix from Microsoft. Before running the EasyFix, pinging remote host responded with IPv6.
I can also connect with Remote Desktop Connection using IPv4 and it works, however, trying to Remote Desktop with hostname gives me this error:
Remote Desktop can't find the computer "OTHERWINPC". This might mean that "OTHERWINPC" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.
What can be the issue?
networking dns remote-desktop ipv6 windows-networking
asked Jul 24 at 5:54
orad
18912
Guess: The remote computer also has an IPv6 address, and that IPv6 address isn't reachable? And remote desktop prefers IPv6 over IPv4, even with the prefix policy?
– dirkt
Jul 24 at 6:54
@dirkt That's correct. Remote computer is not reachable by IPv6, and apparently RDP prefers IPv6 over IPv4.
– orad
Jul 24 at 7:23
So the simplest fix would be to make it look like the remote computer only has an IPv4 address, for example by using a slightly different name, and entering it in the hosts file (if it has a static address). Or any other solution depending on how you've setup your local DNS.
– dirkt
Jul 24 at 8:11
Or fix whatever problem has broken IPv6 connectivity.
– Michael Hampton
Jul 24 at 13:59
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to Remote Desktop to another Windows PC. Both computers are in the same WORKGROUP. I can ping the remote computer by its hostname, which responds with its IPv4 address. I could get that work after running Prefer IPv4 over IPv6 in prefix policies EasyFix from Microsoft. Before running the EasyFix, pinging remote host responded with IPv6.
I can also connect with Remote Desktop Connection using IPv4 and it works, however, trying to Remote Desktop with hostname gives me this error:
Remote Desktop can't find the computer "OTHERWINPC". This might mean that "OTHERWINPC" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.
What can be the issue?
networking dns remote-desktop ipv6 windows-networking
asked Jul 24 at 5:54
orad
18912
I'm trying to Remote Desktop to another Windows PC. Both computers are in the same WORKGROUP. I can ping the remote computer by its hostname, which responds with its IPv4 address. I could get that work after running Prefer IPv4 over IPv6 in prefix policies EasyFix from Microsoft. Before running the EasyFix, pinging remote host responded with IPv6.
I can also connect with Remote Desktop Connection using IPv4 and it works, however, trying to Remote Desktop with hostname gives me this error:
Remote Desktop can't find the computer "OTHERWINPC". This might mean that "OTHERWINPC" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.
What can be the issue?
networking dns remote-desktop ipv6 windows-networking
networking dns remote-desktop ipv6 windows-networking
asked Jul 24 at 5:54
orad
18912
asked Jul 24 at 5:54
orad
18912
asked Jul 24 at 5:54
orad
18912
asked Jul 24 at 5:54
orad
18912
asked Jul 24 at 5:54
orad
18912
18912
Guess: The remote computer also has an IPv6 address, and that IPv6 address isn't reachable? And remote desktop prefers IPv6 over IPv4, even with the prefix policy?
– dirkt
Jul 24 at 6:54
@dirkt That's correct. Remote computer is not reachable by IPv6, and apparently RDP prefers IPv6 over IPv4.
– orad
Jul 24 at 7:23
So the simplest fix would be to make it look like the remote computer only has an IPv4 address, for example by using a slightly different name, and entering it in the hosts file (if it has a static address). Or any other solution depending on how you've setup your local DNS.
– dirkt
Jul 24 at 8:11
Or fix whatever problem has broken IPv6 connectivity.
– Michael Hampton
Jul 24 at 13:59
add a comment |
Guess: The remote computer also has an IPv6 address, and that IPv6 address isn't reachable? And remote desktop prefers IPv6 over IPv4, even with the prefix policy?
– dirkt
Jul 24 at 6:54
@dirkt That's correct. Remote computer is not reachable by IPv6, and apparently RDP prefers IPv6 over IPv4.
– orad
Jul 24 at 7:23
So the simplest fix would be to make it look like the remote computer only has an IPv4 address, for example by using a slightly different name, and entering it in the hosts file (if it has a static address). Or any other solution depending on how you've setup your local DNS.
– dirkt
Jul 24 at 8:11
Or fix whatever problem has broken IPv6 connectivity.
– Michael Hampton
Jul 24 at 13:59
Guess: The remote computer also has an IPv6 address, and that IPv6 address isn't reachable? And remote desktop prefers IPv6 over IPv4, even with the prefix policy?
– dirkt
Jul 24 at 6:54
Guess: The remote computer also has an IPv6 address, and that IPv6 address isn't reachable? And remote desktop prefers IPv6 over IPv4, even with the prefix policy?
– dirkt
Jul 24 at 6:54
@dirkt That's correct. Remote computer is not reachable by IPv6, and apparently RDP prefers IPv6 over IPv4.
– orad
Jul 24 at 7:23
@dirkt That's correct. Remote computer is not reachable by IPv6, and apparently RDP prefers IPv6 over IPv4.
– orad
Jul 24 at 7:23
So the simplest fix would be to make it look like the remote computer only has an IPv4 address, for example by using a slightly different name, and entering it in the hosts file (if it has a static address). Or any other solution depending on how you've setup your local DNS.
– dirkt
Jul 24 at 8:11
So the simplest fix would be to make it look like the remote computer only has an IPv4 address, for example by using a slightly different name, and entering it in the hosts file (if it has a static address). Or any other solution depending on how you've setup your local DNS.
– dirkt
Jul 24 at 8:11
Or fix whatever problem has broken IPv6 connectivity.
– Michael Hampton
Jul 24 at 13:59
Or fix whatever problem has broken IPv6 connectivity.
– Michael Hampton
Jul 24 at 13:59
add a comment |
4 Answers
4
active
oldest
votes
up vote
1
down vote
accepted
Answering myself: The fix was something really weird. First I made sure that both local computer and remote computer prefer IPv6 over IPv4 using the EasyFix. Then I noticed I could not ping the remote computer when I use all caps for hostname. I got:
Ping request could not find host MYHOME-PC. Please check the name and try again.
but could ping with any other casing like ping myhome-pc or ping MyHome-PC that came back with IPv6. I used all lowercase hostname to connect with remote desktop and that worked!
answered Aug 4 at 4:13
orad
18912
2
That's a little strange. Hostnames are not case sensitive. So it shouldn't matter if you have caps lock on or not. I wonder what's going on there.
– Michael Hampton
Aug 4 at 13:44
add a comment |
up vote
0
down vote
In your situation, when you used RDP the hostname, it should have returned the ipv6 address, so that you RDP failed.
You can use this workaround, add a CNAME(alias) DNS record of the ipv4 for the target PC in the DNS server. And then use the CNAME to RDP the target PC.
answered Jul 24 at 8:58
OOOO
83112
add a comment |
up vote
0
down vote
Try adding "\" to the beginning of the computer name
For your "OTHERWINPC" example, try "\OTHERWINPC" instead.
At least this is what worked for me. I only started encountering this error earlier this year. In light of the other comments here, perhaps it was due to some sort of IPv6 change in some upgrade. And maybe "\" ends up forcing IPv4.
answered Oct 1 at 23:43
MotohawkSF
1012
add a comment |
up vote
-1
down vote
Disabling IPv6 on this server 2012 box fixed the issue for me. Thanks.
answered Dec 3 at 18:10
Joel Rodriguez
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1342760%2fcan-ping-by-hostname-can-rdp-by-ip-but-cannot-rdp-by-hostname%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Answering myself: The fix was something really weird. First I made sure that both local computer and remote computer prefer IPv6 over IPv4 using the EasyFix. Then I noticed I could not ping the remote computer when I use all caps for hostname. I got:
Ping request could not find host MYHOME-PC. Please check the name and try again.
but could ping with any other casing like ping myhome-pc or ping MyHome-PC that came back with IPv6. I used all lowercase hostname to connect with remote desktop and that worked!
answered Aug 4 at 4:13
orad
18912
2
That's a little strange. Hostnames are not case sensitive. So it shouldn't matter if you have caps lock on or not. I wonder what's going on there.
– Michael Hampton
Aug 4 at 13:44
add a comment |
up vote
1
down vote
accepted
Answering myself: The fix was something really weird. First I made sure that both local computer and remote computer prefer IPv6 over IPv4 using the EasyFix. Then I noticed I could not ping the remote computer when I use all caps for hostname. I got:
Ping request could not find host MYHOME-PC. Please check the name and try again.
but could ping with any other casing like ping myhome-pc or ping MyHome-PC that came back with IPv6. I used all lowercase hostname to connect with remote desktop and that worked!
answered Aug 4 at 4:13
orad
18912
2
That's a little strange. Hostnames are not case sensitive. So it shouldn't matter if you have caps lock on or not. I wonder what's going on there.
– Michael Hampton
Aug 4 at 13:44
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Answering myself: The fix was something really weird. First I made sure that both local computer and remote computer prefer IPv6 over IPv4 using the EasyFix. Then I noticed I could not ping the remote computer when I use all caps for hostname. I got:
Ping request could not find host MYHOME-PC. Please check the name and try again.
but could ping with any other casing like ping myhome-pc or ping MyHome-PC that came back with IPv6. I used all lowercase hostname to connect with remote desktop and that worked!
answered Aug 4 at 4:13
orad
18912
Answering myself: The fix was something really weird. First I made sure that both local computer and remote computer prefer IPv6 over IPv4 using the EasyFix. Then I noticed I could not ping the remote computer when I use all caps for hostname. I got:
Ping request could not find host MYHOME-PC. Please check the name and try again.
but could ping with any other casing like ping myhome-pc or ping MyHome-PC that came back with IPv6. I used all lowercase hostname to connect with remote desktop and that worked!
answered Aug 4 at 4:13
orad
18912
edited Aug 6 at 19:32
answered Aug 4 at 4:13
orad
18912
answered Aug 4 at 4:13
orad
18912
answered Aug 4 at 4:13
orad
18912
18912
2
That's a little strange. Hostnames are not case sensitive. So it shouldn't matter if you have caps lock on or not. I wonder what's going on there.
– Michael Hampton
Aug 4 at 13:44
add a comment |
2
That's a little strange. Hostnames are not case sensitive. So it shouldn't matter if you have caps lock on or not. I wonder what's going on there.
– Michael Hampton
Aug 4 at 13:44
2
2
That's a little strange. Hostnames are not case sensitive. So it shouldn't matter if you have caps lock on or not. I wonder what's going on there.
– Michael Hampton
Aug 4 at 13:44
That's a little strange. Hostnames are not case sensitive. So it shouldn't matter if you have caps lock on or not. I wonder what's going on there.
– Michael Hampton
Aug 4 at 13:44
add a comment |
up vote
0
down vote
In your situation, when you used RDP the hostname, it should have returned the ipv6 address, so that you RDP failed.
You can use this workaround, add a CNAME(alias) DNS record of the ipv4 for the target PC in the DNS server. And then use the CNAME to RDP the target PC.
answered Jul 24 at 8:58
OOOO
83112
add a comment |
up vote
0
down vote
In your situation, when you used RDP the hostname, it should have returned the ipv6 address, so that you RDP failed.
You can use this workaround, add a CNAME(alias) DNS record of the ipv4 for the target PC in the DNS server. And then use the CNAME to RDP the target PC.
answered Jul 24 at 8:58
OOOO
83112
add a comment |
up vote
0
down vote
up vote
0
down vote
In your situation, when you used RDP the hostname, it should have returned the ipv6 address, so that you RDP failed.
You can use this workaround, add a CNAME(alias) DNS record of the ipv4 for the target PC in the DNS server. And then use the CNAME to RDP the target PC.
answered Jul 24 at 8:58
OOOO
83112
In your situation, when you used RDP the hostname, it should have returned the ipv6 address, so that you RDP failed.
You can use this workaround, add a CNAME(alias) DNS record of the ipv4 for the target PC in the DNS server. And then use the CNAME to RDP the target PC.
answered Jul 24 at 8:58
OOOO
83112
answered Jul 24 at 8:58
OOOO
83112
answered Jul 24 at 8:58
OOOO
83112
answered Jul 24 at 8:58
OOOO
83112
83112
add a comment |
add a comment |
up vote
0
down vote
Try adding "\" to the beginning of the computer name
For your "OTHERWINPC" example, try "\OTHERWINPC" instead.
At least this is what worked for me. I only started encountering this error earlier this year. In light of the other comments here, perhaps it was due to some sort of IPv6 change in some upgrade. And maybe "\" ends up forcing IPv4.
answered Oct 1 at 23:43
MotohawkSF
1012
add a comment |
up vote
0
down vote
Try adding "\" to the beginning of the computer name
For your "OTHERWINPC" example, try "\OTHERWINPC" instead.
At least this is what worked for me. I only started encountering this error earlier this year. In light of the other comments here, perhaps it was due to some sort of IPv6 change in some upgrade. And maybe "\" ends up forcing IPv4.
answered Oct 1 at 23:43
MotohawkSF
1012
add a comment |
up vote
0
down vote
up vote
0
down vote
Try adding "\" to the beginning of the computer name
For your "OTHERWINPC" example, try "\OTHERWINPC" instead.
At least this is what worked for me. I only started encountering this error earlier this year. In light of the other comments here, perhaps it was due to some sort of IPv6 change in some upgrade. And maybe "\" ends up forcing IPv4.
answered Oct 1 at 23:43
MotohawkSF
1012
Try adding "\" to the beginning of the computer name
For your "OTHERWINPC" example, try "\OTHERWINPC" instead.
At least this is what worked for me. I only started encountering this error earlier this year. In light of the other comments here, perhaps it was due to some sort of IPv6 change in some upgrade. And maybe "\" ends up forcing IPv4.
answered Oct 1 at 23:43
MotohawkSF
1012
answered Oct 1 at 23:43
MotohawkSF
1012
answered Oct 1 at 23:43
MotohawkSF
1012
answered Oct 1 at 23:43
MotohawkSF
1012
1012
add a comment |
add a comment |
up vote
-1
down vote
Disabling IPv6 on this server 2012 box fixed the issue for me. Thanks.
answered Dec 3 at 18:10
Joel Rodriguez
1
add a comment |
up vote
-1
down vote
Disabling IPv6 on this server 2012 box fixed the issue for me. Thanks.
answered Dec 3 at 18:10
Joel Rodriguez
1
add a comment |
up vote
-1
down vote
up vote
-1
down vote
Disabling IPv6 on this server 2012 box fixed the issue for me. Thanks.
answered Dec 3 at 18:10
Joel Rodriguez
1
Disabling IPv6 on this server 2012 box fixed the issue for me. Thanks.
answered Dec 3 at 18:10
Joel Rodriguez
1
answered Dec 3 at 18:10
Joel Rodriguez
1
answered Dec 3 at 18:10
Joel Rodriguez
1
answered Dec 3 at 18:10
Joel Rodriguez
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1342760%2fcan-ping-by-hostname-can-rdp-by-ip-but-cannot-rdp-by-hostname%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Guess: The remote computer also has an IPv6 address, and that IPv6 address isn't reachable? And remote desktop prefers IPv6 over IPv4, even with the prefix policy?
– dirkt
Jul 24 at 6:54
@dirkt That's correct. Remote computer is not reachable by IPv6, and apparently RDP prefers IPv6 over IPv4.
– orad
Jul 24 at 7:23
So the simplest fix would be to make it look like the remote computer only has an IPv4 address, for example by using a slightly different name, and entering it in the hosts file (if it has a static address). Or any other solution depending on how you've setup your local DNS.
– dirkt
Jul 24 at 8:11
Or fix whatever problem has broken IPv6 connectivity.
– Michael Hampton
Jul 24 at 13:59