You must be running Terminal Server on the host machine (which is built in to XP Pro, 2K Advanced Server, 2K Server (was there such a thing???), and NT 4. There are alternatives, however. You can head over to AT&T [link]www.uk.research.att.com/vnc/[/link] <--There and download and install VNC (Virtual Networked Computer) on both machines and remote control a Win95/98/me/nt 4/2k/xp/linux/unix/mac/whatever from any of the same =) It's relatively fast, easy to set up, and gets the job done!!
Instant and "easy" dial support mainly, that would be why you would see it in general. Then, these same users would use it on the LAN. Plus, it has integrated support for user permissions in NT by attaching a filter to the GINA.DLL file, but unfortunately that method is sensitive to revision levels and service packs (ever hear about the BSODs at logon in Win2K with v9.0/1? That's why).
I have never used VNC myself, but I love Terminal Services since you can run multiple concurrent sessions on the same box, and it's pretty quick as well.
Welcome to OSNN Wardell - I am not aware of SP2 issues with remote desktop, but I DO know that VPN has been affected and so it would not surprise me if this were too. I am not sure if you have tried it yet, but perhaps a search or two of the forums may also prove fruitful?
On a side-note you will not need to reinstall your O/S - if it is an SP2 issue you can just go to the restore point before SP2 or even remove SP2 I think from ADD/REMOVE programs selection.
Perhaps someone else here knows about this - I do know plenty folks here use remote desktop and I am guessing many of them will have SP2 on also!
I found that when I beta tested SP2, I constantly sent emails to Microsoft about Remote Desktop not working when the SP2 firewall was turned on (even though it was set to allow connections through it). Now, I had this problem up until the actual RTM release so I'm willing to bet that it may still be a problem. Try turning OFF the Windows XP firewall and see if your remote desktop connection works.
Setting up Remote Desktop Web ConnectionRemote Desktop Web Connection is an optional World Wide Web Service component of Internet Information Services, which is included by default in Windows XP Professional and Windows 2000. Remote Desktop Web Connection is not installed by default, but must be installed using Add or Remove Programs.
When you install Remote Desktop Web Connection, the files are copied by default to the %systemroot%\Web\Tsweb directory of your webserver. The included sample default.htm and connect.asp page can be used as is, or you can modify them to meet the needs of your application.
On the client side, Remote Desktop Web Connection requires that the computer have a TCP/IP connection to the Internet or network, and be running Microsoft Internet Explorer 4.0 or higher.
For more information, see:
To install Remote Desktop Web Connection.
To connect to another computer using Remote Desktop Web Connection.
For information on customizing Remote Desktop Web Connection, see the Microsoft Platform SDK.