HOME domain/workgroup does not contain any Terminal Servers

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RJ - 08 Mar 2008 22:35 GMT

Hi,
I'm running several XP pro systems and have had remote desktop running for
several years until recently. I recently did a "XP tweak" and am now not
able to see any PCs when browsing for available computers through the remote
desktop client.

I believe I disabled something related to active directory services or
something. If anyone can help me get back to where I was, it would be
greatly appreciated.

Thx!
--RJ

Reply to this Message

RJ - 09 Mar 2008 01:03 GMT

to be more specific...
Remote Desktop is able to connect to another system but only by using the
other systems IP address. It is no longer able to connect by using the
computer name as it used to. I'm not sure what has changed.

Any suggestions or advice will be greatly appreciated.

Thx.
--RJ

> Hi,
> I'm running several XP pro systems and have had remote desktop running for
[quoted text clipped - 8 lines]
> Thx!
> --RJ

Reply to this Message

Sooner Al [MVP] - 09 Mar 2008 12:43 GMT

> to be more specific...
> Remote Desktop is able to connect to another system but only by using the
[quoted text clipped - 18 lines]
>> Thx!
>> --RJ

Are you in a enterprise domain environment or home workgroup environment?
Normally you can't browse for other terminal servers/Remote Desktop hosts if
your in a workgroup environment without performing this registry tweak.

READ THESE TWO KB ARTICLES FIRST!!!!!

http://support.microsoft.com/default.aspx?scid=kb;EN-US;256986
http://support.microsoft.com/default.aspx?scid=kb;EN-US;322756

The hack...

http://support.microsoft.com/default.aspx?scid=kb;en-us;281307

Signature

Al Jarvi (MS-MVP Windows - Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

Reply to this Message

RJ - 09 Mar 2008 18:18 GMT

>> to be more specific...
>> Remote Desktop is able to connect to another system but only by using the
[quoted text clipped - 31 lines]
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;281307

Hi Al,
I appreciate your response. My network is a home workgroup environment. In
the past I've always been able to enter the remote computer's name in the
Remote Desktop Client (RDC). Now I must enter the remote computer's IP
address.

I did some trouble-shooting by pinging the Host PC by computer name from the
Host PC and from the Client PC and am seeing different NetID and SubmaskIds
returned! I ping using the actual IP address all look fine. I've upgraded to
ZA 2007 a few weeks ago so maybe this has something to do with this.
Something very stange is going on. This may explain why I must enter the
actual IP address as opposed to the computer name.

Anyway, I can email you more details if you are interested. Again, your
pointers are appreciated. Very useful information.

--Rj

Reply to this Message

Sooner Al [MVP] - 10 Mar 2008 12:13 GMT

>>> to be more specific...
>>> Remote Desktop is able to connect to another system but only by using
[quoted text clipped - 50 lines]
>
> --Rj

You might consider either totally removing ZA 2007 as a test and/or falling
back to a restore point made prior to installing ZA to see if that fixes the
issue.

Signature

Reply to this Message

RJ - 15 Mar 2008 20:41 GMT

>>>> to be more specific...
>>>> Remote Desktop is able to connect to another system but only by using
[quoted text clipped - 54 lines]
> falling back to a restore point made prior to installing ZA to see if that
> fixes the issue.

Good suggestions. I removed ZA and tried an older restore point on one of
the PCs but still seeing this strange behavior in terms of IP address. I
have a few more things to try. Will keep you posted.

--Rj

Reply to this Message