SecuraBV/CVE-2020-1472

TimeoutError: WinError 10060

envy041878 opened this issue · 4 comments

not really sure what caused this error below:

Performing authentication attempts...
Traceback (most recent call last):
File "C:\Users\changh6087\AppData\Local\Programs\Python\Python37\lib\site-packages\impacket\dcerpc\v5\transport.py", line 315, in connect
self.__socket.connect(sa)
TimeoutError: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Users\changh6087\AppData\Local\Programs\Python\Python37\zerologon_tester.py", line 101, in
perform_attack('\\' + dc_name, dc_ip, dc_name)
File "C:\Users\changh6087\AppData\Local\Programs\Python\Python37\zerologon_tester.py", line 73, in perform_attack
rpc_con = try_zero_authenticate(dc_handle, dc_ip, target_computer)
File "C:\Users\changh6087\AppData\Local\Programs\Python\Python37\zerologon_tester.py", line 27, in try_zero_authenticate
binding = epm.hept_map(dc_ip, nrpc.MSRPC_UUID_NRPC, protocol='ncacn_ip_tcp')
File "C:\Users\changh6087\AppData\Local\Programs\Python\Python37\lib\site-packages\impacket\dcerpc\v5\epm.py", line 1237, in hept_map
dce.connect()
File "C:\Users\changh6087\AppData\Local\Programs\Python\Python37\lib\site-packages\impacket\dcerpc\v5\rpcrt.py", line 800, in connect
return self._transport.connect()
File "C:\Users\changh6087\AppData\Local\Programs\Python\Python37\lib\site-packages\impacket\dcerpc\v5\transport.py", line 318, in connect
raise DCERPCException("Could not connect: %s" % msg)
impacket.dcerpc.v5.rpcrt.DCERPCException: Could not connect: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

IzxxY commented

I have the same error.
Not sure if it's supposed to say this.

I am getting the same error after successfully testing 3 servers.

Looks like a Windows issue. Can you confirm this? Works on GNU/Linux.

As soon as I can get access to an unfrozen Linux box I will test it