Wireless shuts down after RDP on Windows 7?

1

I have two Laptops with windows 7 installed. They are both on the same wireless network. There is no wired connection. Machine A is able to ping Machine B. I then initiate a RDP connection from A to B and receive a logon prompt. I enter my credentials and then it looks as though the desktop is being readied... but the desktop never shows up and then the session hangs until I am prompted with an error stating that "The Connection to the Remote Computer was Lost"

At this time Machine A is no longer able to ping B. So I log into machine B the old fashioned way and can briefly see that the wireless connection was in a failed state, and then it comes back up and I am able to ping B from A once again.

However, as soon as I try to RDP to B, this process is repeated.

In the System EventLog I see

Event ID: 56

Source: TermDD

Message: "The Terminal Server security layer detected an error in the protocal stream and has disconnected the client."

Anybody have a solution for this?

MattUebel

Posted 2010-12-13T21:52:50.810

Reputation: 1 443

I bet you have problems copying files between the machines over the wireless network too? what kind of wireless AP/router are you using? and what about the machines connecting to it? – Matt H – 2010-12-13T23:02:50.097

Answers

0

This happens if there are problems with the network. Those problems could be duplex mismatching or bad NIC drivers.

Just to troubleshoot, if you use a crossover cable and just link them together do you get the same error? If not, you'd cut out RDP/authentication causing the issue and can then move to the network.

Chris Harrod

Posted 2010-12-13T21:52:50.810

Reputation: 269

Asked: 2010-12-13T21:52:50.810

Viewed: 1 341 times

Active: 2010-12-13T22:59:48.040