Questions

RDP issues when connecting to a laptop that has two connections active

+
0 Votes
Locked

RDP issues when connecting to a laptop that has two connections active

brian
Hey all,

We are currently rolling out Win7 in a large environment (40,000 computers). Some of our staff regularly use RDP to connect to their work computer from home. They will connect the enterprise via VPN then RDP to their work computer.

Some users have laptops in docking stations as their work computer. Prior to the upgrade to Win7 we used the Lenovo ThinkVantage tool to configure/mange wireless connectivity and we never had an issue with RDP.

With Win7 we are running into connectivity issues when the work computer has both an ethernet AND a wireless connection live at the same time. The user will either not be able to connect to the work computer at all or they will connect then after a few minutes lose connectivity to their work computer. One thing they have found is that if the call the help desk, the help desk can't even see the computer on the network; no ping by IP or host name.

We are leaning toward this being an issue with having two live connections at the same time but aren't sure of the best approach for resolving it. We don't want to have our user to have to jump through a bunch of hoops every time they dock/undock their work computer, which they will do from time to time for meetings and such. As I said, we never had this issue in XP and using ThinkVantage.

We have also found that some of our desktops that use Cisco Aironet adapters will lose their authentication from the network and when a user tries to log into the computer, they get a message that says, "No logon servers are available". The only way to resolve that is to hardwire the computer to our LAN, then it's good for awhile but may happen again, with the same username/password.

We are using Cisco WAP's and WPA-2 Enterprise encryption. Any help would be greatly appreciated.
+
0 Votes
gdeangelis
Collapse -

You are right on with your diagnosis. One host, 2 ip addresses, two routes back to their destination, or one route and a black hole route.

I guess the question will come down to if they really need both on all the time. I would consider your average user and if they can turn on the wireless when they leave for a meeting? Or, can they just use wireless all the time? You can probably do something with a hardware profile for wired and wireless, but it may be simpler to have them just turn on wireless when they need it. That will depend on your users. The logon issue mentioned under wireless can be easily dealt with. But, you may need to do some digging to get it right. The old cisco cards are a little quirky with the new wireless ap's, and we've found most on-board cards work just fine, but the initial log on may require a cabled connection and from there the cached logon will take care of things. Hope this helps.