-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Error: [Errno 104] Connection reset by peer #479
Comments
So this happens with only logging in on multiple hosts? No command execution or anything else? |
Every time when I do something with multiple hosts. Including login, various kinds of credential dumps, command execution, and the rest. |
So also simply logging in throws these exceptions? Or only when further command/logic execution? Could you also give me an exact command that fails, including the debug log? |
This is really mysterious to me. We need more debug info to dig into this. Let me push a branch which contains more detailed logging. Also do you have information about the domain/environment you are testing? Has one or more servers null auth enabled?
To further track down the problem we should test these two commits: If the first one is working i have an idea what one of the problems could be. You can install specific commits with pipx: If not, i would suspect the database to be the root problem. There might be issues with sqlalchemy (the backbone of the database). |
@Unreachabl after trying the two commits from the post before, please try the new branch: |
|
Could you provide a debug log from the third option? |
Could you retry with |
Hi, still trying to figure out why this is happening. Pushed some changes, could you try again when you have time? |
|
This does not make sense to me, i just moved code from one function to another. Could you retry? Still trying to figure out why this does not work in the main branch. If it doesn't work please retry with specifying manually |
increased the number of hosts to 35 - the error was reproduced |
@Unreachabl were you on the same network segment as the targets? I usually get Error 104 connection reset by peer from security products. Like, particularly when a client has multiple sites and I'm trying to connect to a host across a tunnel where they have their IPS functionality enabled on that link. It seems like sometimes it's good about stopping every attempt, and sometimes it's when you have a flurry of connections that they block it. I think that would explain why limiting the number of hosts resolves it for you too. |
I've thought about it too, but there are no security products on my network. In addition, the previous version of nxc works fine. |
Describe the bug
When performing an operation on a certain number of hosts (more than 5), the error "Connection Error: [Errno 104] Connection reset by peer" occurs. When reducing the number of hosts, the error does not occur. I tried to set timeouts, reduce the number of threads (-t), install jitter - to no avail.
In the previous version of pcbs (1.2.0.), this was not observed. This problem is repeated with different network configurations (with and without edr)
To Reproduce
Steps to reproduce the behavior i.e.:
Command:
netexec smb -id hosts-id 1
NetExec info
OS: Kali
Version of nxc: 1.3.0
Installed from: pipx install git+https://github.com/Pennyw0rth/NetExec
The text was updated successfully, but these errors were encountered: