L
lurknomo
I had the same problem trying to establish a remote desktop connection
using either a Viewsonic Smart Display, a Compaq x1000 laptop, or an
HP iPAQ to my workstation, which recently had SP2 installed.
I contacted MS support, and after a fairly lengthy runaround, the
tech, named Raj, suggested using the workstation's IP address in the
field usually reserved for the computer's name in the Remote Desktop
Connection setup.
Upon hitting the enter key, the laptop connected to the workstation
just like old times.
I tried the same approach with my Smart Display. Replacing the
workstation's name with its IP Addy solved the problem.
Ditto for the Pocket PC.
I have give Raj his props, this was a really simple suggestion, but I
certainly would not have thought of it.
I'm not a Windows expert, but this may indicate that SP2 somehow
impacted the DNS services or some driver it depends on. Raj did some
research regarding this, but turned up nothing. I asked to keep the
case number open, because for those of us using DHCP, this could be an
inconvenient work around.
Anyway, I hope this will help others get up and running.
using either a Viewsonic Smart Display, a Compaq x1000 laptop, or an
HP iPAQ to my workstation, which recently had SP2 installed.
I contacted MS support, and after a fairly lengthy runaround, the
tech, named Raj, suggested using the workstation's IP address in the
field usually reserved for the computer's name in the Remote Desktop
Connection setup.
Upon hitting the enter key, the laptop connected to the workstation
just like old times.
I tried the same approach with my Smart Display. Replacing the
workstation's name with its IP Addy solved the problem.
Ditto for the Pocket PC.
I have give Raj his props, this was a really simple suggestion, but I
certainly would not have thought of it.
I'm not a Windows expert, but this may indicate that SP2 somehow
impacted the DNS services or some driver it depends on. Raj did some
research regarding this, but turned up nothing. I asked to keep the
case number open, because for those of us using DHCP, this could be an
inconvenient work around.
Anyway, I hope this will help others get up and running.