Carrying on from my previous post Terminal Services And Remote Access Trouble I have another Terminal Services (S) & Remote Desktop (RD) issue on another server. This time I simply can't connect to the server at all. The RD client gives the following error:
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 the network problems are preventing your connection.
Please try connecting again later. If the problem continues to occur, contact your administrator.
I get OK & Help buttons. The help is useless ;-) I have contacted my administrator. I was no help either.
And the following error from the Terminal Services Client:
The client could not connect to the Terminal serve. The server may be too busy. Please try connecting later
I think the same team were responsible for RD & TS help files.
I then thought I knew what the issue was. The registry. Basically if I look at the registry entry for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService its obviously corrupted. The exported key was:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService]
"ErrorControl"=dword:00000001
"ObjectName"="LocalSystem"
"Type"=dword:00000010
"Description"="Provides a multisession environment that allows client devices to access a virtual Windows 2000 Professional desktop session and Windows-based programs running on the server."
"DisplayName"="Terminal Services"
Comparing this entry to ones in other, working serves showed the key to appear incomplete.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService]
"Start"=dword:00000002
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,74,\
00,65,00,72,00,6d,00,73,00,72,00,76,00,2e,00,65,00,78,00,65,00,00,00
"ObjectName"="LocalSystem"
"Type"=dword:00000010
"Description"="Provides a multisession environment that allows client devices to access a virtual Windows 2000 Professional desktop session and Windows-based programs running on the server."
"DisplayName"="Terminal Services"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters]
"UseLicenseServer"=dword:00000000
"fInternetConnector"=dword:00000000
"Certificate"=hex:01,00,00,00,01,00,00,00,01,00,00,00,06,00,5c,00,52,53,41,31,\
48,00,00,00,00,02,00,00,3f,00,00,00,01,00,01,00,99,d3,52,ed,f0,c7,61,2e,a8,\
cd,eb,dd,f6,a3,d2,12,e9,fd,fd,e8,5e,bb,a8,eb,bf,01,bc,04,ae,b2,e5,9c,92,7a,\
7c,02,11,22,f7,db,e5,e1,34,91,03,fb,ec,f9,73,19,76,a4,86,3c,cf,7b,5f,f0,fb,\
86,6d,22,f5,bb,00,00,00,00,00,00,00,00,08,00,48,00,e0,00,de,ec,96,56,61,26,\
07,0f,4a,22,30,c6,8c,c3,ed,6d,d5,23,64,ec,34,b6,d9,b5,f1,d6,4b,bb,78,4b,c3,\
e5,74,c8,6a,5a,9d,0a,8d,66,e9,6c,ca,d8,f5,39,cd,8b,73,3d,f8,16,52,c4,18,21,\
52,05,b2,c1,0e,1d,00,00,00,00,00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Performance]
"Close"="CloseTSObject"
"Collect Timeout"=dword:000003e8
"Collect"="CollectTSObjectData"
"Open Timeout"=dword:000003e8
"Open"="OpenTSObject"
"Library"="perfts.dll"
"Last Counter"=dword:00005af8
"Last Help"=dword:00005af9
"First Counter"=dword:00005a78
"First Help"=dword:00005a79
"Object List"="23160 23282"
"WbemAdapFileTime"=hex:00,20,2b,88,67,40,bf,01
"WbemAdapFileSize"=dword:00003110
"WbemAdapStatus"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Enum]
"0"="Root\\LEGACY_TERMSERVICE\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001
Seeing the huge difference in the registry entries I decided the best policy would be to try and re-create he correct key entries so I uninstalled and re-installed TS via Add/Remove Windows Components. No effect. I also tried to manually enter the keys taken from another server. However, when I tried to manually add the Parameters sub key using RegEdit I got the error message Cannot rename New Key #1: The specified key name already exists. Type another name and try again.. Needless to say the key does not exist as a sub key of TermService. I then un-installed TS and tried to delete the entire TermService key. Whenever I do that using RegEdit I get the pretty useless error message Cannot delete TermService: Error while deleting key.. Using CoolReg I get the more useful error message of Access Denied. I changed permissions, booted to safe mode, booted to command prompt safe mode to try and delete the key all to no avail. I've even tried importing a registry key from a working server in. Again no joy. One interesting point is that all the subkeys bar the Parameters sub key imported.
At this point I thought I'd check if for some reason the actual service wasn't started and found to my dismay the problem was more profound than that. The service wasn't even listed in Services. I have given in for now. I know when I'm beaten ;-) Re-installing the OS isn't really an option. If anyone has any ideas how to get the Terminal Services service registered again let me know!