{"action":"closed","issue":{"url":"https://api.github.com/repos/CoreSecurity/impacket/issues/101","repository_url":"https://api.github.com/repos/CoreSecurity/impacket","labels_url":"https://api.github.com/repos/CoreSecurity/impacket/issues/101/labels{/name}","comments_url":"https://api.github.com/repos/CoreSecurity/impacket/issues/101/comments","events_url":"https://api.github.com/repos/CoreSecurity/impacket/issues/101/events","html_url":"https://github.com/CoreSecurity/impacket/issues/101","id":112815059,"number":101,"title":"secretsdump DRSUAPI \"Connection reset by peer\" on very large dumps","user":{"login":"wintermute4316","id":9419064,"avatar_url":"https://avatars.githubusercontent.com/u/9419064?v=3","gravatar_id":"","url":"https://api.github.com/users/wintermute4316","html_url":"https://github.com/wintermute4316","followers_url":"https://api.github.com/users/wintermute4316/followers","following_url":"https://api.github.com/users/wintermute4316/following{/other_user}","gists_url":"https://api.github.com/users/wintermute4316/gists{/gist_id}","starred_url":"https://api.github.com/users/wintermute4316/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wintermute4316/subscriptions","organizations_url":"https://api.github.com/users/wintermute4316/orgs","repos_url":"https://api.github.com/users/wintermute4316/repos","events_url":"https://api.github.com/users/wintermute4316/events{/privacy}","received_events_url":"https://api.github.com/users/wintermute4316/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-10-22T14:28:23Z","updated_at":"2016-02-09T21:23:58Z","closed_at":"2016-02-09T21:23:58Z","body":"When dumping hashes from a very large DC database using the drsuapi method the following error occurs after several thousand hashes have already been successfully been dumped.\r\n\r\n[-] [Errno 104] Connection reset by peer\r\n[\\*] Something wen't wrong with the DRSUAPI approach. Try again with -use-vss parameter\r\n[\\*] Cleaning up...\r\n[-] 'int' object has no attribute 'disconnectTree'\r\n[*] Cleaning up...\r\n\r\nThe error states that the \"connection was reset by peer\", however the DC that I'm dumping from is fine and if I run again immediately after this error, it starts over again and then fails again in a different place on the list of hashes after many thousands (7k-10k) of hashes have been successfully dumped. Could this be a timeout issue and if so, can a timeout or retry option be added to allow for server side or DRSUAPI hiccups?\r\n\r\nAlso on a separate issue, when saving the data to disk using the -outputfile parm, if the dump is interrupted/fails in the middle by something like above, no hashes are saved to disk.  Seems that secretsdump won't save until all hashes have been dumped successfully, but would be better to save as you go.\r\n\r\nI saw a previous post by Mubix that it would be great to resume on failure when a very large dump is occurring.  A resume would also help fix this issue."}}