Can't Connect Windows XP SP3 via Remote Desktop Connection

[Cheongseo]

I've got a Dell OptiPlex 760 with Windows XP /SP3, but Remote Desktop
Connection doesn't work although it is enabled and allowed on Firewall.
Once it is disabled, Remode Desktop Connection from another Windows XP show
that it could not connect the computer. When it is enabled, there is no erro
messge but just doesn't work.

Any advices will be appreciated.

 

[PA Bear [MS MVP]]

You cannot connect to a remote computer or start a remote application when
you use Terminal Services Web Access or Remote Web Workspace on a Windows XP
SP3-based computer:
http://support.microsoft.com/kb/951607

 

[Cheongseo]

Thanks for your reply, but I think I should be more clear on this.
I am trying to access a Windowx XP computer with SP3 but it won't work while
there is no problem accrssing other computers from the Windowx XP computer
with SP3.
Basically, the new Windowx XP computer with SP3 won't let other computers
access via Remote Desktop Connection
Is there something I can do to make it work?

 

[R. McCarty]

Did you check the PC to ensure that Remote Desktop sessions are
enabled ? Also that the Firewall has the correct Exceptions to allow
the data traffic for RD. Finally that the Services needed for Terminal
Services are set to the proper Start mode and running ? Since this is
a new XP machine could you have any trial version security software
operating that is not setup for RD ?

 

[Cheongseo]

Thanks for your comment, but everything is done properly. In additino, there
is no security software installed yet.
Any suggestions?

 

[R. McCarty]

Try a remote desktop from another member of your LAN. Otherwise
I'd spend some time checking Services.

 

[Pegasus [MVP]]

I've got a Dell OptiPlex 760 with Windows XP /SP3, but Remote Desktop
Connection doesn't work although it is enabled and allowed on Firewall.
Once it is disabled, Remode Desktop Connection from another Windows XP
show
that it could not connect the computer. When it is enabled, there is no
erro
messge but just doesn't work.

Any advices will be appreciated.

- What OS does the host PC run - WinXP Home or WinXP Professional?
- Is the host PC on the same internal network as the PC that starts the
Remote Desktop session or are you doing it via the Internet?

 

[Cheongseo]

I tried it from more than 4 computers (Windows XP and Windows 2003 server)
but none of them worked. Yeah, everything is in the same network.

 

[Cheongseo]

It is Windows XP Professional with SP3 and everything I have tested is on the
same network (not RWW or from Internet). I tried it from 3 different Windows
XP Pro computers, a Windows 2003 Server and a Windows 2008 server. But I
wasn't able to get connected.

I may reinstall the whole things from scratch instead of wasting more time.

 

[Cheongseo]

OK..
Now I found what was causing it after reinstall the whole thing from scratch.

It starts after installing .NET 3. and as soon as I remove it and reboot, it
works fine.

I reinstalled everything from scratch and installed all the applications. It
worked great. After I checked the applications don't affect, I installed
Windows Updates. After the reboot, Remote Desktop Connection to the client XP
maching stop working.
I removed after uninstalling .NET 3.5. and .NET 3 with SP1.
I don't know what is wrong on the NET 3.5, but it caused the issue.
I've seen many people complaining on the same issue but don't know Microsoft
is listening to them.

 

[Shenan Stanley]

This is exactly the same problem i have had. I uninstalled .Net 3
sp1 & sp2 and the ability to use RDC to connect to this machine was
restored.

You replied to nothing... How about quoting something from the proevious
conversation next time...

What you see above is what everyone using the newsgroups will see...

What you probably thought they saw (or something like it):
http://www.howtofixcomputers.com/fo...sp3-via-remote-desktop-connection-241571.html

Ain't the internet and replication of content grand?

 

[VanguardLH]

You replied to nothing... How about quoting something from the proevious
conversation next time...

Google Groups copy of old thread: http://preview.tinyurl.com/ybsd7mx

undisclosed didn't divulge anything different than the OP already claimed
solved his problem. So undisclosed just spewed out a "me too" post.

"undisclosed" has been replying to many ancient threads. The thread to
which he/she replied was */6 months old/*. It's possible that "undisclosed"
it a generic username (also evidenced by the "rickaffeldt" signature) used
for all posts submitted through a forum-to-Usenet gateway used by the
pretend forum or to provide a webnews-for-boobs interface for
Usenet-ignorant users.

For "undisclosed":

X-Newsreader: vBulletin USENET gateway
X-Originating-IP: 66.133.117.3

So you have a boob using a webnews-for-dummies gateway to Usenet. This
pretend forum doesn't even bother to add a header to identify itself or a
signature to show a link to the old thread.