解决ORA-12170:TNS connect timeout occurred问题

公司服务器周末要加硬盘，周一来后应用连不上了。报错如下 报错： ORA-12170:TNS connect timeout occurred 

第一反应是监听没开：

1. 测试了一下， 连接超时没用ping 通

C:/Users/Administrator>tnsping brorcl

TNS Ping Utility for 64-bit Windows: Version 11.2.0.1.0 - Production on 15-6月 -2015 09:45:43

Copyright (c) 1997, 2010, Oracle.  All rights reserved.

已使用的参数文件:

D:/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora

已使用 TNSNAMES 适配器来解析别名

尝试连接 (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.14.147.112)(PORT = 42525)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = brorcl)))
TNS-12535: TNS: 操作超时

2. 我登陆到远程服务器上，查看了一下监听的状态

C:/Documents and Settings/Administrator>lsnrctl status

LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 15-6月 -2015 09:52:54

Copyright (c) 1991, 2010, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Production
Start Date                15-6月 -2015 09:36:02
Uptime                    0 days 0 hr. 16 min. 55 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   F:/app/Administrator/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File         F:/app/Administrator/product/11.2.0/dbhome_1/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=//./pipe/EXTPROC1521ipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=x3650m3)(PORT=47512)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=47512)))
Services Summary...
Service "BANKASSIST" has 1 instance(s).
  Instance "brorcl", status READY, has 1 handler(s) for this service...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "brorcl" has 2 instance(s).
  Instance "brorcl", status UNKNOWN, has 1 handler(s) for this service...