Jump to content

no RDP after a restore

Guest TR

By Guest TR
in Windows NT Server

 Share

Recommended Posts

Guest TR

Guest TR

Posted
Posted

Hi all,

 

I had a hard drive failure on a windows 2003 Terminal Server w/SP2.. I

used the ASR recovery process once the hard drive was replaced to recover.

All the files were restored but now the Terminal will not accept Remote

connections. Any ideas:? I get the error that the terminal server is not

responding and that it is too busy and to try back later. All files and

services appear to be functioning normal.

 

Any help would be appreciated.

Thanks

TR

  • Replies 10
  • Created
  • Last Reply

Popular Days

Popular Days

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Posted
Posted

Re: no RDP after a restore

 

Is the server listening on port 3389? Use "netstat -an" to check.

If it isn't, and I expect that it isn't, then I would delete the rdp-

tcp connection and create a new one, in Terminal Services

Configuration. Then reboot the server and try again.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"TR" <TR@somehwere.com> wrote on 07 nov 2007 in

microsoft.public.windows.terminal_services:

> Hi all,

>

> I had a hard drive failure on a windows 2003 Terminal Server

> w/SP2.. I used the ASR recovery process once the hard drive was

> replaced to recover. All the files were restored but now the

> Terminal will not accept Remote connections. Any ideas:? I get

> the error that the terminal server is not responding and that it

> is too busy and to try back later. All files and services appear

> to be functioning normal.

>

> Any help would be appreciated.

> Thanks

> TR

Guest TR

Guest TR

Posted
Posted

Re: no RDP after a restore

 

Hi Vera,

 

I tried that but it didn't work. Clients are still getting the following

error when trying to connect to the terminal server.

 

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to

accept new connections.

Please try again connecting later.

 

Any other ideas?

Thanks

Tony

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

> Is the server listening on port 3389? Use "netstat -an" to check.

> If it isn't, and I expect that it isn't, then I would delete the rdp-

> tcp connection and create a new one, in Terminal Services

> Configuration. Then reboot the server and try again.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hi all,

>>

>> I had a hard drive failure on a windows 2003 Terminal Server

>> w/SP2.. I used the ASR recovery process once the hard drive was

>> replaced to recover. All the files were restored but now the

>> Terminal will not accept Remote connections. Any ideas:? I get

>> the error that the terminal server is not responding and that it

>> is too busy and to try back later. All files and services appear

>> to be functioning normal.

>>

>> Any help would be appreciated.

>> Thanks

>> TR

Guest TR

Guest TR

Posted
Posted

Re: no RDP after a restore

 

Hi Vera,

 

Yes the server is listening on port 3389. I deleted the connection and

re-created it but clients are still getting:

 

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to

accept new connections.

Please try again connecting later.

 

Any ideas?

 

Thanks

Tony

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

> Is the server listening on port 3389? Use "netstat -an" to check.

> If it isn't, and I expect that it isn't, then I would delete the rdp-

> tcp connection and create a new one, in Terminal Services

> Configuration. Then reboot the server and try again.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hi all,

>>

>> I had a hard drive failure on a windows 2003 Terminal Server

>> w/SP2.. I used the ASR recovery process once the hard drive was

>> replaced to recover. All the files were restored but now the

>> Terminal will not accept Remote connections. Any ideas:? I get

>> the error that the terminal server is not responding and that it

>> is too busy and to try back later. All files and services appear

>> to be functioning normal.

>>

>> Any help would be appreciated.

>> Thanks

>> TR

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Posted
Posted

Re: no RDP after a restore

 

OK, that's good news.

Next thing to try:

Any errors in the EventLog on the server?

Can you connect from the console of the server to the server itself

with rdp (to localhost)?

Can you connect using the IP number in stead of the server name?

Also check the Network settings in the rdp-tcp connection. Is it

listening on all NICs? Is the number of allowed connections correct

( > 0 )?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"TR" <TR@somehwere.com> wrote on 07 nov 2007 in

microsoft.public.windows.terminal_services:

> Hi Vera,

>

> Yes the server is listening on port 3389. I deleted the

> connection and re-created it but clients are still getting:

>

> The client could not connect to the remote computer.

> Remote connections might not be enabled or the computer might be

> too busy to accept new connections.

> Please try again connecting later.

>

> Any ideas?

>

> Thanks

> Tony

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

>> Is the server listening on port 3389? Use "netstat -an" to

>> check. If it isn't, and I expect that it isn't, then I would

>> delete the rdp- tcp connection and create a new one, in

>> Terminal Services Configuration. Then reboot the server and try

>> again.

>> _________________________________________________________ Vera

>> Noest MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hi all,

>>>

>>> I had a hard drive failure on a windows 2003 Terminal Server

>>> w/SP2.. I used the ASR recovery process once the hard drive

>>> was replaced to recover. All the files were restored but now

>>> the Terminal will not accept Remote connections. Any ideas:?

>>> I get the error that the terminal server is not responding and

>>> that it is too busy and to try back later. All files and

>>> services appear to be functioning normal.

>>>

>>> Any help would be appreciated.

>>> Thanks

>>> TR

Guest TR

Guest TR

Posted
Posted

Re: no RDP after a restore

 

Hi Vera,

 

There are no unusual errors in the event log that I can see. As a matter of

fact it is fairly clean.

 

When I am logged into the administrator console of the TERMINAL I can

connect to localhost, the NETBIOS name, the FQDN and the raw IP using the

Remote desktop, but I cannot connect to the TREMINAL server via RDP from any

other machine on the network. I have checked Network settings and

everything looks fine. At the administrator console I can connect to

anywhere in the network, I can surf the internet and I can connect to all

available shares. I can manage the TERMINAL from the Domain controller and

I can ping it and get valid reponses. All programs work. Any other ideas

before I decide to make a backup of the files, wipe the machine and start

from scratch?

 

Thanks

TR

 

It's never like they tell you.. :(

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99E1AD34FAD1Cveranoesthemutforsse@207.46.248.16...

> OK, that's good news.

> Next thing to try:

> Any errors in the EventLog on the server?

> Can you connect from the console of the server to the server itself

> with rdp (to localhost)?

> Can you connect using the IP number in stead of the server name?

> Also check the Network settings in the rdp-tcp connection. Is it

> listening on all NICs? Is the number of allowed connections correct

> ( > 0 )?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hi Vera,

>>

>> Yes the server is listening on port 3389. I deleted the

>> connection and re-created it but clients are still getting:

>>

>> The client could not connect to the remote computer.

>> Remote connections might not be enabled or the computer might be

>> too busy to accept new connections.

>> Please try again connecting later.

>>

>> Any ideas?

>>

>> Thanks

>> Tony

>>

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

>>> Is the server listening on port 3389? Use "netstat -an" to

>>> check. If it isn't, and I expect that it isn't, then I would

>>> delete the rdp- tcp connection and create a new one, in

>>> Terminal Services Configuration. Then reboot the server and try

>>> again.

>>> _________________________________________________________ Vera

>>> Noest MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hi all,

>>>>

>>>> I had a hard drive failure on a windows 2003 Terminal Server

>>>> w/SP2.. I used the ASR recovery process once the hard drive

>>>> was replaced to recover. All the files were restored but now

>>>> the Terminal will not accept Remote connections. Any ideas:?

>>>> I get the error that the terminal server is not responding and

>>>> that it is too busy and to try back later. All files and

>>>> services appear to be functioning normal.

>>>>

>>>> Any help would be appreciated.

>>>> Thanks

>>>> TR

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Posted
Posted

Re: no RDP after a restore

 

Mmm, only other thing that I can think of is the Windows firewall.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"TR" <TR@somehwere.com> wrote on 08 nov 2007 in

microsoft.public.windows.terminal_services:

> Hi Vera,

>

> There are no unusual errors in the event log that I can see. As

> a matter of fact it is fairly clean.

>

> When I am logged into the administrator console of the TERMINAL

> I can connect to localhost, the NETBIOS name, the FQDN and the

> raw IP using the Remote desktop, but I cannot connect to the

> TREMINAL server via RDP from any other machine on the network.

> I have checked Network settings and everything looks fine. At

> the administrator console I can connect to anywhere in the

> network, I can surf the internet and I can connect to all

> available shares. I can manage the TERMINAL from the Domain

> controller and I can ping it and get valid reponses. All

> programs work. Any other ideas before I decide to make a backup

> of the files, wipe the machine and start from scratch?

>

> Thanks

> TR

>

> It's never like they tell you.. :(

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99E1AD34FAD1Cveranoesthemutforsse@207.46.248.16...

>> OK, that's good news.

>> Next thing to try:

>> Any errors in the EventLog on the server?

>> Can you connect from the console of the server to the server

>> itself with rdp (to localhost)?

>> Can you connect using the IP number in stead of the server

>> name? Also check the Network settings in the rdp-tcp

>> connection. Is it listening on all NICs? Is the number of

>> allowed connections correct ( > 0 )?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hi Vera,

>>>

>>> Yes the server is listening on port 3389. I deleted the

>>> connection and re-created it but clients are still getting:

>>>

>>> The client could not connect to the remote computer.

>>> Remote connections might not be enabled or the computer might

>>> be too busy to accept new connections.

>>> Please try again connecting later.

>>>

>>> Any ideas?

>>>

>>> Thanks

>>> Tony

>>>

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>> wrote in message

>>> news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

>>>> Is the server listening on port 3389? Use "netstat -an" to

>>>> check. If it isn't, and I expect that it isn't, then I would

>>>> delete the rdp- tcp connection and create a new one, in

>>>> Terminal Services Configuration. Then reboot the server and

>>>> try again.

>>>> _________________________________________________________

>>>> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

>>>> TS troubleshooting: http://ts.veranoest.net

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> Hi all,

>>>>>

>>>>> I had a hard drive failure on a windows 2003 Terminal Server

>>>>> w/SP2.. I used the ASR recovery process once the hard drive

>>>>> was replaced to recover. All the files were restored but now

>>>>> the Terminal will not accept Remote connections. Any

>>>>> ideas:? I get the error that the terminal server is not

>>>>> responding and that it is too busy and to try back later.

>>>>> All files and services appear to be functioning normal.

>>>>>

>>>>> Any help would be appreciated.

>>>>> Thanks

>>>>> TR

Guest TR

Guest TR

Posted
Posted

Re: no RDP after a restore

 

How do i check to see if the windows firewall is causing the problem? I

don't believe it is enabled.

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99E2E3983B440veranoesthemutforsse@207.46.248.16...

> Mmm, only other thing that I can think of is the Windows firewall.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "TR" <TR@somehwere.com> wrote on 08 nov 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hi Vera,

>>

>> There are no unusual errors in the event log that I can see. As

>> a matter of fact it is fairly clean.

>>

>> When I am logged into the administrator console of the TERMINAL

>> I can connect to localhost, the NETBIOS name, the FQDN and the

>> raw IP using the Remote desktop, but I cannot connect to the

>> TREMINAL server via RDP from any other machine on the network.

>> I have checked Network settings and everything looks fine. At

>> the administrator console I can connect to anywhere in the

>> network, I can surf the internet and I can connect to all

>> available shares. I can manage the TERMINAL from the Domain

>> controller and I can ping it and get valid reponses. All

>> programs work. Any other ideas before I decide to make a backup

>> of the files, wipe the machine and start from scratch?

>>

>> Thanks

>> TR

>>

>> It's never like they tell you.. :(

>>

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns99E1AD34FAD1Cveranoesthemutforsse@207.46.248.16...

>>> OK, that's good news.

>>> Next thing to try:

>>> Any errors in the EventLog on the server?

>>> Can you connect from the console of the server to the server

>>> itself with rdp (to localhost)?

>>> Can you connect using the IP number in stead of the server

>>> name? Also check the Network settings in the rdp-tcp

>>> connection. Is it listening on all NICs? Is the number of

>>> allowed connections correct ( > 0 )?

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hi Vera,

>>>>

>>>> Yes the server is listening on port 3389. I deleted the

>>>> connection and re-created it but clients are still getting:

>>>>

>>>> The client could not connect to the remote computer.

>>>> Remote connections might not be enabled or the computer might

>>>> be too busy to accept new connections.

>>>> Please try again connecting later.

>>>>

>>>> Any ideas?

>>>>

>>>> Thanks

>>>> Tony

>>>>

>>>>

>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>> wrote in message

>>>> news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

>>>>> Is the server listening on port 3389? Use "netstat -an" to

>>>>> check. If it isn't, and I expect that it isn't, then I would

>>>>> delete the rdp- tcp connection and create a new one, in

>>>>> Terminal Services Configuration. Then reboot the server and

>>>>> try again.

>>>>> _________________________________________________________

>>>>> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>

>>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>>> microsoft.public.windows.terminal_services:

>>>>>

>>>>>> Hi all,

>>>>>>

>>>>>> I had a hard drive failure on a windows 2003 Terminal Server

>>>>>> w/SP2.. I used the ASR recovery process once the hard drive

>>>>>> was replaced to recover. All the files were restored but now

>>>>>> the Terminal will not accept Remote connections. Any

>>>>>> ideas:? I get the error that the terminal server is not

>>>>>> responding and that it is too busy and to try back later.

>>>>>> All files and services appear to be functioning normal.

>>>>>>

>>>>>> Any help would be appreciated.

>>>>>> Thanks

>>>>>> TR

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Posted
Posted

Re: no RDP after a restore

 

Sorry, that's what I meant: make sure it is disabled.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"TR" <TR@somehwere.com> wrote on 08 nov 2007 in

microsoft.public.windows.terminal_services:

> How do i check to see if the windows firewall is causing the

> problem? I don't believe it is enabled.

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99E2E3983B440veranoesthemutforsse@207.46.248.16...

>> Mmm, only other thing that I can think of is the Windows

>> firewall.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "TR" <TR@somehwere.com> wrote on 08 nov 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hi Vera,

>>>

>>> There are no unusual errors in the event log that I can see.

>>> As a matter of fact it is fairly clean.

>>>

>>> When I am logged into the administrator console of the

>>> TERMINAL I can connect to localhost, the NETBIOS name, the

>>> FQDN and the raw IP using the Remote desktop, but I cannot

>>> connect to the TREMINAL server via RDP from any other machine

>>> on the network. I have checked Network settings and everything

>>> looks fine. At the administrator console I can connect to

>>> anywhere in the network, I can surf the internet and I can

>>> connect to all available shares. I can manage the TERMINAL

>>> from the Domain controller and I can ping it and get valid

>>> reponses. All programs work. Any other ideas before I decide

>>> to make a backup of the files, wipe the machine and start from

>>> scratch?

>>>

>>> Thanks

>>> TR

>>>

>>> It's never like they tell you.. :(

>>>

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>> wrote in message

>>> news:Xns99E1AD34FAD1Cveranoesthemutforsse@207.46.248.16...

>>>> OK, that's good news.

>>>> Next thing to try:

>>>> Any errors in the EventLog on the server?

>>>> Can you connect from the console of the server to the server

>>>> itself with rdp (to localhost)?

>>>> Can you connect using the IP number in stead of the server

>>>> name? Also check the Network settings in the rdp-tcp

>>>> connection. Is it listening on all NICs? Is the number of

>>>> allowed connections correct ( > 0 )?

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>> TS troubleshooting: http://ts.veranoest.net

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> Hi Vera,

>>>>>

>>>>> Yes the server is listening on port 3389. I deleted the

>>>>> connection and re-created it but clients are still getting:

>>>>>

>>>>> The client could not connect to the remote computer.

>>>>> Remote connections might not be enabled or the computer

>>>>> might be too busy to accept new connections.

>>>>> Please try again connecting later.

>>>>>

>>>>> Any ideas?

>>>>>

>>>>> Thanks

>>>>> Tony

>>>>>

>>>>>

>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>>> wrote in message

>>>>> news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

>>>>>> Is the server listening on port 3389? Use "netstat -an" to

>>>>>> check. If it isn't, and I expect that it isn't, then I

>>>>>> would delete the rdp- tcp connection and create a new one,

>>>>>> in Terminal Services Configuration. Then reboot the server

>>>>>> and try again.

>>>>>> _________________________________________________________

>>>>>> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>>

>>>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>>>> microsoft.public.windows.terminal_services:

>>>>>>

>>>>>>> Hi all,

>>>>>>>

>>>>>>> I had a hard drive failure on a windows 2003 Terminal

>>>>>>> Server w/SP2.. I used the ASR recovery process once the

>>>>>>> hard drive was replaced to recover. All the files were

>>>>>>> restored but now the Terminal will not accept Remote

>>>>>>> connections. Any ideas:? I get the error that the

>>>>>>> terminal server is not responding and that it is too busy

>>>>>>> and to try back later. All files and services appear to be

>>>>>>> functioning normal.

>>>>>>>

>>>>>>> Any help would be appreciated.

>>>>>>> Thanks

>>>>>>> TR

  • 2 weeks later...
Guest TR

Guest TR

Posted
Posted

Re: no RDP after a restore

 

Vera

 

What i did to fix it was change the setting on the NIC IP from fixed to

dynamic and let the domain controller issue the ip to the terminal server

and then I set it back to the original fixed IP.....for whatever reason,

that fixed the problem.

 

TR

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99E2F1E064D04veranoesthemutforsse@207.46.248.16...

> Sorry, that's what I meant: make sure it is disabled.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "TR" <TR@somehwere.com> wrote on 08 nov 2007 in

> microsoft.public.windows.terminal_services:

>

>> How do i check to see if the windows firewall is causing the

>> problem? I don't believe it is enabled.

>>

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns99E2E3983B440veranoesthemutforsse@207.46.248.16...

>>> Mmm, only other thing that I can think of is the Windows

>>> firewall.

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "TR" <TR@somehwere.com> wrote on 08 nov 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hi Vera,

>>>>

>>>> There are no unusual errors in the event log that I can see.

>>>> As a matter of fact it is fairly clean.

>>>>

>>>> When I am logged into the administrator console of the

>>>> TERMINAL I can connect to localhost, the NETBIOS name, the

>>>> FQDN and the raw IP using the Remote desktop, but I cannot

>>>> connect to the TREMINAL server via RDP from any other machine

>>>> on the network. I have checked Network settings and everything

>>>> looks fine. At the administrator console I can connect to

>>>> anywhere in the network, I can surf the internet and I can

>>>> connect to all available shares. I can manage the TERMINAL

>>>> from the Domain controller and I can ping it and get valid

>>>> reponses. All programs work. Any other ideas before I decide

>>>> to make a backup of the files, wipe the machine and start from

>>>> scratch?

>>>>

>>>> Thanks

>>>> TR

>>>>

>>>> It's never like they tell you.. :(

>>>>

>>>>

>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>> wrote in message

>>>> news:Xns99E1AD34FAD1Cveranoesthemutforsse@207.46.248.16...

>>>>> OK, that's good news.

>>>>> Next thing to try:

>>>>> Any errors in the EventLog on the server?

>>>>> Can you connect from the console of the server to the server

>>>>> itself with rdp (to localhost)?

>>>>> Can you connect using the IP number in stead of the server

>>>>> name? Also check the Network settings in the rdp-tcp

>>>>> connection. Is it listening on all NICs? Is the number of

>>>>> allowed connections correct ( > 0 )?

>>>>>

>>>>> _________________________________________________________

>>>>> Vera Noest

>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>

>>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>>> microsoft.public.windows.terminal_services:

>>>>>

>>>>>> Hi Vera,

>>>>>>

>>>>>> Yes the server is listening on port 3389. I deleted the

>>>>>> connection and re-created it but clients are still getting:

>>>>>>

>>>>>> The client could not connect to the remote computer.

>>>>>> Remote connections might not be enabled or the computer

>>>>>> might be too busy to accept new connections.

>>>>>> Please try again connecting later.

>>>>>>

>>>>>> Any ideas?

>>>>>>

>>>>>> Thanks

>>>>>> Tony

>>>>>>

>>>>>>

>>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>>>> wrote in message

>>>>>> news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

>>>>>>> Is the server listening on port 3389? Use "netstat -an" to

>>>>>>> check. If it isn't, and I expect that it isn't, then I

>>>>>>> would delete the rdp- tcp connection and create a new one,

>>>>>>> in Terminal Services Configuration. Then reboot the server

>>>>>>> and try again.

>>>>>>> _________________________________________________________

>>>>>>> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>>>

>>>>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>>>>> microsoft.public.windows.terminal_services:

>>>>>>>

>>>>>>>> Hi all,

>>>>>>>>

>>>>>>>> I had a hard drive failure on a windows 2003 Terminal

>>>>>>>> Server w/SP2.. I used the ASR recovery process once the

>>>>>>>> hard drive was replaced to recover. All the files were

>>>>>>>> restored but now the Terminal will not accept Remote

>>>>>>>> connections. Any ideas:? I get the error that the

>>>>>>>> terminal server is not responding and that it is too busy

>>>>>>>> and to try back later. All files and services appear to be

>>>>>>>> functioning normal.

>>>>>>>>

>>>>>>>> Any help would be appreciated.

>>>>>>>> Thanks

>>>>>>>> TR

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Posted
Posted

Re: no RDP after a restore

 

Strange! But well done of you to find the solution, and thanks for

letting us know!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"TR" <TR@somehwere.com> wrote on 21 nov 2007 in

microsoft.public.windows.terminal_services:

> Vera

>

> What i did to fix it was change the setting on the NIC IP from

> fixed to dynamic and let the domain controller issue the ip to

> the terminal server and then I set it back to the original fixed

> IP.....for whatever reason, that fixed the problem.

>

> TR

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99E2F1E064D04veranoesthemutforsse@207.46.248.16...

>> Sorry, that's what I meant: make sure it is disabled.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "TR" <TR@somehwere.com> wrote on 08 nov 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> How do i check to see if the windows firewall is causing the

>>> problem? I don't believe it is enabled.

>>>

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>> wrote in message

>>> news:Xns99E2E3983B440veranoesthemutforsse@207.46.248.16...

>>>> Mmm, only other thing that I can think of is the Windows

>>>> firewall.

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>> TS troubleshooting: http://ts.veranoest.net

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> "TR" <TR@somehwere.com> wrote on 08 nov 2007 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> Hi Vera,

>>>>>

>>>>> There are no unusual errors in the event log that I can see.

>>>>> As a matter of fact it is fairly clean.

>>>>>

>>>>> When I am logged into the administrator console of the

>>>>> TERMINAL I can connect to localhost, the NETBIOS name, the

>>>>> FQDN and the raw IP using the Remote desktop, but I cannot

>>>>> connect to the TREMINAL server via RDP from any other

>>>>> machine on the network. I have checked Network settings and

>>>>> everything looks fine. At the administrator console I can

>>>>> connect to anywhere in the network, I can surf the internet

>>>>> and I can connect to all available shares. I can manage the

>>>>> TERMINAL from the Domain controller and I can ping it and

>>>>> get valid reponses. All programs work. Any other ideas

>>>>> before I decide to make a backup of the files, wipe the

>>>>> machine and start from scratch?

>>>>>

>>>>> Thanks

>>>>> TR

>>>>>

>>>>> It's never like they tell you.. :(

>>>>>

>>>>>

>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>>> wrote in message

>>>>> news:Xns99E1AD34FAD1Cveranoesthemutforsse@207.46.248.16...

>>>>>> OK, that's good news.

>>>>>> Next thing to try:

>>>>>> Any errors in the EventLog on the server?

>>>>>> Can you connect from the console of the server to the

>>>>>> server itself with rdp (to localhost)?

>>>>>> Can you connect using the IP number in stead of the server

>>>>>> name? Also check the Network settings in the rdp-tcp

>>>>>> connection. Is it listening on all NICs? Is the number of

>>>>>> allowed connections correct ( > 0 )?

>>>>>>

>>>>>> _________________________________________________________

>>>>>> Vera Noest

>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>>

>>>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>>>> microsoft.public.windows.terminal_services:

>>>>>>

>>>>>>> Hi Vera,

>>>>>>>

>>>>>>> Yes the server is listening on port 3389. I deleted the

>>>>>>> connection and re-created it but clients are still

>>>>>>> getting:

>>>>>>>

>>>>>>> The client could not connect to the remote computer.

>>>>>>> Remote connections might not be enabled or the computer

>>>>>>> might be too busy to accept new connections.

>>>>>>> Please try again connecting later.

>>>>>>>

>>>>>>> Any ideas?

>>>>>>>

>>>>>>> Thanks

>>>>>>> Tony

>>>>>>>

>>>>>>>

>>>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>

>>>>>>> wrote in message

>>>>>>> news:Xns99E176FD4E431veranoesthemutforsse@207.46.248.16...

>>>>>>>> Is the server listening on port 3389? Use "netstat -an"

>>>>>>>> to check. If it isn't, and I expect that it isn't, then I

>>>>>>>> would delete the rdp- tcp connection and create a new

>>>>>>>> one, in Terminal Services Configuration. Then reboot the

>>>>>>>> server and try again.

>>>>>>>> _________________________________________________________

>>>>>>>> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

>>>>>>>> TS troubleshooting: http://ts.veranoest.net

>>>>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>>>>

>>>>>>>> "TR" <TR@somehwere.com> wrote on 07 nov 2007 in

>>>>>>>> microsoft.public.windows.terminal_services:

>>>>>>>>

>>>>>>>>> Hi all,

>>>>>>>>>

>>>>>>>>> I had a hard drive failure on a windows 2003 Terminal

>>>>>>>>> Server w/SP2.. I used the ASR recovery process once the

>>>>>>>>> hard drive was replaced to recover. All the files were

>>>>>>>>> restored but now the Terminal will not accept Remote

>>>>>>>>> connections. Any ideas:? I get the error that the

>>>>>>>>> terminal server is not responding and that it is too

>>>>>>>>> busy and to try back later. All files and services

>>>>>>>>> appear to be functioning normal.

>>>>>>>>>

>>>>>>>>> Any help would be appreciated.

>>>>>>>>> Thanks

>>>>>>>>> TR

 Share
Go to topic listing
×
×
  • Create New...