Remote Desktop Dropouts: “Because of an error in data encryption, this session will end.”
up vote
3
down vote
favorite
I'm getting some strange connection problems when trying to remote desktop to a Vista box. It connects and works for a while then disconnects with the following message:
"Because of an error in data encryption, this session will end. Please try connecting to the remote computer again."
Any help would be great!
windows-vista remote-desktop
add a comment |
up vote
3
down vote
favorite
I'm getting some strange connection problems when trying to remote desktop to a Vista box. It connects and works for a while then disconnects with the following message:
"Because of an error in data encryption, this session will end. Please try connecting to the remote computer again."
Any help would be great!
windows-vista remote-desktop
Are the two machines on the same LAN or are you connecting across a router, the Internet, etc?
– boot13
Sep 2 '10 at 1:26
@boot13 The connection is via a VPN over the Internet.
– Luke Quinane
Sep 2 '10 at 1:40
Ah. Which VPN client are you using? You might want to read any documentation you can find on that client, looking for notes on using RDP. You could also use it to narrow down your search. Anyway, from what I've seen so far, this is one of those weird problems that a few people are having but nobody knows how to resolve (+1).
– boot13
Sep 2 '10 at 5:22
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm getting some strange connection problems when trying to remote desktop to a Vista box. It connects and works for a while then disconnects with the following message:
"Because of an error in data encryption, this session will end. Please try connecting to the remote computer again."
Any help would be great!
windows-vista remote-desktop
I'm getting some strange connection problems when trying to remote desktop to a Vista box. It connects and works for a while then disconnects with the following message:
"Because of an error in data encryption, this session will end. Please try connecting to the remote computer again."
Any help would be great!
windows-vista remote-desktop
windows-vista remote-desktop
asked Sep 1 '10 at 23:46
Luke Quinane
292716
292716
Are the two machines on the same LAN or are you connecting across a router, the Internet, etc?
– boot13
Sep 2 '10 at 1:26
@boot13 The connection is via a VPN over the Internet.
– Luke Quinane
Sep 2 '10 at 1:40
Ah. Which VPN client are you using? You might want to read any documentation you can find on that client, looking for notes on using RDP. You could also use it to narrow down your search. Anyway, from what I've seen so far, this is one of those weird problems that a few people are having but nobody knows how to resolve (+1).
– boot13
Sep 2 '10 at 5:22
add a comment |
Are the two machines on the same LAN or are you connecting across a router, the Internet, etc?
– boot13
Sep 2 '10 at 1:26
@boot13 The connection is via a VPN over the Internet.
– Luke Quinane
Sep 2 '10 at 1:40
Ah. Which VPN client are you using? You might want to read any documentation you can find on that client, looking for notes on using RDP. You could also use it to narrow down your search. Anyway, from what I've seen so far, this is one of those weird problems that a few people are having but nobody knows how to resolve (+1).
– boot13
Sep 2 '10 at 5:22
Are the two machines on the same LAN or are you connecting across a router, the Internet, etc?
– boot13
Sep 2 '10 at 1:26
Are the two machines on the same LAN or are you connecting across a router, the Internet, etc?
– boot13
Sep 2 '10 at 1:26
@boot13 The connection is via a VPN over the Internet.
– Luke Quinane
Sep 2 '10 at 1:40
@boot13 The connection is via a VPN over the Internet.
– Luke Quinane
Sep 2 '10 at 1:40
Ah. Which VPN client are you using? You might want to read any documentation you can find on that client, looking for notes on using RDP. You could also use it to narrow down your search. Anyway, from what I've seen so far, this is one of those weird problems that a few people are having but nobody knows how to resolve (+1).
– boot13
Sep 2 '10 at 5:22
Ah. Which VPN client are you using? You might want to read any documentation you can find on that client, looking for notes on using RDP. You could also use it to narrow down your search. Anyway, from what I've seen so far, this is one of those weird problems that a few people are having but nobody knows how to resolve (+1).
– boot13
Sep 2 '10 at 5:22
add a comment |
3 Answers
3
active
oldest
votes
up vote
0
down vote
From this thread, http://www.techzonez.com/forums/archive/index.php/t-9868.html, it sounds like you may have your Vista computer setup in the router as the DMZ. Other suggestions are to delete any network protocols except the basics to see if that fixes it.
Hope this helps
the remote computer is just connected to a basic switch, no DMZ setting. Both local and remote PCs only have IPv4 and IPv6.
– Luke Quinane
Sep 2 '10 at 1:16
add a comment |
up vote
0
down vote
These answers are not correct, you can fix this by Simply uninstalling the Link-Layer Topology (Mapper I/O Driver and Responder) protocols, as well as the QoS Packet Scheduler service (you can add them back again afterwards) in the Local Area Connection of the client machine (not the server/target). You must uninstall, not simply remove the checkmark next to the protocol or service.
1
Anything to back that up?
– Canadian Luke
Jul 31 '13 at 22:25
I am not the one who answered but I found the reference here from a comment made by "Garth Rautenbach": social.technet.microsoft.com/Forums/windowsserver/en-US/…
– wandersick
Sep 15 '17 at 6:48
add a comment |
up vote
0
down vote
My issue was resolved by starting the Link-Layer Topology service. It was previously set to Manual and was not started after I had reinstalled Windows 7.
2
Welcome to SuperUser. Your answer would be even better if you edit it to provide some explanation as to why your solution addresses the OPs question.
– Twisty Impersonator
Dec 17 '14 at 21:05
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
From this thread, http://www.techzonez.com/forums/archive/index.php/t-9868.html, it sounds like you may have your Vista computer setup in the router as the DMZ. Other suggestions are to delete any network protocols except the basics to see if that fixes it.
Hope this helps
the remote computer is just connected to a basic switch, no DMZ setting. Both local and remote PCs only have IPv4 and IPv6.
– Luke Quinane
Sep 2 '10 at 1:16
add a comment |
up vote
0
down vote
From this thread, http://www.techzonez.com/forums/archive/index.php/t-9868.html, it sounds like you may have your Vista computer setup in the router as the DMZ. Other suggestions are to delete any network protocols except the basics to see if that fixes it.
Hope this helps
the remote computer is just connected to a basic switch, no DMZ setting. Both local and remote PCs only have IPv4 and IPv6.
– Luke Quinane
Sep 2 '10 at 1:16
add a comment |
up vote
0
down vote
up vote
0
down vote
From this thread, http://www.techzonez.com/forums/archive/index.php/t-9868.html, it sounds like you may have your Vista computer setup in the router as the DMZ. Other suggestions are to delete any network protocols except the basics to see if that fixes it.
Hope this helps
From this thread, http://www.techzonez.com/forums/archive/index.php/t-9868.html, it sounds like you may have your Vista computer setup in the router as the DMZ. Other suggestions are to delete any network protocols except the basics to see if that fixes it.
Hope this helps
answered Sep 2 '10 at 0:13
wbeard52
2,71822238
2,71822238
the remote computer is just connected to a basic switch, no DMZ setting. Both local and remote PCs only have IPv4 and IPv6.
– Luke Quinane
Sep 2 '10 at 1:16
add a comment |
the remote computer is just connected to a basic switch, no DMZ setting. Both local and remote PCs only have IPv4 and IPv6.
– Luke Quinane
Sep 2 '10 at 1:16
the remote computer is just connected to a basic switch, no DMZ setting. Both local and remote PCs only have IPv4 and IPv6.
– Luke Quinane
Sep 2 '10 at 1:16
the remote computer is just connected to a basic switch, no DMZ setting. Both local and remote PCs only have IPv4 and IPv6.
– Luke Quinane
Sep 2 '10 at 1:16
add a comment |
up vote
0
down vote
These answers are not correct, you can fix this by Simply uninstalling the Link-Layer Topology (Mapper I/O Driver and Responder) protocols, as well as the QoS Packet Scheduler service (you can add them back again afterwards) in the Local Area Connection of the client machine (not the server/target). You must uninstall, not simply remove the checkmark next to the protocol or service.
1
Anything to back that up?
– Canadian Luke
Jul 31 '13 at 22:25
I am not the one who answered but I found the reference here from a comment made by "Garth Rautenbach": social.technet.microsoft.com/Forums/windowsserver/en-US/…
– wandersick
Sep 15 '17 at 6:48
add a comment |
up vote
0
down vote
These answers are not correct, you can fix this by Simply uninstalling the Link-Layer Topology (Mapper I/O Driver and Responder) protocols, as well as the QoS Packet Scheduler service (you can add them back again afterwards) in the Local Area Connection of the client machine (not the server/target). You must uninstall, not simply remove the checkmark next to the protocol or service.
1
Anything to back that up?
– Canadian Luke
Jul 31 '13 at 22:25
I am not the one who answered but I found the reference here from a comment made by "Garth Rautenbach": social.technet.microsoft.com/Forums/windowsserver/en-US/…
– wandersick
Sep 15 '17 at 6:48
add a comment |
up vote
0
down vote
up vote
0
down vote
These answers are not correct, you can fix this by Simply uninstalling the Link-Layer Topology (Mapper I/O Driver and Responder) protocols, as well as the QoS Packet Scheduler service (you can add them back again afterwards) in the Local Area Connection of the client machine (not the server/target). You must uninstall, not simply remove the checkmark next to the protocol or service.
These answers are not correct, you can fix this by Simply uninstalling the Link-Layer Topology (Mapper I/O Driver and Responder) protocols, as well as the QoS Packet Scheduler service (you can add them back again afterwards) in the Local Area Connection of the client machine (not the server/target). You must uninstall, not simply remove the checkmark next to the protocol or service.
answered Jul 31 '13 at 21:45
Nightdiver
1
1
1
Anything to back that up?
– Canadian Luke
Jul 31 '13 at 22:25
I am not the one who answered but I found the reference here from a comment made by "Garth Rautenbach": social.technet.microsoft.com/Forums/windowsserver/en-US/…
– wandersick
Sep 15 '17 at 6:48
add a comment |
1
Anything to back that up?
– Canadian Luke
Jul 31 '13 at 22:25
I am not the one who answered but I found the reference here from a comment made by "Garth Rautenbach": social.technet.microsoft.com/Forums/windowsserver/en-US/…
– wandersick
Sep 15 '17 at 6:48
1
1
Anything to back that up?
– Canadian Luke
Jul 31 '13 at 22:25
Anything to back that up?
– Canadian Luke
Jul 31 '13 at 22:25
I am not the one who answered but I found the reference here from a comment made by "Garth Rautenbach": social.technet.microsoft.com/Forums/windowsserver/en-US/…
– wandersick
Sep 15 '17 at 6:48
I am not the one who answered but I found the reference here from a comment made by "Garth Rautenbach": social.technet.microsoft.com/Forums/windowsserver/en-US/…
– wandersick
Sep 15 '17 at 6:48
add a comment |
up vote
0
down vote
My issue was resolved by starting the Link-Layer Topology service. It was previously set to Manual and was not started after I had reinstalled Windows 7.
2
Welcome to SuperUser. Your answer would be even better if you edit it to provide some explanation as to why your solution addresses the OPs question.
– Twisty Impersonator
Dec 17 '14 at 21:05
add a comment |
up vote
0
down vote
My issue was resolved by starting the Link-Layer Topology service. It was previously set to Manual and was not started after I had reinstalled Windows 7.
2
Welcome to SuperUser. Your answer would be even better if you edit it to provide some explanation as to why your solution addresses the OPs question.
– Twisty Impersonator
Dec 17 '14 at 21:05
add a comment |
up vote
0
down vote
up vote
0
down vote
My issue was resolved by starting the Link-Layer Topology service. It was previously set to Manual and was not started after I had reinstalled Windows 7.
My issue was resolved by starting the Link-Layer Topology service. It was previously set to Manual and was not started after I had reinstalled Windows 7.
answered Dec 17 '14 at 21:02
Jaszucs
1
1
2
Welcome to SuperUser. Your answer would be even better if you edit it to provide some explanation as to why your solution addresses the OPs question.
– Twisty Impersonator
Dec 17 '14 at 21:05
add a comment |
2
Welcome to SuperUser. Your answer would be even better if you edit it to provide some explanation as to why your solution addresses the OPs question.
– Twisty Impersonator
Dec 17 '14 at 21:05
2
2
Welcome to SuperUser. Your answer would be even better if you edit it to provide some explanation as to why your solution addresses the OPs question.
– Twisty Impersonator
Dec 17 '14 at 21:05
Welcome to SuperUser. Your answer would be even better if you edit it to provide some explanation as to why your solution addresses the OPs question.
– Twisty Impersonator
Dec 17 '14 at 21:05
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f183661%2fremote-desktop-dropouts-because-of-an-error-in-data-encryption-this-session-w%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
Are the two machines on the same LAN or are you connecting across a router, the Internet, etc?
– boot13
Sep 2 '10 at 1:26
@boot13 The connection is via a VPN over the Internet.
– Luke Quinane
Sep 2 '10 at 1:40
Ah. Which VPN client are you using? You might want to read any documentation you can find on that client, looking for notes on using RDP. You could also use it to narrow down your search. Anyway, from what I've seen so far, this is one of those weird problems that a few people are having but nobody knows how to resolve (+1).
– boot13
Sep 2 '10 at 5:22