Remote Desktop Connection - Revisited

[Jethro]

Here I am again - in a learning mode. I still can't get XP's 'remote
desktop' to work completely.

As I said earlier, I have two machines, both with XP PRO SP2 - one is
conveniently named 'left' and the other named right' because that is
where they are in front of me. Both have the same password-protected
user (me) with the same password. 'My Network Places' on both
machines show what they should - the two machines in the Workgroup
'MSHOME'. I can access and change most files on either machine from
the other machine by using Windows Explorer.

Okay then - when I try to use remote desktop connection, it will work
one way but not the other. I am wondering why?

On LEFT machine, it displays machine RIGHT for me to connect to, but
when I select 'connect', it does not ask me for RIGHT machine's login
and password. That surprises me. I figure it should ask me for a
login and password, but it does not. However, it correctly shows
RIGHT machine on LEFT machine's screen immediately.

Going the other way, things act differently. On RIGHT machine, it
displays machine LEFT for me to connect to, and when I select
'connect', it does ask me for LEFT machine's login and password.
I thought that to be correct. However, then I get an error window
that states 'This machine cannot connect to the remote computer'.

So - I have to be missing something, Can anyone suggest anything?

Thanks

Jethro

 

[Pegasus \(MVP\)]

Here I am again - in a learning mode. I still can't get XP's 'remote
desktop' to work completely.

As I said earlier, I have two machines, both with XP PRO SP2 - one is
conveniently named 'left' and the other named right' because that is
where they are in front of me. Both have the same password-protected
user (me) with the same password. 'My Network Places' on both
machines show what they should - the two machines in the Workgroup
'MSHOME'. I can access and change most files on either machine from
the other machine by using Windows Explorer.

Okay then - when I try to use remote desktop connection, it will work
one way but not the other. I am wondering why?

On LEFT machine, it displays machine RIGHT for me to connect to, but
when I select 'connect', it does not ask me for RIGHT machine's login
and password. That surprises me. I figure it should ask me for a
login and password, but it does not. However, it correctly shows
RIGHT machine on LEFT machine's screen immediately.

Going the other way, things act differently. On RIGHT machine, it
displays machine LEFT for me to connect to, and when I select
'connect', it does ask me for LEFT machine's login and password.
I thought that to be correct. However, then I get an error window
that states 'This machine cannot connect to the remote computer'.

So - I have to be missing something, Can anyone suggest anything?

Thanks

Jethro

A couple of points:
- Make sure your machine-based firewalls are turned off while testing.
- You did not tell us what the underlying command is when you
try to establish a connection. To remove this uncertainty, use
this command while testing:
mstsc /v:LLL.LLL.LLL.LLL
where LLL.LLL.LLL.LLL is the IP address of LEFT.
You must, of course, enable Remote Desktop on Left and include
your account in the list of authorised Remote Desktop users, as
detailed in the printed guide you have in front of you.

 

[Sooner Al [MVP]]

Here I am again - in a learning mode. I still can't get XP's 'remote
desktop' to work completely.

As I said earlier, I have two machines, both with XP PRO SP2 - one is
conveniently named 'left' and the other named right' because that is
where they are in front of me. Both have the same password-protected
user (me) with the same password. 'My Network Places' on both
machines show what they should - the two machines in the Workgroup
'MSHOME'. I can access and change most files on either machine from
the other machine by using Windows Explorer.

Okay then - when I try to use remote desktop connection, it will work
one way but not the other. I am wondering why?

On LEFT machine, it displays machine RIGHT for me to connect to, but
when I select 'connect', it does not ask me for RIGHT machine's login
and password. That surprises me. I figure it should ask me for a
login and password, but it does not. However, it correctly shows
RIGHT machine on LEFT machine's screen immediately.

Going the other way, things act differently. On RIGHT machine, it
displays machine LEFT for me to connect to, and when I select
'connect', it does ask me for LEFT machine's login and password.
I thought that to be correct. However, then I get an error window
that states 'This machine cannot connect to the remote computer'.

So - I have to be missing something, Can anyone suggest anything?

Thanks

Jethro

What version of the Remote Desktop client are you running, ie. the new RDP 6
client or the older one? Make sure the client is configured like this...

http://theillustratednetwork.mvps.org/ScreenShots/XP/RDP6-XPClientSettings.jpg

Have you looked in the event logs on either machine to see if there are any
clues?

Are you using the computer name or IP to call? Are you using a hosts or
lmhosts file that may be mapping the computer name to a non-existent IP?
Have you tried deleting the connection history entries on each PC and
calling again?

http://support.microsoft.com/kb/312169/en-us

When trying to access RIGHT from LEFT do you just get a black screen, ie. no
login popup? If so I would make sure you have the latest video drivers
installed on each PC. Also make sure the Options -> Experience tab is set
correctly for the type of connection, ie. LAN, broadband, etc...

As far as LEFT from RIGHT I would recreate the password. Its possible your
password is not what you remember...

When you open the Remote Desktop connectoid try deleting any saved user
credentials and subsequently reenter them.

More troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

Please post Remote Desktop questions to the
microsoft.public.windowsxp.work_remotely news group...

--

Al Jarvi (MS-MVP Windows Networking)

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

 

[Jethro]

A couple of points:
- Make sure your machine-based firewalls are turned off while testing.

They both were (are).

- You did not tell us what the underlying command is when you
try to establish a connection.

I am not using a 'command' per se. I am using a desktop shortcut to
%SystemRoot%\system32\mstsc.exe that 'properties' says starts in
%HOMEDRIVE%%HOMEPATH%

To remove this uncertainty, use
this command while testing:
mstsc /v:LLL.LLL.LLL.LLL
where LLL.LLL.LLL.LLL is the IP address of LEFT.

I should have included the fact that I can 'ping' either machine from
the other just fine.

You must, of course, enable Remote Desktop on Left and include
your account in the list of authorised Remote Desktop users, as
detailed in the printed guide you have in front of you.

I'll have to check on this one.


Thanks

Jethro

 

[Pegasus \(MVP\)]

I am not using a 'command' per se. I am using a desktop shortcut to
%SystemRoot%\system32\mstsc.exe that 'properties' says starts in
%HOMEDRIVE%%HOMEPATH%

*** Fine. Now use the command below while testing!

 

[Jethro]

*** Fine. Now use the command below while testing!

Hiya

I had to cut the grass before it gets hot (predict 100 degrees!). So
I am just getting back to all this,

I tried the mstsc command and get the same results.
mstsc works as does remote desktop from LEFT machine to the RIGHT
machine. No surprise there. Both mstsc and remote desktop fail
identically (same error as stated earlier) from RIGHT machine to LEFT
machine.

I do notice that the LEFT machine does not ask for login/password,
whereas RIGHT machine does. But this is probably because LEFT to
RIGHT works and it remembered the login/password (I had checked the
box). Since RIGHT to LEFT has never worked, the login/password is not
remembered (until it does work I would guess).

As I said earlier, command line 'ping' works both ways just fine.
BTW - I did check correctness of the IP addresses with 'ipconfig'.

I hadn't said, but user name and password are the same on both
machines.

Jethro

 

[Jethro]

What version of the Remote Desktop client are you running, ie. the new RDP 6
client or the older one? Make sure the client is configured like this...

Boy I have no idea as to RDP version - 6 or whatever. How can I
determine that?
I do notice that LEFT machine has no 'advanced' tab under remote
desktop, whereas RIGHT machine does. Any idea why that would be?
Anyway, my settings agree with those at the URL below.

Another thing I notice - although both machines are set up with a
single user (me) and with the same password, LEFT machine asks me for
them at boot-up whereas RIGHT machine does not. I wonder why?

Thanks
Jethro

 

[Sooner Al [MVP]]

On Tue, 7 Aug 2007 07:14:11 -0500, "Sooner Al [MVP]"


Boy I have no idea as to RDP version - 6 or whatever. How can I
determine that?
I do notice that LEFT machine has no 'advanced' tab under remote
desktop, whereas RIGHT machine does. Any idea why that would be?
Anyway, my settings agree with those at the URL below.

Another thing I notice - although both machines are set up with a
single user (me) and with the same password, LEFT machine asks me for
them at boot-up whereas RIGHT machine does not. I wonder why?

Thanks
Jethro

The LEFT machine is running the older version while the RIGHT machine is
running RDP 6. You can open the Remote Desktop connectoid on each machine,
click on the small computer icon in the upper left corner and click "About"
to get the version.

Did you, or anyone, use Tweak UI to setup auto login on the RIGHT machine?

Getting back to the original issues did you look at the suggestions I made
earlier?

Are either of these PCs running anything like NAV or OneCare Live or
something similar that may be causing issues?

I presume both these PCs are on the same LAN and not remote from each other?
Perhaps if you describe your home network a bit that may also be of some
help...

--

Al Jarvi (MS-MVP Windows Networking)

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

 

[Pegasus \(MVP\)]

Hiya

I had to cut the grass before it gets hot (predict 100 degrees!). So
I am just getting back to all this,

I tried the mstsc command and get the same results.
mstsc works as does remote desktop from LEFT machine to the RIGHT
machine. No surprise there. Both mstsc and remote desktop fail
identically (same error as stated earlier) from RIGHT machine to LEFT
machine.

I do notice that the LEFT machine does not ask for login/password,
whereas RIGHT machine does. But this is probably because LEFT to
RIGHT works and it remembered the login/password (I had checked the
box). Since RIGHT to LEFT has never worked, the login/password is not
remembered (until it does work I would guess).

As I said earlier, command line 'ping' works both ways just fine.
BTW - I did check correctness of the IP addresses with 'ipconfig'.

I hadn't said, but user name and password are the same on both
machines.

Jethro

When you do not need to enter an account/password then these
credentials are stored in a hidden file xxxx.rdp. It could be anywhere
on your hard disk. This Remote Desktop profile file might hold
other details that interfere with your operation. Find out where it is,
then get rid of it! Note: You might have more than one of them.

 

[Jethro]

The LEFT machine is running the older version while the RIGHT machine is
running RDP 6. You can open the Remote Desktop connectoid on each machine,
click on the small computer icon in the upper left corner and click "About"
to get the version.

You are right again - LEFT machine is V5.1 while the RIGHT machine is
V6.0. I'll have to try to figure out how to get V6 back.

Did you, or anyone, use Tweak UI to setup auto login on the RIGHT machine?

I guess I might have - some time in the past. I don't remember. I
did have access to TweakUI a long time back - long gone now. I wonder
how I can undo this?

Getting back to the original issues did you look at the suggestions I made
earlier?

My apology - I missed these suggestions that you made:

Have you looked in the event logs on either machine to see if there are any
clues?

I went to event viewer and saw nothing meaningful - to me anyway. I
even repeated the failing remote connect to see if it made an entry in
any log, and I did not see any.

Are you using the computer name or IP to call?

I have tried both - same result.

Are you using a hosts or
lmhosts file that may be mapping the computer name to a non-existent IP?

I don't believe so.

Have you tried deleting the connection history entries on each PC and
calling again?

No, but I will......

http://support.microsoft.com/kb/312169/en-us

As the above URL shows, I deleted every MRUnumber on both machines,
and re-tried the connections. Same results. LEFT to RIGHT works -
RIGHT to LEFT fails. Interestingly, the registry on LEFT (that
worked) now has one MRU0 in its registry containing 'RIGHT'. The
registry on RIGHT has no MRU0 entries in its registry now.

When trying to access RIGHT from LEFT do you just get a black screen, ie. no
login popup?

No - just the error (failure) window.

If so I would make sure you have the latest video drivers
installed on each PC. Also make sure the Options -> Experience tab is set
correctly for the type of connection, ie. LAN, broadband, etc...

On LEFT (that works), it is set to LAN which I did a while back and I
guess it took since it works. On RIGHT (that fails), it is set to
MODEM which is wrong, but after I change it to LAN, the connection
still fails, after which the 'experience' is set back by XP to MODEM.

As far as LEFT from RIGHT I would recreate the password. Its possible your
password is not what you remember...

They are both the same, and verify to be correct.

When you open the Remote Desktop connectoid try deleting any saved user
credentials and subsequently reenter them.

Can U tell me how to do this please ???

More troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

Are either of these PCs running anything like NAV or OneCare Live or
something similar that may be causing issues?

No - I avoid Norton. I never heard of OneCare Live

I presume both these PCs are on the same LAN and not remote from each other?
Yes


Perhaps if you describe your home network a bit that may also be of some
help...

Two amd desktops wire-LAN'ed together via a D-Link router. Two
USB-connected printers on one machine - used by the other machine via
the LAN. XP PRO SP2 on both machines. Relatively simple? The LAN is
functional - I just wanted to learn about 'remote connection'. Bad
idea?

Jethro

 

[Sooner Al [MVP]]

You can download Tweak UI for XP from MS. Look at the Login section of Tweak
UI to enable/disable auto logon for a user...

http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx

You can download the new RDP 6 client for XP from here...

http://www.microsoft.com/downloads/...0c-0d18-4306-abcf-d4f18c8f5df9&DisplayLang=en

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

Beyond that...

On RIGHT make sure the service is started and is in fact listening on TCP
Port 3389. See this...

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

Make sure logging is setup on each PC.

http://theillustratednetwork.mvps.o...teDesktopSetupandTroubleshooting.html#Logging

On each PC (LEFT and RIGHT) search for files ending in .RDP or .rdp as
suggested by Pegasus (MVP). Delete those files.

On both LEFT and RIGHT create a new limited user account with a password for
testing. You can remove the account later when this is all fixed. Add the
new test user ID to the Remote Desktop Users Group. See if you can login
using the new user account on each PC.

--

Al Jarvi (MS-MVP Windows Networking)

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

 

[Jethro]

You can download Tweak UI for XP from MS. Look at the Login section of Tweak
UI to enable/disable auto logon for a user...

http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx

You can download the new RDP 6 client for XP from here...

http://www.microsoft.com/downloads/...0c-0d18-4306-abcf-d4f18c8f5df9&DisplayLang=en

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

Beyond that...

On RIGHT make sure the service is started and is in fact listening on TCP
Port 3389. See this...

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

I did what this line said to do:
The user can verify if the Terminal Services is running on the desktop
PC by executing the services.msc command from the Windows XP Start |
Run command window. The server status should be Started.

I had to make some services automatic, and then started any not
started. They were manual originally.

I got identical results - that is, LEFT can connect to RIGHT, but not
vice versa.

I tried netstat -a and verify the PC is listening on TCP Port 3389 -
but on both machines the DOS window simply flashed but left nothing
displayed for me to look at. So I can't verify that either machine is
listening on port 3389. :<(

Make sure logging is setup on each PC.

http://theillustratednetwork.mvps.o...teDesktopSetupandTroubleshooting.html#Logging

On each PC (LEFT and RIGHT) search for files ending in .RDP or .rdp as
suggested by Pegasus (MVP). Delete those files.

I found one such file on both machines under Documents and
settings\user\my documents and under My Computer - default.rdp. I
removed all. Then I created a limited account as below and tested
remote desktop thataway. The new desktop screens were pretty much
'virgin' as I expected - so I used run>cmd to use the command
mstsc /v:###.###.###.### to test remote connect. I got identical
results - that is, LEFT can connect to RIGHT, but not vice versa.

 

[Sooner Al [MVP]]

I did what this line said to do:
The user can verify if the Terminal Services is running on the desktop
PC by executing the services.msc command from the Windows XP Start |
Run command window. The server status should be Started.

I had to make some services automatic, and then started any not
started. They were manual originally.

I got identical results - that is, LEFT can connect to RIGHT, but not
vice versa.

I tried netstat -a and verify the PC is listening on TCP Port 3389 -
but on both machines the DOS window simply flashed but left nothing
displayed for me to look at. So I can't verify that either machine is
listening on port 3389. :<(


I found one such file on both machines under Documents and
settings\user\my documents and under My Computer - default.rdp. I
removed all. Then I created a limited account as below and tested
remote desktop thataway. The new desktop screens were pretty much
'virgin' as I expected - so I used run>cmd to use the command
mstsc /v:###.###.###.### to test remote connect. I got identical
results - that is, LEFT can connect to RIGHT, but not vice versa.

To run netstat go to "Start -> Run" and type cmd in the command window. At
the resulting command prompt run the netstat command.

--

Al Jarvi (MS-MVP Windows Networking)

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

 

[Sooner Al [MVP]]

Also, on each PC run the group policy editor and verify all the group
policies that pertain to Terminal services are in a "not configured"
state...

Click Start, click Run, type gpedit.msc, and then click OK.

In the Group Policy editor, click to expand Computer Configuration, click to
expand Administrative Templates, click to expand Windows Components, and
then click to expand Terminal Services.

--

Al Jarvi (MS-MVP Windows Networking)

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

 

[Jethro]

To run netstat go to "Start -> Run" and type cmd in the command window. At
the resulting command prompt run the netstat command.

Gad - you're smart! Guess that's why they pay you the big bucks?
Anyway, netstat on RIGHT machine shows 'listening' on port 3389, to
wit:
TCP RIGHT:3389 RIGHT:0 LISTENING

OTOH, LEFT machine does not show that at all, not even port 3389
whatsoever. Maybe this is a clue?

Jethro

 

[Sooner Al [MVP]]

Gad - you're smart! Guess that's why they pay you the big bucks?
Anyway, netstat on RIGHT machine shows 'listening' on port 3389, to
wit:
TCP RIGHT:3389 RIGHT:0 LISTENING

OTOH, LEFT machine does not show that at all, not even port 3389
whatsoever. Maybe this is a clue?

Jethro

Is the service running on LEFT?

--

Al Jarvi (MS-MVP Windows Networking)

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

 

[Jethro]

Also, on each PC run the group policy editor and verify all the group
policies that pertain to Terminal services are in a "not configured"
state...

Click Start, click Run, type gpedit.msc, and then click OK.

In the Group Policy editor, click to expand Computer Configuration, click to
expand Administrative Templates, click to expand Windows Components, and
then click to expand Terminal Services.

As near as I can tell, everything there is set 'not configured'.

Jethro

 

[Sooner Al [MVP]]

As near as I can tell, everything there is set 'not configured'.

Jethro

All of the policies are either set to not configured or not. Which is it?

Beyond that what happens when you check the service on LEFT? Is it started
or not?

By the way, I ran across this post from late July where you said you could
login to RIGHT with Remote Desktop.

http://groups.google.com/group/microsoft.public.windowsxp.network_web/msg/2c10674acaa44e55

Now you can't. What changed? Can you go back to a restore point prior to the
time Remote Desktop stopped working to see if that fixes the problem on that
PC?

Have you ever been able to login to LEFT using Remote Desktop?

--

Al Jarvi (MS-MVP Windows Networking)

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

 

[Jethro]

All of the policies are either set to not configured or not. Which is it?

Good golly! I think I have said something wrong - or have at least
burst your patience - sorry if so. I meant that all the entries
there said 'not configured'. Nothing more.

Beyond that what happens when you check the service on LEFT? Is it started
or not?

As I tried to say - I checked the service on both LEFT and RIGHT, and
some were not started, some were. Some were automatic, some manual.
I set all to automatic on both machines. Then I set all to started on
both machines.

By the way, I ran across this post from late July where you said you could
login to RIGHT with Remote Desktop.

http://groups.google.com/group/microsoft.public.windowsxp.network_web/msg/2c10674acaa44e55

You are right! And I meant exactly that.

I checked my post of 11:10 - 08/07, and this is what I said:

This is correct, and always has been true. I never meant to ever say
that RIGHT machine has ever connected to LEFT machine. In what post
did I say that? If I did, I made a booboo, but tell me - straighten
me out - in what post did I say that?

At 11:10A 08/08 I said:
Gad - you're smart! Guess that's why they pay you the big bucks?
Anyway, netstat on RIGHT machine shows 'listening' on port 3389, to
wit:
TCP RIGHT:3389 RIGHT:0 LISTENING

OTOH, LEFT machine does not show that at all, not even port 3389
whatsoever. Maybe this is a clue?

Now you can't. What changed?
Nothing

Can you go back to a restore point prior to the
time Remote Desktop stopped working to see if that fixes the problem on that
PC?

Have you ever been able to login to LEFT using Remote Desktop?

NNNOOO.



Can you guide me as to how I can render LEFT machine's netstat to say
'listening' on port 3389?

I hope this clarifies things. If you tell me to go peddle my papers,
I will.

Thanks again,
Jethro

 

[Sooner Al [MVP]]

Ok, to make this clear...

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

You can login in to RIGHT from LEFT using Remote Desktop. There is no
problem with RIGHT, correct? If that is not correct then you have lost me
somewhere...

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

The Terminal Services service status on LEFT is started but the netstat
command shows LEFT is not listening on TCP Port 3389. Have you or someone
else in the past changed the listening port on LEFT to something other than
3389?

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

If not then as an administrator run this command from a command line on
LEFT. Reboot the PC after doing this...

regsvr32 remotepg.dll

--

Al Jarvi (MS-MVP Windows Networking)


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