connection.py timeout in _send_smb2_negotiate, line 1354 about smbprotocol HOT 5 CLOSED

Thanks @pacmanoth for the detailed info. Are you able to let me know the following bits of info;

• The OS version you are connecting to
• If you have something like Wireshark, do you see any packets being returned from the server after the initial negotiation request

When I first started working on this I found some libraries send an SMB v1 negotiate message first and then send an SMB v2 negotiate message with the true list of dialects the client supported if the first message responsed with the dialect wildcard value. I tested out quite a few scenarios and found that this wasn't required and removed this step to save on time and complexity, I assumed it was only needed if you wanted to support SMB v1 which I don't. Maybe I missed something and it is needed but I'm not sure.

from smbprotocol.

Thank you for your reply. Looks like the machines in question are probably Windows 2003 R2.
I am including the wireshark output from an attempt to connect to one of these machines. Note that the Source Machine is 137.65.57.227 and the Target is: 151.155.185.187
SMB Trace.zip

from smbprotocol.

Server 2003 only supports SMB v1 which is is not under the scope of this library unfortunately. SMB v1 is completely different and outdated compared to v2 and 3 and I have no plans on implementing it due to the various security issues associated with it.

from smbprotocol.

:-(

from smbprotocol.

Sorry to be the bearer of bad news but SMB v1 is just plain insecure and should be burned at the stake, even Microsoft has numerous articles explaining why and how to disable it on newer hosts. Unfortunately Server 2003 needs SMB v1 but as that has been out of support for a few years now there's not much I can do for you sorry.

from smbprotocol.