The Samba Wiki entry

[FullScale4Me]

What replaced NT1 was SMB2 and later SMB3. Both are faster (compressed data streams), more secure and (by design) more reliable due to using TCP only. Current implementations only use TCP port 445 with a teeny leak of whispers on UDP 137 if nmbd is installed and running. Going 'back' means a lot [more] of things to watch after. MOST of the common exploits that attack a PC with methods that run before the OS loads propagate locally via SMB1, many times bricking a PC firmware. Don't go there unless you can afford the risk!

@FullScale4Me Thank you for this very useful to know. I wasn't sure which ports to allow through UFW as I saw 139 mentioned as well, so allowed all traffic through from certain clients via their ips.

The GUFW app has 2 pre-configured Samba 'rules' (identical) that setup a ruleset for SMB1. Use a Simple Rule to set TCP on Port 445 for SMB 2/3 use.

The most ancient of SMB will use all the port range of 135-139 as UDP and some as TCP. Some of that was for WINS <--> Samba traffic IIRC. As time moved SMB to the NT1 'era' a lot of the TCP dropped.

Now just 137 and 138 UDP; 139 and 445 TCP. The 445 TCP was for support of 'NetBios over TCP' when a client supported enabling it (Windows NT - Win 8.1). This allowed older WINS Services on NT 3/4 IIRC to remain in place. These old memories have cobwebs in the cobwebs!

[FullScale4Me]

@FullScale4Me to be honest, I found wsdd flaky as hell and gave up on it. ( It seems to be problem all over.)

I struggled as well with Avahi and finally gave up on it as well.

My Google Fu to the rescue! I found a working WS-Discover daemon that run on *nix! https://github.com/gershnik/wsdd-native Working on Windows 10 here.

A Unix daemon that makes your Linux/macOS/BSD/illumos machine visible in Network view of Windows Explorer on newer versions of Windows. It implements WS-Discovery protocol that Windows now uses to discover machines on local network. It is a native daemon, written in C++.
...
There are a couple of similar projects available: wsdd written in Python and wsdd2 written in C. Neither of them, however, fully provides the features above.

[CharlesV]

@FullScale4Me to be honest, I found wsdd flaky as hell and gave up on it. ( It seems to be problem all over.)

I struggled as well with Avahi and finally gave up on it as well.

My Google Fu to the rescue! I found a working WS-Discover daemon that run on *nix! https://github.com/gershnik/wsdd-native Working on Windows 10 here.

A Unix daemon that makes your Linux/macOS/BSD/illumos machine visible in Network view of Windows Explorer on newer versions of Windows. It implements WS-Discovery protocol that Windows now uses to discover machines on local network. It is a native daemon, written in C++.
...
There are a couple of similar projects available: wsdd written in Python and wsdd2 written in C. Neither of them, however, fully provides the features above.

Very good!

[BitterTruth]

@CharlesV Fantastic tool! No wonder it works, you're not just scanning for every type of protocol but the OS type, guest access, ports etc too. This could easily be more than just a Samba Network Browser.

[FullScale4Me]

@CharlesV Fantastic tool! No wonder it works, you're not just scanning for every type of protocol but the OS type, guest access, ports etc too. This could easily be more than just a Samba Network Browser.

Sounds like something to be careful with on a corporate network. Fine for home

[CharlesV]

@CharlesV Fantastic tool! No wonder it works, you're not just scanning for every type of protocol but the OS type, guest access, ports etc too. This could easily be more than just a Samba Network Browser.

Thanks. When I started it I was interested in only smb, but there is so much more info that can be found, I kind of branched out. And this has been working very well for me.

[CharlesV]

@CharlesV Fantastic tool! No wonder it works, you're not just scanning for every type of protocol but the OS type, guest access, ports etc too. This could easily be more than just a Samba Network Browser.

Sounds like something to be careful with on a corporate network. Fine for home

Aye, I use a combination of an nmap probe, followed up with smbclient info and netbios info probs, along with an nslookup... all standard stuff on a real network, but yes I can see it being frowned upon by an unknowing admin.

[BitterTruth]

@CharlesV Ive been playing around with your script for a couple of hours now. In particular, Ive been trying to modify it to allow selecting an network interface.
The reason being that I have 2 VM's setup. A devuan one (smb client) and an alpine (smb server). When I try to run the script on the devuan VM, it defaults to a 10.0.0 network on eth0. This is the one that allows it to use the internet from the host, however the alpine one is on eth1 and 192.168 network.

I was hoping to be able to get it to allow me to pick an interface and then do a scan on that interface, but Ive been struggling.
Iḿ not much of a coder, so taking a leaf out of your book, I tried to get chatgpt to do it for me. Letś just say it was a good exercise in frustration. After almost being gradually driven nuts by it, I thought I´d throw in the towel and ask you to maybe add that feature in.

You might also consider giving your script itś own thread so others can test it out as well.

[Jerry3904]

I wonder if Claude wouldn't be a better AI to try. I've seen a number of tests (this one, for instance) that demonstrated its superiority specifically over ChatGPT for such areas.

<Here endeth my entire brain record about Claude or any other AI>

[CharlesV]

@BitterTruth Yes, I think putting that script into it's own thread is smart, I was thinking of that too when I posted it.

I had a version earlier on that I chose which network to scan on, but it seemed too clunky as I was 99% of the time looking at my regular network and not my vpn's, and the additional selection box slowed me down. When I have a little more time I will try to integrate that back in.

@Jerry3904 100% agreement. Claude seems to be far better than chatgpt for most things. I found chatgpt to be good helping smooth documents and such, but Claude rocks.

Also.. I should mention that Claude has let me down in many cases where I have tossed code at him, or asked for x, y, z . Some specifics can be done well when either an idea and starting code is handed out... but the best I have found either of them is to hand them something, let them help figure out some smaller part of it, and then integrate that code into what I am working on. So far, almost all "ask chat to build something" in code has failed or the code has been SO BAD that I would never run it.