Re: Scan to SMB
That's an excellent comparison.
Before I go any further, I want to give a shoutout to Print Whisperer for pointing me in the right direction because I was wasting time chasing pink elephants.
SMB is an application protocol. Keep that in the back of your mind.
Print Whisperer told me to pay attention to the "session" layer. He was right again. "Negotiate Protocol" happens at the "session" layer and is similar to the TCP/IP handshake in that this is how a session is negotiated and started/rejected.
Quick Note: These are the most frequently used Request/Response messages for SMB:
- Negotiate Protocol (SMB, SMB2, SMB3)
- Set Up Account
- Tree connect
- Create
-Read
-Write
-Close
-Tree Disconnect
I think every networker needs to learn to troubleshoot SMB up to Layer 4. But there may be times where we need to go higher.
It's now clear to me that it really isn't possible for a SMB scan to go to 2 folders on 2 computers on the same session. I need to look for the problem elsewhere.
That's an excellent comparison.
Before I go any further, I want to give a shoutout to Print Whisperer for pointing me in the right direction because I was wasting time chasing pink elephants.

SMB is an application protocol. Keep that in the back of your mind.
Print Whisperer told me to pay attention to the "session" layer. He was right again. "Negotiate Protocol" happens at the "session" layer and is similar to the TCP/IP handshake in that this is how a session is negotiated and started/rejected.
Quick Note: These are the most frequently used Request/Response messages for SMB:
- Negotiate Protocol (SMB, SMB2, SMB3)
- Set Up Account
- Tree connect
- Create
-Read
-Write
-Close
-Tree Disconnect
I think every networker needs to learn to troubleshoot SMB up to Layer 4. But there may be times where we need to go higher.
It's now clear to me that it really isn't possible for a SMB scan to go to 2 folders on 2 computers on the same session. I need to look for the problem elsewhere.
Comment