I have a strange scenario where after installing a Mikrotik CRS125-24G-1S-2HnD-IN, I've been unable to connect to my SMB shares from my Windows computers. My network looks something like this:
Previously I had just used the Rogers CODA Modem as a Router and during this configuration I was able to connect and setup the SMB shares on my Fedora Server without issue on both Windows Systems.
Since installing the MikroTik Cloud Router Switch, my Windows machines have been unsuccessful in finding the SMB shares. The Windows shares on my Windows machine do function, although upon initial setup it took a while for them to be found. I am able to ping the Fedora Server from both of my Windows machines and I'm able to SSH into it (as well as play Minecraft if that helps at all) over LAN. I have confirmed that the Samba Daemon is running on the Fedora Machine:
Code: Select all
[jupdown@Fedora-Server ~]$ systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2021-02-08 14:08:18 EST; 2h 17min ago
Code: Select all
[global]
workgroup = WORKGROUP
server string = Fedora-Server
server role = standalone server
hosts allow = 10.0.0. 127. #This line previously had 192.168.1. in it for the Rogers CODA configuration
Code: Select all
[admin@CRS125] > /export hide-sensitive
# feb/08/2021 16:48:20 by RouterOS 6.48
# software id = J0IH-TTY3
#
# model = CRS125-24G-1S-2HnD
/interface bridge
add admin-mac=4C:5E:0C:92:18:45 auto-mac=no comment=defconf name=bridge
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-g/n channel-width=20/40mhz-XX country=canada disabled=no distance=\
indoors frequency=auto installation=indoor mode=ap-bridge ssid="WifiName" wireless-protocol=802.11
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk mode=dynamic-keys supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=10.0.0.3-10.0.0.254
/ip dhcp-server
add address-pool=dhcp disabled=no interface=bridge name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=ether6
add bridge=bridge comment=defconf interface=ether7
add bridge=bridge comment=defconf interface=ether8
add bridge=bridge comment=defconf interface=ether9
add bridge=bridge comment=defconf interface=ether10
add bridge=bridge comment=defconf interface=ether11
add bridge=bridge comment=defconf interface=ether12
add bridge=bridge comment=defconf interface=ether13
add bridge=bridge comment=defconf interface=ether14
add bridge=bridge comment=defconf interface=ether15
add bridge=bridge comment=defconf interface=ether16
add bridge=bridge comment=defconf interface=ether17
add bridge=bridge comment=defconf interface=ether18
add bridge=bridge comment=defconf interface=ether19
add bridge=bridge comment=defconf interface=ether20
add bridge=bridge comment=defconf interface=ether21
add bridge=bridge comment=defconf interface=ether22
add bridge=bridge comment=defconf interface=ether23
add bridge=bridge comment=defconf interface=ether24
add bridge=bridge comment=defconf interface=sfp1
add bridge=bridge comment=defconf interface=wlan1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/ip address
add address=10.0.0.1/24 comment=defconf interface=bridge network=10.0.0.0
/ip dhcp-client
add comment=defconf disabled=no interface=ether1
/ip dhcp-server lease
# I've more or less statically allocated all my machines; nothing to see here
/ip dhcp-server network
add address=10.0.0.0/24 comment=defconf gateway=10.0.0.1 netmask=24
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=10.0.0.1 comment=defconf name=router.lan
/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=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
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=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
add action=dst-nat chain=dstnat dst-port=25565 in-interface=ether1 protocol=tcp to-addresses=10.0.0.200 \
to-ports=25565
add action=dst-nat chain=dstnat dst-port=25565 in-interface=ether1 protocol=udp to-addresses=10.0.0.200 \
to-ports=25565
/ip service
set www-ssl disabled=no
/ip smb
set allow-guests=no domain=WORKGROUP
/system clock
set time-zone-name=America/Toronto
/system identity
set name=CRS125
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
I also found another one suggesting that changing the IP address back to 192.168.0.# may resolve the issue (viewtopic.php?t=109015#p541383)... although I'd like to keep this option as a last resort if possible.
I'm not looking to do anything fancy, I just want to be able to access my SMB shares over LAN on the same Subnet. If anyone has an idea as to where I should start on figuring this issue out, please let me know!
