Re: RDC Console connection locks up server

Hi, I have some suggestions just in case you haven't tried them already:

- Run SFC /scannow
- Run chkdsk c: /r
- Update video driver
- Update server firmware
- Run a repair install
- Run tstst.exe utility and examine output for anything strange. You need to download this utility from Microsoft, it is part of the Platform Support Reporting utilities, specifically Directory Services. By default it is installed in C:\WINDOWS\MPSReports\DirSvc\Bin. Sample output of tstst is included at the end of this message.
- Examine TS registry keys/values against a known good 2003 SP1 server. I would start with HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server

Please let me know if you have any questions.

-TP

Sample tstst.exe output, yours will differ some due to different configurations

Machine Name...............................TS86
Domain Name................................CONTOSO
Site Name..................................Default-First-Site-Name
IP Address.................................207.46.130.
System Dir.................................C:\WINDOWS\system32
ProductType................................VER_NT_DOMAIN_CONTROLLER
ProductSuite...............................VER_SUITE_TERMINAL TS Version.................................5.2
Is this a server machine?..................Its a Server
Is tsoc.log Present?.......................Passed
Did TsOC get CompleteInstallationMessage...Passed
Does ProductSuite Contain TS?..............Passed
Did OCM Install TSEnable...................Skipped Test
Is TSEnabled registry alright?.............Passed
Is Kernel TSEnabled?.......................Passed
Is Terminal Server Registry Ok?............Passed
GetWinstationList..........................Console, RDP-Tcp(3389)
Is TermServ Start Bit Ok?..................AutoStart
Is TermServ service running?...............Passed
Termsrv Service Command....................%SystemRoot%\System32\svchost.exe -k termsvcs
Is Listner session Present ?...............Passed
Is TermSrv in System Context?..............Passed
AreEffectiveConnectionAllowed..............Allowed
Are Connections Allowed?...................Yes
Are Remote Logons allowed by winlogon?.....Passed
Is RdpDr Installed Properly?...............Passed
Is RdpNP in NetProviders?..................Passed
Are Multipal Connections Allowed...........Yes
Are Video keys setup right?................Passed
What mode is Terminal Server set in?.......Application Server
What is permission Mode set to?............Its W2k Compatible
Check termdd signature.....................Passed
Check tdpipe signature.....................Passed
Check tdtcp signature......................Passed
Check rdpwd signature......................Passed
Check rdpdd signature......................Passed
Check rdpwsx signature.....................Passed
Is this a Beta System?.....................Its RTM

Unknown OS. Assume no grace period
Has Licence GracePeriod Expired............Its Not expired
Audio test.................................Passed
Details:Running in a session
Audio is not redirected
------------------------------------------------

Enumerating Licensing Servers (May take some time)........Passed, Found Some!
Extracting Related Events from Event Log...

End Sample

flouie wrote:
Yeah, nothing shows up in the eventlogs even with the debugging
turned on which I've already tried.

I happens on all client versions. Microsoft's answer was to
reinstall the OS which is not a viable solution.


.

Relevant Pages

  • Re: script to see whether nt4.0 server
    ... Sample output follows ... NT Member Server - Terminal Server ... Product Name: Microsoft Windows 2000 ... > i want to know whether searching via registry key for above is correct? ...
    (microsoft.public.windows.server.scripting)
  • Re: Help calculate checksum (newbie)
    ... Here's the sample output from server: ... I cannot figure out where this checksum come from, can anyone post a sample in vb.net or C#? ... Doesn't the packet description contain information on how to calculate the checksum? ...
    (microsoft.public.dotnet.languages.vb)
Loading