Hi,
I’m hoping that someone might have some suggestions on how I debug an install.
I have installed the community edition on Kali (WSL) on my windows laptop and have successfully ran scans, and see in the results messages for the hosts:
Detection Result
It was possible to log into the remote host using the SMB protocol.
I wanted to have a dedicated device for scans - so I took an Intel NUC and installed Kali and Greenbone. The Kali install on the NUC doesn’t seem to even try to scan using SMB, I can see on the WSL install successful SMB logins and CVE’s but not when I scan using exactly the same settings on the native Linux install.
I have tried logging in using smbclient and that works when I specify SMB2, after that I changed the settings in Samba to use SMB2 and SMB3 as the minimum version. This allowed be to login using smbclient.
If I look at the log files, on WSL I can see messages logged that contain SMB (using grep) but on the native Linux machine I don’t see anything.
I can use nc -vz [mytargetip] 445 and see that the port is open (as a test of some of the ports I have had to open on the windows firewall).
I have added exclusions for both the IPs in Windows Firewall for the local WSL IP and the native Linux IP on the NUC
I’m not sure what else to try - I don’t want to only be able to scan from WSL, and feel like I must have missed something when I installed Kali and Greenbone on the NUC.