none
windows server 2012 远程连接黑屏,没有出现输入用户名和密码登陆框 RRS feed

  • 问题

  • 版主,您好!

     我的一台windwos server 2012服务器通过开通远程桌面进行管理,现在遇到一个问题。远程桌面过一段时间就出现黑屏,时间不确定,可能是一星期或者两个星期就会出现一次。每次必须重启动才可以连接。可以判断机器没有死,其他服务器都是正常的。烦请帮忙分析一下原因,谢谢!以下是截图。


    田辉

    2015年11月2日 8:55

全部回复

  • 这个最好是通过事件查看器去具体分析原因以解决它
    2015年11月3日 0:56
  • 您好,

    我是通过事件查看器查看的。没有错误或者警告信息,包括系统和应用程序。很是奇怪!


    田辉

    2015年11月3日 2:27
  • 是不是远程计算机弹出了 UAC 确认提示或者某些全屏显示的程序,可能会引起远程桌面黑屏。

    --
    Alexis Zhang
     
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
    本帖是回复帖,原帖作者是楼上的 "田辉"
     
    | 我的一台windwos server 2012服务器通过开通远程桌面进行管理,现在遇到一个问题。远程桌面过一段时间就出现黑屏,时间不确定,可能是一星期或者两个星期就会出现一次。每次必须重启动才可以连接。
    2015年11月3日 14:01
    版主
  • 没有弹出UAC确认,也不是某个程序全屏显示引起的。现在又发现一个问题,连接显示器登陆后,任务管理器调不出来,控制面板里面的许多项点击没响应。点击杀毒软件都调不出窗口,点击多啦,就显示windows进程错误,接着就无法进入资源管理器,只能重新启动机器解决。不知道是什么原因哎,隔一段时间就出现,比较烦人。

    田辉

    2015年11月4日 1:38
  • 没有弹出UAC确认,也不是某个程序全屏显示引起的。现在又发现一个问题,连接显示器登陆后,任务管理器调不出来,控制面板里面的许多项点击没响应。点击杀毒软件都调不出窗口,点击多啦,就显示windows进程错误,接着就无法进入资源管理器,只能重新启动机器解决。不知道是什么原因哎,隔一段时间就出现,比较烦人。

    田辉


    这些现象是通过远程桌面连接的远程计算机出现的?还是在连接了远程桌面的本地计算机出现的?
     
    它们仅在连接远程桌面时出现吗?在不运行远程桌面时是否会出现?

    --
    Alexis Zhang
     
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
    本帖是回复帖,原帖作者是楼上的 "田辉"
     
    | 没有弹出UAC确认,也不是某个程序全屏显示引起的。现在又发现一个问题,连接显示器登陆后,任务管理器调不出来,控制面板里面的许多项点击没响应。点击杀毒软件都调不出窗口,点击多啦,就显示windows进程错误,
    2015年11月5日 14:47
    版主
  • 只是在远程桌面的时候出现黑屏,没有弹出输入用户名和密码。本地登陆没有出现黑屏,但是有一个问题,资源管理器没有调出来。检查后台日志,发现错误信息,截图如下,估计和它有关系。使用wmidiag诊断出来信息,看不懂哎,都贴上来帮我分析一下原因,谢谢!

    39116 18:15:14 (0) ** WMIDiag v2.2 started on 2015年11月6日 at 18:05.
    39117 18:15:14 (0) ** 
    39118 18:15:14 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    39119 18:15:14 (0) ** 
    39120 18:15:14 (0) ** This script is not supported under any Microsoft standard support program or service.
    39121 18:15:14 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    39122 18:15:14 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    39123 18:15:14 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    39124 18:15:14 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    39125 18:15:14 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    39126 18:15:14 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    39127 18:15:14 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    39128 18:15:14 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    39129 18:15:14 (0) ** of the possibility of such damages.
    39130 18:15:14 (0) ** 
    39131 18:15:14 (0) ** 
    39132 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39133 18:15:14 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    39134 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39135 18:15:14 (0) ** 
    39136 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39137 18:15:14 (0) ** Windows Server 2012 R2 - No Service Pack - 64-bit (9600) - User 'xxxx' on computer 'xxxx'.
    39138 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39139 18:15:14 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
    39140 18:15:14 (0) ** INFO: => 10 possible incorrect shutdown(s) detected on:
    39141 18:15:14 (0) **          - Shutdown on 18 October 2014 09:22:31 (GMT-0).
    39142 18:15:14 (0) **          - Shutdown on 09 November 2014 09:15:15 (GMT-0).
    39143 18:15:14 (0) **          - Shutdown on 07 December 2014 23:24:06 (GMT-0).
    39144 18:15:14 (0) **          - Shutdown on 16 January 2015 02:32:30 (GMT-0).
    39145 18:15:14 (0) **          - Shutdown on 24 January 2015 08:19:03 (GMT-0).
    39146 18:15:14 (0) **          - Shutdown on 06 September 2015 06:57:15 (GMT-0).
    39147 18:15:14 (0) **          - Shutdown on 15 September 2015 11:41:04 (GMT-0).
    39148 18:15:14 (0) **          - Shutdown on 29 September 2015 01:16:23 (GMT-0).
    39149 18:15:14 (0) **          - Shutdown on 12 October 2015 08:41:33 (GMT-0).
    39150 18:15:14 (0) **          - Shutdown on 05 November 2015 01:37:11 (GMT-0).
    39151 18:15:14 (0) ** 
    39152 18:15:14 (0) ** System drive: ....................................................................................................... C: (#0 #1).
    39153 18:15:14 (0) ** Drive type: ......................................................................................................... IDE 

    (ST2000DM001-1CH164).
    39154 18:15:14 (0) ** There are no missing WMI system files: .............................................................................. OK.
    39155 18:15:14 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    39156 18:15:14 (0) ** WMI repository state: ............................................................................................... N/A.
    39157 18:15:14 (0) ** AFTER running WMIDiag:
    39158 18:15:14 (0) ** The WMI repository has a size of: ................................................................................... 33 MB.
    39159 18:15:14 (0) ** - Disk free space on 'C:': .......................................................................................... 128949 MB.
    39160 18:15:14 (0) **   - INDEX.BTR,                     4784128 bytes,      2015/11/6 18:14:24
    39161 18:15:14 (0) **   - MAPPING1.MAP,                  96564 bytes,        2015/11/6 16:13:54
    39162 18:15:14 (0) **   - MAPPING2.MAP,                  96564 bytes,        2015/11/6 18:08:24
    39163 18:15:14 (0) **   - OBJECTS.DATA,                  29065216 bytes,     2015/11/6 18:14:24
    39164 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39165 18:15:14 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    39166 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39167 18:15:14 (0) ** DCOM Status: ........................................................................................................ OK.
    39168 18:15:14 (0) ** WMI registry setup: ................................................................................................. OK.
    39169 18:15:14 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE

    (S)!
    39170 18:15:14 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    39171 18:15:14 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    39172 18:15:14 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    39173 18:15:14 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    39174 18:15:14 (0) **          this can prevent the service/application to work as expected.
    39175 18:15:14 (0) ** 
    39176 18:15:14 (0) ** RPCSS service: ...................................................................................................... OK (Already 

    started).
    39177 18:15:14 (0) ** WINMGMT service: .................................................................................................... OK (Already 

    started).
    39178 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39179 18:15:14 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    39180 18:15:14 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    39181 18:15:14 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    39182 18:15:14 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    39183 18:15:14 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    39184 18:15:14 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    39185 18:15:14 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    39186 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39187 18:15:14 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
    39188 18:15:14 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
    39189 18:15:14 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
    39190 18:15:14 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
    39191 18:15:14 (0) **         selecting 'Run as Administrator'.
    39192 18:15:14 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
    39193 18:15:14 (0) **         in the Task Scheduler within the right security context.
    39194 18:15:14 (0) ** 
    39195 18:15:14 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    39196 18:15:14 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    39197 18:15:14 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    39198 18:15:14 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    39199 18:15:14 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    39200 18:15:14 (0) ** 
    39201 18:15:14 (0) ** Overall DCOM security status: ....................................................................................... OK.
    39202 18:15:14 (0) ** Overall WMI security status: ........................................................................................ OK.
    39203 18:15:14 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    39204 18:15:14 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
    39205 18:15:14 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    39206 18:15:14 (0) **   'select * from MSFT_SCMEventLogEvent'
    39207 18:15:14 (0) ** 
    39208 18:15:14 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    39209 18:15:14 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 4 NAMESPACE

    (S)!
    39210 18:15:14 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    39211 18:15:14 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    39212 18:15:14 (0) ** - ROOT/MICROSOFTIISV2.
    39213 18:15:14 (0) ** - ROOT/SERVICEMODEL.
    39214 18:15:14 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    39215 18:15:14 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    39216 18:15:14 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    39217 18:15:14 (0) **    i.e. 'WMIC.EXE /NODE:"ALTOBEAMBJ" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    39218 18:15:14 (0) ** 
    39219 18:15:14 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    39220 18:15:14 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    39221 18:15:14 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 2 ERROR(S)!
    39222 18:15:14 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServicesSession, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    39223 18:15:14 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI 

    provider)'
    39224 18:15:14 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServicesSession, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    39225 18:15:14 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI 

    provider)'
    39226 18:15:14 (0) ** 
    39227 18:15:14 (0) ** WMI MOF representations: ............................................................................................ OK.
    39228 18:15:14 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    39229 18:15:14 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    39230 18:15:14 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    39231 18:15:14 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    39232 18:15:14 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    39233 18:15:14 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    39234 18:15:14 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    39235 18:15:14 (0) ** WMI static instances retrieved: ..................................................................................... 2092.
    39236 18:15:14 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    39237 18:15:14 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    39238 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39239 18:15:14 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    39240 18:15:14 (0) **   DCOM: ............................................................................................................. 0.
    39241 18:15:14 (0) **   WINMGMT: .......................................................................................................... 0.
    39242 18:15:14 (0) **   WMIADAPTER: ....................................................................................................... 0.
    39243 18:15:14 (0) ** 
    39244 18:15:14 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    39245 18:15:14 (0) **   DCOM: ............................................................................................................. 0.
    39246 18:15:14 (0) **   WINMGMT: .......................................................................................................... 0.
    39247 18:15:14 (0) **   WMIADAPTER: ....................................................................................................... 0.
    39248 18:15:14 (0) ** 
    39249 18:15:14 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    39250 18:15:14 (0) ** => This error is typically a WMI error. This WMI error is due to:
    39251 18:15:14 (0) **    - a missing WMI class definition or object.
    39252 18:15:14 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    39253 18:15:14 (0) **      You can correct the missing class definitions by:
    39254 18:15:14 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    39255 18:15:14 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    39256 18:15:14 (0) **            (This list can be built on a similar and working WMI Windows installation)
    39257 18:15:14 (0) **            The following command line must be used:
    39258 18:15:14 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
    39259 18:15:14 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    39260 18:15:14 (0) **            with WMI by starting the ADAP process.
    39261 18:15:14 (0) **    - a WMI repository corruption.
    39262 18:15:14 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    39263 18:15:14 (0) **      to validate the WMI repository operations.
    39264 18:15:14 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    39265 18:15:14 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    39266 18:15:14 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
    39267 18:15:14 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    39268 18:15:14 (0) **      the WMI repository must be reconstructed.
    39269 18:15:14 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    39270 18:15:14 (0) **          otherwise some applications may fail after the reconstruction.
    39271 18:15:14 (0) **          This can be achieved with the following command:
    39272 18:15:14 (0) **          i.e. 'WMIDiag ShowMOFErrors'
    39273 18:15:14 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    39274 18:15:14 (0) **          ALL fixes previously mentioned.
    39275 18:15:14 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    39276 18:15:14 (0) ** 
    39277 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39278 18:15:14 (0) ** WMI Registry key setup: ............................................................................................. OK.
    39279 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39280 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39281 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39282 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39283 18:15:14 (0) ** 
    39284 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39285 18:15:14 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    39286 18:15:14 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    39287 18:15:14 (0) ** 
    39288 18:15:14 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\ADMINISTRATOR\APPDATA

    \LOCAL\TEMP\WMIDIAG-V2.2_2K12R2.SRV.RTM.64_2015.11.06_18.05.47.LOG' for details.
    39289 18:15:14 (0) ** 
    39290 18:15:14 (0) ** WMIDiag v2.2 ended on 2015年11月6日 at 18:15 (W:119 E:93 S:1).


    田辉

    2015年11月9日 3:38