I upgraded my Mikrotik cAP ac to version 7.14.2 yesterday (don’t remember which exact version I had before that). After the upgrade, I noticed that I cannot access the default SMB share /flash/pub, named pub, where I output the active clients list for my home automation script to fetch.
Everything is as before, the share is enabled and user ‘guest’ with password ‘guest’ has read access to the folder. However, trying to log in to \192.168.0.100\pub prompts me with a username and password, but refuses login because "password is incorrect’ even though I know it’s correct and also tested changing it several times.
Is there something I should check that I may have forgotten?
!) rose-storage - moved SMB service to the RouterOS bundle;
!) smb - removed legacy SMB service (replaced with newer and faster ROSE SMB service, compatible with SMB 2.1, SMB 3.0 and SMB 3.1.1);
I am sorry to say…
Have you tested the beta ?
And is it only Windows the problem exist ?
Windows can be little angry about the smb version, M$ have disable old versions, because of easy hacking issues.
And what I can see my Linux mount, mounts at version 3.1.1 see my another thread.
If you are very kind to Mikrotik you may try to grab some pcaps files so you can see the differences between LInux and Windows. PCAPS = Wireshark, tcpdump dump files. And with Windws what version do you use ???..winver.exe.
Looks like configuration is mixed up between old and new SMB implementation, something has gone wrong during upgrade. Normally it is not so, for others the upgrade has happened smoothly, but here something went wrong and now two SMB programs want to co-exist. I think the easiest fix is to do a reinstall with RouterOS 7.14.2 and configure SMB again. You can re-apply all the other config from your export via copy/paste, but leave out everything to do with SMB
This is rather odd. I tried accessing the device using ftp and it also fails login, but at least it shows that in the log. I have a user named ‘guest’ with set password, but login still fails with that password using Windows ftp or FileZilla.
Why do you have /ip pool1 same as pool2? It is not right.
You have one big mix in the IP firewall filter, “Input” and “forward” trafic are not indicated as it should be. In this way, traffic cannot work correctly.
Default configuration is always taken as a basis. Records responsible for incoming traffic are missing.
Example:
Input Chain - this section is responsible for incoming traffic.
Forward chain - this section is responsible for traffic passing through the router.
/ip firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=accept chain=input in-interface-list=LAN
add action=drop chain=input comment="drop all else"
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=forward comment="allow internet traffic" in-interface-list=LAN out-interface-list=WAN
add action=accept chain=forward comment="allow port forwarding" connection-nat-state=dstnat { disable or remove if not required }
add action=drop chain=forward comment="drop all else"
Got the same issue after upgrading to 7.14.3. Can’t connect to smb share from windows 10. It was working on version 6 before the upgrade.
Added input, forward and output firewall rules to allow all traffic to all tcp and upd ports (quite excessive, yes) and see the counters.
Still can’t open any of those ports - TCP 137,139,445, UDP 137,138 from my windows computer using telnet and nmap. Tried to re-create users and shares - no luck.
I’ve got RouterOS 7.8 on another mikrotik and SMB share there works perfectly so it’s not something related to my windows pc.
UPD: I’ve found that when I put something in SMB comment field (like “123”) and let it wait for 10-20 seconds then I am able to connect to the share. If I edit comment field and remove everything - it does not work. Tried that several times - remove and put, looks like it is the reason. Now it works.