RDP internal error when connecting through VPN and LAN but through WAN works fine
Here's my setup.
2 Telus ADSL Connections at 2 seperate locations
Location 1 has a dsl modem and a TP-Link HL-R600VPN v4 (or whatever the latest is)
Location 2 has an actiontec3200M and a TP-Link HL-R600VPN v1 (or maybe v2)
The actiontec router is setup in bridge mode.
The IpSec tunnel is there, file sharing works completely fine, however I cannot RDP from the computer in location 2 to the computer in location 1. The first time I try to connect, it gets as far as logging in and then hits a black screen and eventually times out. When I try to reconnect, I get an internal error on the RDP program.
When I first set this up, i was able to connect but once I disconnected and tried to connect again, the same thing would happen with the black screen and then internal errors with successive attempts. It seemed as if i rebooted computer from location 1, i could connect again one time. At another time, i tried again several hours later without rebooting and it worked one time but failed the next. However in the last couple of days, it does not work at all.
Here's some other things I've noticed.
From location 2, i can access both routers at both locations using their local addresses.
From location 1, i cannot access location 2's router. This may be that the router is just blocking outside access or a symptom of what's causing the RDP issue.
If i open up port 3389 on the PC at location 1 and connect through RDP from the computer at location 2 using the WAN ip, it works every time.
Also, I cant remote to the computer in location 2 from the computer in location 1 using the LAN
Any thoughts?
networking vpn remote-desktop
asked Dec 14 at 23:10
Richard Chase
1
add a comment |
Here's my setup.
2 Telus ADSL Connections at 2 seperate locations
Location 1 has a dsl modem and a TP-Link HL-R600VPN v4 (or whatever the latest is)
Location 2 has an actiontec3200M and a TP-Link HL-R600VPN v1 (or maybe v2)
The actiontec router is setup in bridge mode.
The IpSec tunnel is there, file sharing works completely fine, however I cannot RDP from the computer in location 2 to the computer in location 1. The first time I try to connect, it gets as far as logging in and then hits a black screen and eventually times out. When I try to reconnect, I get an internal error on the RDP program.
When I first set this up, i was able to connect but once I disconnected and tried to connect again, the same thing would happen with the black screen and then internal errors with successive attempts. It seemed as if i rebooted computer from location 1, i could connect again one time. At another time, i tried again several hours later without rebooting and it worked one time but failed the next. However in the last couple of days, it does not work at all.
Here's some other things I've noticed.
From location 2, i can access both routers at both locations using their local addresses.
From location 1, i cannot access location 2's router. This may be that the router is just blocking outside access or a symptom of what's causing the RDP issue.
If i open up port 3389 on the PC at location 1 and connect through RDP from the computer at location 2 using the WAN ip, it works every time.
Also, I cant remote to the computer in location 2 from the computer in location 1 using the LAN
Any thoughts?
networking vpn remote-desktop
asked Dec 14 at 23:10
Richard Chase
1
Here's some more info after more testing: I setup file shares on both computers. Location 2 PC can access Location 1 PC but Location 1 PC can't access Location 2 PC. Location 2 PC can ping routers from both locations and computer from Location 2. Location 1 PC can ping it's own router but but location 2 router or location 2 PC.
– Richard Chase
Dec 14 at 23:16
Sounds like a NAT problem. You sure you set your tunnel up properly? Sounds like one of your routers is NATing the traffic and it’s causing routing issues as well.
– Appleoddity
Dec 15 at 0:52
This is a case for Wireshark. Be sure to update the firmware of all devices along the path. Then do some deep analysis. It would be ideal to capture a success and watch what happens when you close the RDP connection.
– HackSlash
Dec 17 at 16:29
I assume that it's setup properly. In the last few tests I've done, its worked a few times and then all of a sudden when I try to connect again, I get the black screen, kicked out and then internal error again. Seems to be hit and miss. Firmware is updated on all devices however one of the routers is fairly old so we've ordered a replacement to see if that is the issue. I attempted to put in a plain speedtouch DLS modem instead of the ActionTec device but it would not get a dsl signal. I assume their connection doesnt support those modems. What is Wireshark?
– Richard Chase
Dec 18 at 17:34
add a comment |
Here's my setup.
2 Telus ADSL Connections at 2 seperate locations
Location 1 has a dsl modem and a TP-Link HL-R600VPN v4 (or whatever the latest is)
Location 2 has an actiontec3200M and a TP-Link HL-R600VPN v1 (or maybe v2)
The actiontec router is setup in bridge mode.
The IpSec tunnel is there, file sharing works completely fine, however I cannot RDP from the computer in location 2 to the computer in location 1. The first time I try to connect, it gets as far as logging in and then hits a black screen and eventually times out. When I try to reconnect, I get an internal error on the RDP program.
When I first set this up, i was able to connect but once I disconnected and tried to connect again, the same thing would happen with the black screen and then internal errors with successive attempts. It seemed as if i rebooted computer from location 1, i could connect again one time. At another time, i tried again several hours later without rebooting and it worked one time but failed the next. However in the last couple of days, it does not work at all.
Here's some other things I've noticed.
From location 2, i can access both routers at both locations using their local addresses.
From location 1, i cannot access location 2's router. This may be that the router is just blocking outside access or a symptom of what's causing the RDP issue.
If i open up port 3389 on the PC at location 1 and connect through RDP from the computer at location 2 using the WAN ip, it works every time.
Also, I cant remote to the computer in location 2 from the computer in location 1 using the LAN
Any thoughts?
networking vpn remote-desktop
asked Dec 14 at 23:10
Richard Chase
1
Here's my setup.
2 Telus ADSL Connections at 2 seperate locations
Location 1 has a dsl modem and a TP-Link HL-R600VPN v4 (or whatever the latest is)
Location 2 has an actiontec3200M and a TP-Link HL-R600VPN v1 (or maybe v2)
The actiontec router is setup in bridge mode.
The IpSec tunnel is there, file sharing works completely fine, however I cannot RDP from the computer in location 2 to the computer in location 1. The first time I try to connect, it gets as far as logging in and then hits a black screen and eventually times out. When I try to reconnect, I get an internal error on the RDP program.
When I first set this up, i was able to connect but once I disconnected and tried to connect again, the same thing would happen with the black screen and then internal errors with successive attempts. It seemed as if i rebooted computer from location 1, i could connect again one time. At another time, i tried again several hours later without rebooting and it worked one time but failed the next. However in the last couple of days, it does not work at all.
Here's some other things I've noticed.
From location 2, i can access both routers at both locations using their local addresses.
From location 1, i cannot access location 2's router. This may be that the router is just blocking outside access or a symptom of what's causing the RDP issue.
If i open up port 3389 on the PC at location 1 and connect through RDP from the computer at location 2 using the WAN ip, it works every time.
Also, I cant remote to the computer in location 2 from the computer in location 1 using the LAN
Any thoughts?
networking vpn remote-desktop
networking vpn remote-desktop
asked Dec 14 at 23:10
Richard Chase
1
asked Dec 14 at 23:10
Richard Chase
1
asked Dec 14 at 23:10
Richard Chase
1
asked Dec 14 at 23:10
Richard Chase
1
asked Dec 14 at 23:10
Richard Chase
1
1
Here's some more info after more testing: I setup file shares on both computers. Location 2 PC can access Location 1 PC but Location 1 PC can't access Location 2 PC. Location 2 PC can ping routers from both locations and computer from Location 2. Location 1 PC can ping it's own router but but location 2 router or location 2 PC.
– Richard Chase
Dec 14 at 23:16
Sounds like a NAT problem. You sure you set your tunnel up properly? Sounds like one of your routers is NATing the traffic and it’s causing routing issues as well.
– Appleoddity
Dec 15 at 0:52
This is a case for Wireshark. Be sure to update the firmware of all devices along the path. Then do some deep analysis. It would be ideal to capture a success and watch what happens when you close the RDP connection.
– HackSlash
Dec 17 at 16:29
I assume that it's setup properly. In the last few tests I've done, its worked a few times and then all of a sudden when I try to connect again, I get the black screen, kicked out and then internal error again. Seems to be hit and miss. Firmware is updated on all devices however one of the routers is fairly old so we've ordered a replacement to see if that is the issue. I attempted to put in a plain speedtouch DLS modem instead of the ActionTec device but it would not get a dsl signal. I assume their connection doesnt support those modems. What is Wireshark?
– Richard Chase
Dec 18 at 17:34
add a comment |
Here's some more info after more testing: I setup file shares on both computers. Location 2 PC can access Location 1 PC but Location 1 PC can't access Location 2 PC. Location 2 PC can ping routers from both locations and computer from Location 2. Location 1 PC can ping it's own router but but location 2 router or location 2 PC.
– Richard Chase
Dec 14 at 23:16
Sounds like a NAT problem. You sure you set your tunnel up properly? Sounds like one of your routers is NATing the traffic and it’s causing routing issues as well.
– Appleoddity
Dec 15 at 0:52
This is a case for Wireshark. Be sure to update the firmware of all devices along the path. Then do some deep analysis. It would be ideal to capture a success and watch what happens when you close the RDP connection.
– HackSlash
Dec 17 at 16:29
I assume that it's setup properly. In the last few tests I've done, its worked a few times and then all of a sudden when I try to connect again, I get the black screen, kicked out and then internal error again. Seems to be hit and miss. Firmware is updated on all devices however one of the routers is fairly old so we've ordered a replacement to see if that is the issue. I attempted to put in a plain speedtouch DLS modem instead of the ActionTec device but it would not get a dsl signal. I assume their connection doesnt support those modems. What is Wireshark?
– Richard Chase
Dec 18 at 17:34
Here's some more info after more testing: I setup file shares on both computers. Location 2 PC can access Location 1 PC but Location 1 PC can't access Location 2 PC. Location 2 PC can ping routers from both locations and computer from Location 2. Location 1 PC can ping it's own router but but location 2 router or location 2 PC.
– Richard Chase
Dec 14 at 23:16
Here's some more info after more testing: I setup file shares on both computers. Location 2 PC can access Location 1 PC but Location 1 PC can't access Location 2 PC. Location 2 PC can ping routers from both locations and computer from Location 2. Location 1 PC can ping it's own router but but location 2 router or location 2 PC.
– Richard Chase
Dec 14 at 23:16
Sounds like a NAT problem. You sure you set your tunnel up properly? Sounds like one of your routers is NATing the traffic and it’s causing routing issues as well.
– Appleoddity
Dec 15 at 0:52
Sounds like a NAT problem. You sure you set your tunnel up properly? Sounds like one of your routers is NATing the traffic and it’s causing routing issues as well.
– Appleoddity
Dec 15 at 0:52
This is a case for Wireshark. Be sure to update the firmware of all devices along the path. Then do some deep analysis. It would be ideal to capture a success and watch what happens when you close the RDP connection.
– HackSlash
Dec 17 at 16:29
This is a case for Wireshark. Be sure to update the firmware of all devices along the path. Then do some deep analysis. It would be ideal to capture a success and watch what happens when you close the RDP connection.
– HackSlash
Dec 17 at 16:29
I assume that it's setup properly. In the last few tests I've done, its worked a few times and then all of a sudden when I try to connect again, I get the black screen, kicked out and then internal error again. Seems to be hit and miss. Firmware is updated on all devices however one of the routers is fairly old so we've ordered a replacement to see if that is the issue. I attempted to put in a plain speedtouch DLS modem instead of the ActionTec device but it would not get a dsl signal. I assume their connection doesnt support those modems. What is Wireshark?
– Richard Chase
Dec 18 at 17:34
I assume that it's setup properly. In the last few tests I've done, its worked a few times and then all of a sudden when I try to connect again, I get the black screen, kicked out and then internal error again. Seems to be hit and miss. Firmware is updated on all devices however one of the routers is fairly old so we've ordered a replacement to see if that is the issue. I attempted to put in a plain speedtouch DLS modem instead of the ActionTec device but it would not get a dsl signal. I assume their connection doesnt support those modems. What is Wireshark?
– Richard Chase
Dec 18 at 17:34
add a comment |
active
oldest
votes
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',
autoActivateHeartbeat: false,
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%2f1383712%2frdp-internal-error-when-connecting-through-vpn-and-lan-but-through-wan-works-fin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1383712%2frdp-internal-error-when-connecting-through-vpn-and-lan-but-through-wan-works-fin%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
Here's some more info after more testing: I setup file shares on both computers. Location 2 PC can access Location 1 PC but Location 1 PC can't access Location 2 PC. Location 2 PC can ping routers from both locations and computer from Location 2. Location 1 PC can ping it's own router but but location 2 router or location 2 PC.
– Richard Chase
Dec 14 at 23:16
Sounds like a NAT problem. You sure you set your tunnel up properly? Sounds like one of your routers is NATing the traffic and it’s causing routing issues as well.
– Appleoddity
Dec 15 at 0:52
This is a case for Wireshark. Be sure to update the firmware of all devices along the path. Then do some deep analysis. It would be ideal to capture a success and watch what happens when you close the RDP connection.
– HackSlash
Dec 17 at 16:29
I assume that it's setup properly. In the last few tests I've done, its worked a few times and then all of a sudden when I try to connect again, I get the black screen, kicked out and then internal error again. Seems to be hit and miss. Firmware is updated on all devices however one of the routers is fairly old so we've ordered a replacement to see if that is the issue. I attempted to put in a plain speedtouch DLS modem instead of the ActionTec device but it would not get a dsl signal. I assume their connection doesnt support those modems. What is Wireshark?
– Richard Chase
Dec 18 at 17:34