Jethro

You readers probably are saying, Oh No - here he is again - and here I
am!

This is another try to make my Remote Desktop Connection work.

In the 'active connections' result from command 'netstat -a', I see
a line on my so-called RIGHT machine as:

Proto Local Address Foreign Address State
TCP RIGHT:3389 RIGHT:0 LISTENING

and, as I have said in the past, I can connect from my LEFT machine to
the RIGHT machine just fine. So, indeed, RIGHT machine is listening.

But, as I also have said, I cannot connect from my RIGHT machine to my
LEFT machine.

I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
machine. I'm thinking maybe my problem is that my LEFT machine is not
listening' and it should be.

So, a simple question. How and where do I create that line so LEFT
machine is listening on port 3389?

Robert Moir

"Jethro" <Wilson@somewhere.org> wrote in message
news:mamrb39q3f4papat26a61hsmjrmcpbhjiq@4ax.com...
> You readers probably are saying, Oh No - here he is again - and here I
> am!
>
> This is another try to make my Remote Desktop Connection work.
>
> In the 'active connections' result from command 'netstat -a', I see
> a line on my so-called RIGHT machine as:
>
> Proto Local Address Foreign Address State
> TCP RIGHT:3389 RIGHT:0 LISTENING
>
> and, as I have said in the past, I can connect from my LEFT machine to
> the RIGHT machine just fine. So, indeed, RIGHT machine is listening.
>
> But, as I also have said, I cannot connect from my RIGHT machine to my
> LEFT machine.
>
> I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
> machine. I'm thinking maybe my problem is that my LEFT machine is not
> listening' and it should be.
>
> So, a simple question. How and where do I create that line so LEFT
> machine is listening on port 3389?

Not so simple. Talking about ports essentially means you're talking about
surgery when all that should be needed is a plaster. I'm assuming your
'left' machine is an XP Pro machine?

Right-Click My Computer, choose properties.
Click the 'Remote' tab.
In "Remote Desktop", ensure that 'Allow users to connect remotely to this
computer' is ticked, and press OK.

This 'should' be all you need to do. Are you saying you've tried this and
got nowhere?

Jack \(MVP-Networking\).

Hi
The computer that is idle with the Remote Desktop Host On is the one that is
listening.
Jack (MVP-Networking).

"Jethro" <Wilson@somewhere.org> wrote in message
news:mamrb39q3f4papat26a61hsmjrmcpbhjiq@4ax.com...
> You readers probably are saying, Oh No - here he is again - and here I
> am!
>
> This is another try to make my Remote Desktop Connection work.
>
> In the 'active connections' result from command 'netstat -a', I see
> a line on my so-called RIGHT machine as:
>
> Proto Local Address Foreign Address State
> TCP RIGHT:3389 RIGHT:0 LISTENING
>
> and, as I have said in the past, I can connect from my LEFT machine to
> the RIGHT machine just fine. So, indeed, RIGHT machine is listening.
>
> But, as I also have said, I cannot connect from my RIGHT machine to my
> LEFT machine.
>
> I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
> machine. I'm thinking maybe my problem is that my LEFT machine is not
> listening' and it should be.
>
> So, a simple question. How and where do I create that line so LEFT
> machine is listening on port 3389?

Jack \(MVP-Networking\).

Hi
The computer that is idle with the Remote Desktop Host On is the one that is
listening.
Jack (MVP-Networking).

"Jethro" <Wilson@somewhere.org> wrote in message
news:mamrb39q3f4papat26a61hsmjrmcpbhjiq@4ax.com...
> You readers probably are saying, Oh No - here he is again - and here I
> am!
>
> This is another try to make my Remote Desktop Connection work.
>
> In the 'active connections' result from command 'netstat -a', I see
> a line on my so-called RIGHT machine as:
>
> Proto Local Address Foreign Address State
> TCP RIGHT:3389 RIGHT:0 LISTENING
>
> and, as I have said in the past, I can connect from my LEFT machine to
> the RIGHT machine just fine. So, indeed, RIGHT machine is listening.
>
> But, as I also have said, I cannot connect from my RIGHT machine to my
> LEFT machine.
>
> I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
> machine. I'm thinking maybe my problem is that my LEFT machine is not
> listening' and it should be.
>
> So, a simple question. How and where do I create that line so LEFT
> machine is listening on port 3389?

Jethro

On Sat, 11 Aug 2007 17:11:22 +0100, "Robert Moir"
<usenet@REMOVE2EMAILrobertmoir.com> wrote:

>
>"Jethro" <Wilson@somewhere.org> wrote in message
>news:mamrb39q3f4papat26a61hsmjrmcpbhjiq@4ax.com.. .
>> You readers probably are saying, Oh No - here he is again - and here I
>> am!
>>
>> This is another try to make my Remote Desktop Connection work.
>>
>> In the 'active connections' result from command 'netstat -a', I see
>> a line on my so-called RIGHT machine as:
>>
>> Proto Local Address Foreign Address State
>> TCP RIGHT:3389 RIGHT:0 LISTENING
>>
>> and, as I have said in the past, I can connect from my LEFT machine to
>> the RIGHT machine just fine. So, indeed, RIGHT machine is listening.
>>
>> But, as I also have said, I cannot connect from my RIGHT machine to my
>> LEFT machine.
>>
>> I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
>> machine. I'm thinking maybe my problem is that my LEFT machine is not
>> listening' and it should be.
>>
>> So, a simple question. How and where do I create that line so LEFT
>> machine is listening on port 3389?
>
>Not so simple. Talking about ports essentially means you're talking about
>surgery when all that should be needed is a plaster. I'm assuming your
>'left' machine is an XP Pro machine?

Both are - sorry.


>
>Right-Click My Computer, choose properties.
>Click the 'Remote' tab.
>In "Remote Desktop", ensure that 'Allow users to connect remotely to this
>computer' is ticked, and press OK.

I right-clicked on My Computer and selected Properties on both
machines - I don't see any 'Remote Tab' on either. Now then - Control
Panel>System does produce the Remote Tab. An yes I have that option
checked on both machines.

>
>This 'should' be all you need to do. Are you saying you've tried this and
>got nowhere?

Yep

Thanks

Jethro
>

Jethro

On Sat, 11 Aug 2007 12:34:31 -0400, "Jack \(MVP-Networking\)."
<jack@discussiongroup.com> wrote:

>Hi
>The computer that is idle with the Remote Desktop Host On is the one that is
>listening.
>Jack (MVP-Networking).
>
Hi back.

Can both machines be listening at same time? IOW, normally one would
have one host and one or more remotes. I have two machines that I
want to be able to run one's apps etc on the other - my choice as to
which, but of course, only one connection would (could) be active at
the same time. Is that reasonable?

Thanks
Jethro


>"Jethro" <Wilson@somewhere.org> wrote in message
>news:mamrb39q3f4papat26a61hsmjrmcpbhjiq@4ax.com.. .
>> You readers probably are saying, Oh No - here he is again - and here I
>> am!
>>
>> This is another try to make my Remote Desktop Connection work.
>>
>> In the 'active connections' result from command 'netstat -a', I see
>> a line on my so-called RIGHT machine as:
>>
>> Proto Local Address Foreign Address State
>> TCP RIGHT:3389 RIGHT:0 LISTENING
>>
>> and, as I have said in the past, I can connect from my LEFT machine to
>> the RIGHT machine just fine. So, indeed, RIGHT machine is listening.
>>
>> But, as I also have said, I cannot connect from my RIGHT machine to my
>> LEFT machine.
>>
>> I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
>> machine. I'm thinking maybe my problem is that my LEFT machine is not
>> listening' and it should be.
>>
>> So, a simple question. How and where do I create that line so LEFT
>> machine is listening on port 3389?

Jethro

On Sat, 11 Aug 2007 17:11:22 +0100, "Robert Moir"
<usenet@REMOVE2EMAILrobertmoir.com> wrote:

>
>"Jethro" <Wilson@somewhere.org> wrote in message
>news:mamrb39q3f4papat26a61hsmjrmcpbhjiq@4ax.com.. .
>> You readers probably are saying, Oh No - here he is again - and here I
>> am!
>>
>> This is another try to make my Remote Desktop Connection work.
>>
>> In the 'active connections' result from command 'netstat -a', I see
>> a line on my so-called RIGHT machine as:
>>
>> Proto Local Address Foreign Address State
>> TCP RIGHT:3389 RIGHT:0 LISTENING
>>
>> and, as I have said in the past, I can connect from my LEFT machine to
>> the RIGHT machine just fine. So, indeed, RIGHT machine is listening.
>>
>> But, as I also have said, I cannot connect from my RIGHT machine to my
>> LEFT machine.
>>
>> I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
>> machine. I'm thinking maybe my problem is that my LEFT machine is not
>> listening' and it should be.
>>
>> So, a simple question. How and where do I create that line so LEFT
>> machine is listening on port 3389?
>
>Not so simple. Talking about ports essentially means you're talking about
>surgery when all that should be needed is a plaster. I'm assuming your
>'left' machine is an XP Pro machine?

Both are - sorry.


>
>Right-Click My Computer, choose properties.
>Click the 'Remote' tab.
>In "Remote Desktop", ensure that 'Allow users to connect remotely to this
>computer' is ticked, and press OK.

I right-clicked on My Computer and selected Properties on both
machines - I don't see any 'Remote Tab' on either. Now then - Control
Panel>System does produce the Remote Tab. An yes I have that option
checked on both machines.

>
>This 'should' be all you need to do. Are you saying you've tried this and
>got nowhere?

Yep

Thanks

Jethro
>

Jethro

On Sat, 11 Aug 2007 12:34:31 -0400, "Jack \(MVP-Networking\)."
<jack@discussiongroup.com> wrote:

>Hi
>The computer that is idle with the Remote Desktop Host On is the one that is
>listening.
>Jack (MVP-Networking).
>
Hi back.

Can both machines be listening at same time? IOW, normally one would
have one host and one or more remotes. I have two machines that I
want to be able to run one's apps etc on the other - my choice as to
which, but of course, only one connection would (could) be active at
the same time. Is that reasonable?

Thanks
Jethro


>"Jethro" <Wilson@somewhere.org> wrote in message
>news:mamrb39q3f4papat26a61hsmjrmcpbhjiq@4ax.com.. .
>> You readers probably are saying, Oh No - here he is again - and here I
>> am!
>>
>> This is another try to make my Remote Desktop Connection work.
>>
>> In the 'active connections' result from command 'netstat -a', I see
>> a line on my so-called RIGHT machine as:
>>
>> Proto Local Address Foreign Address State
>> TCP RIGHT:3389 RIGHT:0 LISTENING
>>
>> and, as I have said in the past, I can connect from my LEFT machine to
>> the RIGHT machine just fine. So, indeed, RIGHT machine is listening.
>>
>> But, as I also have said, I cannot connect from my RIGHT machine to my
>> LEFT machine.
>>
>> I don't have the above 'listening' line in the 'NETSTAT -a' on my LEFT
>> machine. I'm thinking maybe my problem is that my LEFT machine is not
>> listening' and it should be.
>>
>> So, a simple question. How and where do I create that line so LEFT
>> machine is listening on port 3389?

Robert Moir

"Jethro" <Wilson@somewhere.org> wrote in message
news:llrrb39dmh3uq4jna4rp0uuf6sm72kn5bh@4ax.com...

> I right-clicked on My Computer and selected Properties on both
> machines - I don't see any 'Remote Tab' on either. Now then - Control
> Panel>System does produce the Remote Tab. An yes I have that option
> checked on both machines.
>
>>
>>This 'should' be all you need to do. Are you saying you've tried this and
>>got nowhere?
>
> Yep

Right. Still in control panel, open up Performance and Maintenance,
Administrative Tools and then run services.

Scroll down to the service named "Terminal Services". Is it started? If not,
what happens when you start it?

Still in administrative tools, open Event Viewer. Have a look in system for
errors relating to services having trouble starting at boot time in general,
and of course pay special interest to problems recorded with the terminal
server service. I'd also be thinking of double-checking my firewall about
this time to make sure that isn't treading on things.

This is one of those "really, it should 'just work'" kinda things so it's
odd that you're having issues, I wonder if something is killing it at
startup or if some settings got mixed up.

Jethro

On Sat, 11 Aug 2007 20:14:52 +0100, "Robert Moir"
<usenet@REMOVE2EMAILrobertmoir.com> wrote:

>
>"Jethro" <Wilson@somewhere.org> wrote in message
>news:llrrb39dmh3uq4jna4rp0uuf6sm72kn5bh@4ax.com.. .
>
>> I right-clicked on My Computer and selected Properties on both
>> machines - I don't see any 'Remote Tab' on either. Now then - Control
>> Panel>System does produce the Remote Tab. An yes I have that option
>> checked on both machines.
>>
>>>
>>>This 'should' be all you need to do. Are you saying you've tried this and
>>>got nowhere?
>>
>> Yep
>
>Right. Still in control panel, open up Performance and Maintenance,
>Administrative Tools and then run services.
>
>Scroll down to the service named "Terminal Services". Is it started? If not,
>what happens when you start it?

On RIGHT machine, it was started, but on LEFT machine it was disabled!
for some reason. I enabled & started it, and now things are working
(for the first time!!!!).

>
>Still in administrative tools, open Event Viewer. Have a look in system for
>errors relating to services having trouble starting at boot time in general,
>and of course pay special interest to problems recorded with the terminal
>server service. I'd also be thinking of double-checking my firewall about
>this time to make sure that isn't treading on things.
>
>This is one of those "really, it should 'just work'" kinda things so it's
>odd that you're having issues, I wonder if something is killing it at
>startup or if some settings got mixed up.
>
>
Now I have another question - I notice that when a remote machine, say
LEFT, is connected to RIGHT machine, the latter is locked out and
displays only a login screen. This may be how Remote Desktop is
designed, but I am used to PCANYWHERE wherein when a remote is
controlling a 'host's' machine, the latter can be observed. In this
way, when I was on a remote machine, I could 'show' a user on his
machine exactly what I was doing, and by so doing, that user would
learn from me by following what I would do.

I guess that is not possible with Remote Desktop?

Anyway, thanks a meg for you help. Sorry to be so dense.

Jethro