Remote Desktop unavailable on lan after connecting to wireless?

[Guest Xiata]

So I am trying to manage my system and a wireless router using a remote

desktop connection only to find that when I try to connect to any wireless

network Remote Desktop immediately forgets what interface it was started on

and refuses to accept new remote desktop requests until the wireless host it

was connecting to forcefully disconnects it (via unplugging, or other means).

 

Why does Remote Desktop forget what interface it is on and immediately bind

to the WLAN interface? I have configured windows to give preference to LAN

connections over WLAN connections (Network Connections -> Advanced Settings),

and there is no indication that the original LAN connection has been dropped

since all my other services are running as to be expected.

 

Because this machine does not have a videocard (waiting for RMA return) I

have managed this machine through Remote Desktop and this bug, yes bug- there

is no reason why it is terminating all connections to the non-affected LAN

interface, is making it impossible for me to manage my wireless router which

lost its configuration after a firmware reflash.

 

STEPS TO REPRODUCE:

1. Disconnect from wireless if used and connect to LAN via ethernet.

2. Set priority to LAN device over WLAN device in Advanced Settings in

Manage Network Connections (Advanced menubar -> Advanced Settings (hit alt if

necessary to make menubar visible)).

3. Remote into machine using Remote Desktop (TSClient v6).

4. Start -> Connect to. Choose any access point Windows may not recognize.

[if you can only remote in, make sure it is an AP you can turn off]

5. Wait until windows attempts to connect. You will notice Remote Desktop

has lost its connection after about 30 seconds.

6. Ping the machine or access any other service running on it. It should

still be responsive on the LAN interface (as it has not been disconnected).

7. Attempt to reconnect using Remote Desktop over LAN. It should not connect

to that machine at this point.

8. Turn off Access Point you control. Attempt to use Remote desktop to the

machine that was unresponsive over LAN. It will connect now.

 

Expected Behavior:

Wireless device connects without interrupting and denying Remote Desktop

session.

 

Experienced Behavior:

As long as wireless device is connected, Remote Desktop becomes unavailable

until wireless device has been disconnected or disabled.

 

System:

Windows Vista Business, fully patched.

LAN [nForce4 Ethernet [ven/dev: 0x10DE/0x0038]: nForce 15.00 driver]

WLAN [Linksys Wireless-G PCI [ven/dev: 0x1814/0x0301]: Windows WHQL driver

2.0.3.0]

 

Note: This system does not currently have a videocard and can only be

accessed via remote desktop.