Lost Remote desktop connection

After rebooting the server, I can no longer use the
Remote Desktop Connection from inside the network, to
connect to it. I checked all the settings and they are
exactly where they are supposed to be.
Tha message is: "The client could not connect to the
remote computer"


Any ideas?

Thanks

Hi Matt,

If you logon to server's console and use Terminal Services client to connect
back to itself does it work?

What operating system is the server 2000 or 2003? If you are running Windows
2003 did ICF become enabled? Can clients ping the server and access e.g.
shares?

Mike

"Matt" <(E-Mail Removed)> wrote in message
news:0f5201c48bc2$27f41380$(E-Mail Removed)...
> After rebooting the server, I can no longer use the
> Remote Desktop Connection from inside the network, to
> connect to it. I checked all the settings and they are
> exactly where they are supposed to be.
> Tha message is: "The client could not connect to the
> remote computer"
>
>
> Any ideas?
>
> Thanks

Thanks for the reply:
When I use the Remote desktop, at server's console, I get
the same message. It does not work. The server is
Standard 2003. ICF is disabled and clints can ping and
access shares etc.

Matt
>-----Original Message-----
>Hi Matt,
>
>If you logon to server's console and use Terminal
Services client to connect
>back to itself does it work?
>
>What operating system is the server 2000 or 2003? If you
are running Windows
>2003 did ICF become enabled? Can clients ping the server
and access e.g.
>shares?
>
>Mike
>
>"Matt" <(E-Mail Removed)> wrote in
message
>news:0f5201c48bc2$27f41380$(E-Mail Removed)...
>> After rebooting the server, I can no longer use the
>> Remote Desktop Connection from inside the network, to
>> connect to it. I checked all the settings and they are
>> exactly where they are supposed to be.
>> Tha message is: "The client could not connect to the
>> remote computer"
>>
>>
>> Any ideas?
>>
>> Thanks
>
>
>.
>

Can you run this on your server in command line

netstat -an

and look for

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

Can you see 3389 TCP port in the list?

Can you also Right click on My Computer -> Remote tab and check that "Allow
users to connect to remotely to this computer" is checked...

Mike

<(E-Mail Removed)> wrote in message
news:193901c48c62$ee379440$(E-Mail Removed)...
> Thanks for the reply:
> When I use the Remote desktop, at server's console, I get
> the same message. It does not work. The server is
> Standard 2003. ICF is disabled and clints can ping and
> access shares etc.
>
> Matt
> >-----Original Message-----
> >Hi Matt,
> >
> >If you logon to server's console and use Terminal
> Services client to connect
> >back to itself does it work?
> >
> >What operating system is the server 2000 or 2003? If you
> are running Windows
> >2003 did ICF become enabled? Can clients ping the server
> and access e.g.
> >shares?
> >
> >Mike
> >
> >"Matt" <(E-Mail Removed)> wrote in
> message
> >news:0f5201c48bc2$27f41380$(E-Mail Removed)...
> >> After rebooting the server, I can no longer use the
> >> Remote Desktop Connection from inside the network, to
> >> connect to it. I checked all the settings and they are
> >> exactly where they are supposed to be.
> >> Tha message is: "The client could not connect to the
> >> remote computer"
> >>
> >>
> >> Any ideas?
> >>
> >> Thanks
> >
> >
> >.
> >

Thank you for the assistance. After executing the command
line netstat -an, the port 3389 was not listed. Also in
the remote tab,the "allow users to connect remotely to
this computer " is checked

Matt
>-----Original Message-----
>Can you run this on your server in command line
>
>netstat -an
>
>and look for
>
>TCP 0.0.0.0:3389 0.0.0.0:0
LISTENING
>
>Can you see 3389 TCP port in the list?
>
>Can you also Right click on My Computer -> Remote tab
and check that "Allow
>users to connect to remotely to this computer" is
checked...
>
>Mike
>
><(E-Mail Removed)> wrote in message
>news:193901c48c62$ee379440$(E-Mail Removed)...
>> Thanks for the reply:
>> When I use the Remote desktop, at server's console, I
get
>> the same message. It does not work. The server is
>> Standard 2003. ICF is disabled and clints can ping and
>> access shares etc.
>>
>> Matt
>> >-----Original Message-----
>> >Hi Matt,
>> >
>> >If you logon to server's console and use Terminal
>> Services client to connect
>> >back to itself does it work?
>> >
>> >What operating system is the server 2000 or 2003? If
you
>> are running Windows
>> >2003 did ICF become enabled? Can clients ping the
server
>> and access e.g.
>> >shares?
>> >
>> >Mike
>> >
>> >"Matt" <(E-Mail Removed)> wrote in
>> message
>> >news:0f5201c48bc2$27f41380$(E-Mail Removed)...
>> >> After rebooting the server, I can no longer use the
>> >> Remote Desktop Connection from inside the network,
to
>> >> connect to it. I checked all the settings and they
are
>> >> exactly where they are supposed to be.
>> >> Tha message is: "The client could not connect to the
>> >> remote computer"
>> >>
>> >>
>> >> Any ideas?
>> >>
>> >> Thanks
>> >
>> >
>> >.
>> >
>
>
>.
>

Matt,

I don't know what would cause this. What you could try and do is disable RDP
on Remote tab reboot the server and then enable it back...

Mike

<(E-Mail Removed)> wrote in message
news:06c401c48d13$3f6d4fc0$(E-Mail Removed)...
> Thank you for the assistance. After executing the command
> line netstat -an, the port 3389 was not listed. Also in
> the remote tab,the "allow users to connect remotely to
> this computer " is checked
>
> Matt
> >-----Original Message-----
> >Can you run this on your server in command line
> >
> >netstat -an
> >
> >and look for
> >
> >TCP 0.0.0.0:3389 0.0.0.0:0
> LISTENING
> >
> >Can you see 3389 TCP port in the list?
> >
> >Can you also Right click on My Computer -> Remote tab
> and check that "Allow
> >users to connect to remotely to this computer" is
> checked...
> >
> >Mike
> >
> ><(E-Mail Removed)> wrote in message
> >news:193901c48c62$ee379440$(E-Mail Removed)...
> >> Thanks for the reply:
> >> When I use the Remote desktop, at server's console, I
> get
> >> the same message. It does not work. The server is
> >> Standard 2003. ICF is disabled and clints can ping and
> >> access shares etc.
> >>
> >> Matt
> >> >-----Original Message-----
> >> >Hi Matt,
> >> >
> >> >If you logon to server's console and use Terminal
> >> Services client to connect
> >> >back to itself does it work?
> >> >
> >> >What operating system is the server 2000 or 2003? If
> you
> >> are running Windows
> >> >2003 did ICF become enabled? Can clients ping the
> server
> >> and access e.g.
> >> >shares?
> >> >
> >> >Mike
> >> >
> >> >"Matt" <(E-Mail Removed)> wrote in
> >> message
> >> >news:0f5201c48bc2$27f41380$(E-Mail Removed)...
> >> >> After rebooting the server, I can no longer use the
> >> >> Remote Desktop Connection from inside the network,
> to
> >> >> connect to it. I checked all the settings and they
> are
> >> >> exactly where they are supposed to be.
> >> >> Tha message is: "The client could not connect to the
> >> >> remote computer"
> >> >>
> >> >>
> >> >> Any ideas?
> >> >>
> >> >> Thanks
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >