Re: No RDP connection possible to win2k3 server in Remote Adminis

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

amzd <Andreas.meyer@xxxxxxxxxxxx> wrote on 23 feb 2009:

On 21 Feb., 00:39, Samhain_Knight <samhain.kni...@xxxxxxxxx>
wrote:
Are you getting the following error in your system log?

1014 TermServices
 Cannot load illegal module:
"C:\windows\system32\drivers\rdpwd.sys"

I suddendly lost RDP connectivity to a Windows 2003 Server SP2
& XP Pro S
P3
Box. I noticed that error in the event log. I copied rdpwd.sys
from anoth
er
server that RDP was working properly, I replaced it, then
rebooted the server. This fixed it for me and I could RDP into
the systems again.

Hope this helps.



"Vera Noest [MVP]" wrote:
Not sure if it helps, but check this:

My Terminal Server does not respond after a reboot. How do I
solve this?
http://ts.veranoest.net/ts_faq_connectivity.htm#no_access_after
_reb
oot
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:  http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

amzd <Andreas.me...@xxxxxxxxxxxx> wrote on 20 feb 2009 in
microsoft.public.windows.terminal_services:

On 20 Feb., 16:16, amzd <Andreas.me...@xxxxxxxxxxxx> wrote:
Ok, here in englisch:
The error message when trying to connect to the 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. It is also
possible that network problems are preventing your
connection. Please try connecting again later. If the
problem continues to occur, contact your administrator."

I am the admin, of course.
Ich have a little farm with Win2k3 Servers.
7 server run in Remote Administration Mode. Recently I
installed SP2 und Hoffixes.
After installing SP2 on one machine, I could not reach it
anymore through RDP.
All others were OK. At first the port 3389 was still being
listened (netstat ?aon), yet I could not get on the
machine with Rdp. The server was kind of busy so I
dismounted some Oracle instances. Ram was freed, but to no
avail.

Terminalservices is oviously managed by a svchost that
does not do anything else. Since the service
Terminalservices cannot be manually stopped I killed the
corresponding svchost in taskmanager (found out with
wmic...). Then I started again Terminal services. To no
avail. There was a message in eventlog after I killed the
svchost and after I restarted the service there were two
messages confirming that it was started OK.

Ping to the server was OK, I could connect the hidden
Admin-Share (c $)
telnet Servername 3389 ==> did not work:
Coult not open connection: Connect failed

With the other servers it did work (blinking Telnet
window).

I switched the machine from RemoteAdministration Mode to
Terminal server mode and restarted the machine. To no
avail.

I set the machine back to Remote Administration Mode
(hoping that would fix s.th.), installed all current
Hotfixes and restarted. No change.
Now the port 3389 was not being listened to any more.

I deleted in tscc.msc the RDP-Tcp, rebooted the server,
then created RDP-Tcp again, rebooted the Server, no
change.

I verified, that in %SystemRoot%\System32\Drivers the
files Termdd.sys und Rdpwd.sys were present.
I verified, that in  %SystemRoot%\System32 the files
Rdpdd.dll and Rdpwsx.dll were present.
These files were of same size and date as on the other
servers. Just to make sure I finally copied these files on
to this server again. In
HKEY_Local_Machine\System\CurrentControlSet\Services\TermDD
the value for Start was set to 1 ? the same as with the
other servers, so it must be correct for Remote
Administration mode. I de-activated the Windows Firewall.
No change.

So, what is wrong here?
Port 3389 is not being listened to anymore by the server
(netstat ? aon).
At what point is the server being told to listen to port
3389 for RDP?
Why doesn't it work and why is there no error message or
event log message?
The server works otherwise OK, just no RDP connections
anymore.

Thank you for fresh ideas that get it working again.

Andreas

Now the message has changed somewhat to:
This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact
theowner of the remote computer or your network
administrator.

Sincerely
Andreas- Zitierten Text ausblenden -

- Zitierten Text anzeigen -


Hello,
I stood next to the server during reboot.
There are no error messages in the log.
When I let the server do its reboot there is no entry in
eventlog that TerminalServices have been started.
This obviously only occurs when I kill the service and then
restart it.
In
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServi
ce
\DependOnService
the entries are now:
RPCSS
TermDD
Still no RDP-Session possible.
Can't be because the server does not listen to 3389.
When and where is it being told to listen to the RDP port?
Why is there no error message when TermServices start but the
port is not being listened to?
S.th. goes wrong but is not recognized...
So what can I do?
Please don't tell me "re-install the server..."
All seems fine, just RDP isn't.

Sincerely
Andreas

I'm not sure, but I think that initially, after installing SP2,
your server suffered from the problem described here:

948496 - An update to turn off default SNP features is available
for Windows Server 2003-based and Small Business Server 2003-based
computers
http://support.microsoft.com/kb/948496/

since that fits your description: After installing SP2 ... I could
not reach it through RDP.... At first the port 3389 was still being
listened on.... The server was kind of busy.

Obviously, the situation has deteriorated after that, because now
it doesn't even listen anymore. To be honest, I've no idea what you
could do that you haven't already tried. Maybe apply SP2 once more,
and then the hotfix from 948496?
If that doesn't solve it, I think you will either have to call
Microsoft Support or re-install.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
.

Relevant Pages

  • Re: SBS 2003 IIS BASED SERVICES FAIL INTERMITTENTLY
    ... If I read your post correctly, you have a switch where the SBS ... Run DHCP server on your SBS, and set all client machine nics to dynamic. ... Once you have your nics configured, run the Connect to the Internet wizard, ... QUESTION1 - what is REFUSING CONNECTIONS? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... So far everything is good and now I'm just monitoring my exchange. ... get the SMTP service to stop hanging in the first place. ... won't have dead connections. ... work for now until I put into production new server hardware with sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2004 problem
    ... Remote connections might not be enabled or the computer might be too busy to ... I cannot ping to the workstation, but from the local lan yes. ... RDP to the server but not to the workstations. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2004 problem
    ... Remote connections might not be enabled or the computer might be too busy ... I cannot ping to the workstation, but from the local lan yes. ... RDP to the server but not to the workstations. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... You really should go through the steps I posted and get the SMTP service to stop hanging in the first place. ... You'll be happier, you won't be clubbing your server every day with a kill script, and you won't have dead connections. ... You do *not* need to restart the server, ...
    (microsoft.public.windows.server.sbs)