Terminal Services Manager and Windows XP SP2

[Yogi]

Previous to Service Pack 2 being released for Windows XP, I used
Terminal Services Manager a Windows 2003 Server to remote control the
XP machines in the office. I could use "Connect to Computer" to
connect to any XP computer that had remote desktop enabled and be able
to see the user logged into the console session. I could then use
"Remote Control" to take control of the user. I now cannot connect
using Terminal Services Manager to any of the XP machines that have
been updated with SP2. I get the error "You could not be authenticated
on this server" if I attempt to connect to any of the XP machines that
I have listed in the "Favorite servers" area of Terminal Services
Manager or the error "Could not find server" if I'm trying to connect
to a new XP SP2 computer that isn't already listed. I can connect fine
to the computers that still have XP SP2 on them. I have tried
disabling the Windows Firewall that is enabled by default in XP SP2,
but it doesn't correct the problem. Any suggestions on how to get this
setup working again would be greatly appreciated.

Thank you,
Yogi

 

[Mike Monaghan]

Hello Yogi,

This might be related to the Windows XP Firewall. Check if the firewall
is enabled on an XP SP 2 machine. If it is, you can either create an exception
to allow RDP protocol in or disable the firewall. For help, on your XP SP2
machine open "Help and Support" and search for "opening ports in windows
firewall" or "disable windows firewall". RDP is TCP Port # 3389.

Hope this helps,

Mike

 

[Yogi]

Hello Yogi,

This might be related to the Windows XP Firewall. Check if the firewall
is enabled on an XP SP 2 machine. If it is, you can either create an exception
to allow RDP protocol in or disable the firewall. For help, on your XP SP2
machine open "Help and Support" and search for "opening ports in windows
firewall" or "disable windows firewall". RDP is TCP Port # 3389.

Hope this helps,

Mike

Mike,

The firewall is open for port 3389 and I can use Remote Desktop to
login to any of the XP computers just fine. I just cannot use Terminal
Services Manager from the Adminpak to connect to any of the XP
computers with SP2 installed. I have tried disabling the firewall
completely, but it doesn't help.

Thanks,
Yogi

 

[Jim Reid]

Previous to Service Pack 2 being released for Windows XP, I used
Terminal Services Manager a Windows 2003 Server to remote control the
XP machines in the office. I could use "Connect to Computer" to
connect to any XP computer that had remote desktop enabled and be able
to see the user logged into the console session. I could then use
"Remote Control" to take control of the user. I now cannot connect
using Terminal Services Manager to any of the XP machines that have
been updated with SP2. I get the error "You could not be authenticated
on this server" if I attempt to connect to any of the XP machines that
I have listed in the "Favorite servers" area of Terminal Services
Manager or the error "Could not find server" if I'm trying to connect
to a new XP SP2 computer that isn't already listed. I can connect fine
to the computers that still have XP SP2 on them. I have tried
disabling the Windows Firewall that is enabled by default in XP SP2,
but it doesn't correct the problem. Any suggestions on how to get this
setup working again would be greatly appreciated.

Thank you,
Yogi

I have this same exact issue. I have the Windows Firewall disabled for
all domain clients using Group Policy. I can use Remote Desktop to
connect to any of the computers, I just can't use Terminal Services
Manager to shadow the console user like I used to before SP2. I'm
thinking about installing VNC on all the client computers to control
the console session, but I would prefer not to have to install another
remote application when Terminal Services Manager in conjunction with
WindowsXP worked so well prior to SP2. Anybody have an answer?

Thanks,
Jim Reid