no "Remote" tab on system properties window after upgrade to XP Pro

  • Thread starter Thread starter Michael
  • Start date Start date
M

Michael

Greetings!

I have upgraded from Win2k to WinXP Pro; mostly this was
done to get the Remote Desktop services. However, the
instructions for enabling the workstation for remote access
say to select the "Remote" tab on system properties window.
Unfortunately, there isn't one! I have tried installing
just Remote Desktop service from the DVD, but the install
tells me that I already have it as part of my OS. Help!

Thanks,
Michael
 
From a reply by Jeffrey Randow, MS-MVP, back on January 3, 2002, to a similar question...

*************************************

From an earlier MS Post:

Do you have a REMOTEPG.DLL file in your SYSTEM32 directory? If so, try reregistering it.

regsvr32 remotepg.dll

*************************************
 
I have it, and have tried re-registering it. However, I
also just noticed that even though the DVD that I got
with my MSDN subcription says "Windows XP Professional
with Service Pack 1", and the install *said* it was
installing WinXP Pro... but the General tab of the System
Properties window tells me that I am running "Windows XP
Media Center Edition"! I now presume that is the
problem; but if the MSDN DVDs don't work... how *do* I
get the Pro version installed???
-----Original Message-----
From a reply by Jeffrey Randow, MS-MVP, back on January
3, 2002, to a similar question...
*************************************

From an earlier MS Post:

Do you have a REMOTEPG.DLL file in your SYSTEM32
directory? If so, try reregistering it.
 
I would presume that XP Media Center Edition should still have the Remote Tab simply because you
enable/disable Remote Assistance via that tab, in addition to Remote Desktop on the Pro edition.
Remote Assistance should be available in all versions of XP with the possible exception of the 64
bit version. I know Remote Assistance is definitely available in XP Pro and Home editions.

I would try a repair install and see if that works...

http://michaelstevenstech.com/XPrepairinstall.htm

Otherwise, you may need to get an XP Pro Upgrade CD (at your friendly local retailer or other
source) and either install over the existing installation or do a clean install. The later
suggestion is my personal choice...
 
RD is available in MCE since MCE uses Windows XP Pro...

Jeffrey Randow (Windows MVP - Networking & Smart Display)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Wiki -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Given what everybody else has said, and what you've spotted, I would
reinstall over the current install.

i.e. do a "repair install" of the OS over itself.

I suspect this will fix it. If SP1 really isn't there, I'd put it, and all
the other critical patches, etc, in ASAP.
 
Well... I have done the repair install and I now have a
Remote tab... however; I still can't connect from a
remote computer. Terminal services seem to be hosed, and
nothing seems to be repairing it. Sigh... I am about to
just go to a clean install and then reinstall all my apps.
-----Original Message-----
I would presume that XP Media Center Edition should
still have the Remote Tab simply because you
enable/disable Remote Assistance via that tab, in
addition to Remote Desktop on the Pro edition.
Remote Assistance should be available in all versions of
XP with the possible exception of the 64
bit version. I know Remote Assistance is definitely
available in XP Pro and Home editions.
I would try a repair install and see if that works...

http://michaelstevenstech.com/XPrepairinstall.htm

Otherwise, you may need to get an XP Pro Upgrade CD (at
your friendly local retailer or other
source) and either install over the existing
installation or do a clean install. The later
 
Any chance you can test with a local connection--this will remove a number
of vagaries that you might not have quite right in terms of a remote
connection?

If possible, test on a local LAN, just to eliminate addressing and
router/nat/firewall issues involved in a remote connection.
 
Back
Top