Solved Wireless LAN disconnects just after successful RDP connection

[pjwsax]

I've seen a few threads about similar problems, but nothing precisely the same and nothing I've found solves my issue. I've got a laptop (Toshiba Satellite) running Windows 7 Professional (64-bit). I'm trying to connect to the laptop from another machine via RDP, but the connection dies every time. This is what happens:

1) I log into the laptop, which then connects to the wireless network.
2) I initiate the RDP connection from the other machine.
3) The connection is successfully made, I see the "Welcome" window, then the RDP screen goes black. At the same time (just as the screen goes back on the RDP client), the screen on my laptop locks (goes back to the login screen) and the network monitor icon ("Toshiba Wireless LAN Indicator") shows that the wireless connection is down - no network connection available.
5) After a few seconds (15 to 20) I get a message on the client that the connection couldn't be made.

From this I'm gathering that my firewall is set up to allow incoming connections properly (I also verified this manually) and I can see that the initial connection is being made. My best guess is that the wireless connection is being killed when the RDP session is started.

Is there a way to prevent the network connection from being reset (or whatever's happening) when connecting via RDP?

I've noticed that my laptop doesn't connect to wifi until after I've logged in. Is this the likely culprit? If so, is there a way to change this so the computer will connect to the wireless network before I've actually logged in?

For what it's worth, I get the same behavior regardless of the client machine being used (Win 7 Enterprise, Win 7 Home Premium, Linux, etc.).

Any help would be greatly appreciated!

-Peter

 

[pjwsax]

Murphy's Law is alive and well. Not even an hour after posting this thread I found the answer myself. The issue was that my network connection was set to be available to myself only. Apparently this is the default setting, so I deleted and manually recreated the network connection so it's now available to all users and my RDP connection is just fine!

To give credit where credit is due, here's where I found the answer:

Wireless before Login

Hopefully this will help someone else in the future.

 

[Schoutens1]

Thank you so much!

I was chasing everything! I checked everything I knew to check - nothing. Then, I saw this post. That was the problem - wifi profile restricted to 'Me Only.' WTF? Oh well.

Thanks again.

 

[eaglesupport]

My WIFI profile is on "ALL USERS" and I have this issue can anyone help ?

 

[i3v]

I also experience the same problem, and I also have "all users" text already.
Few additional details, to be more specific:

1. in addition to "all users" text, there's also a large note "some network settings are managed by your company" (or something like this)
2. I'm able to login to other PCs within this domain and running the same version of windows without any problems.

 

[softpro]

Steps to fix it

1. Connect pc to network with cable
2. Logoff
3. Connect to the pc using RDP from another computer
4. In DOS prompt
execute
netsh wlan show profiles

netsh wlan delete profile name="ProfileName"

this will force wifi profile to ask for the password

5. Go to Adapter Settings
6. Right Click on the wifi adapter -click on connect
7. Select the WIFI router -- click connect
8. Type the wifi password
9. After successful connection from wifi - disonect from RDP
10. Disconect the pc from the cable
11. No connect back with RDP from the remote computer - and it wifi use wifi connectin without any problems

This is because the wifi profile saves the wifi password but only for the locally connected user. It does not have the password saved as remote user

 

[khaizaz]

Hey Softpro, your trick fix the issue for me. But what I have noticed that whenever the laptop gets a new IP from the AP, I have to perform the same steps to make it work. Do you think there could be a perminent fix?