How did you open access to the server-manager interface?
If you've added a new local network in server-manger using "Security" / "Local networks" then the new local network should be included in
* the "hosts allow" declaration in /etc/samba/smb.conf
* the "local_chk" code in /etc/rc.d/init.masq so that traffic is accepted through the firewall
You can see what your server thinks the local network list looks like using either the db command or a perl command.
I created a non-existent network "192.168.1.0" on my server for demonstration purposes.
# db networks show
192.168.1.0=network
Mask=255.255.255.0
Router=192.168.200.18
192.168.200.0=network
Mask=255.255.255.0
SystemLocalNetwork=yes
# perl -e 'use esmith::NetworksDB; my $ndb = esmith::NetworksDB->open_ro; print join("\n",$ndb->local_access_spec) . "\n"'
127.0.0.1
192.168.1.0/255.255.255.0
192.168.200.0/255.255.255.0
Checking the actual code in the various config files:
# grep 'hosts allow' /etc/samba/smb.conf
hosts allow = 127.0.0.1 192.168.1.0/255.255.255.0 192.168.200.0/255.255.255.0
# grep '192.168.1' /etc/rc.d/init.d/masq
/sbin/iptables -A $NEW_local_chk -s 192.168.1.0/255.255.255.0 -j ACCEPT
/sbin/iptables --append FORWARD -s 192.168.1.0/255.255.255.0 -d 192.168.1.0/255.255.255.0 -j ACCEPT
/sbin/iptables --append FORWARD -s 192.168.200.0/255.255.255.0 -d 192.168.1.0/255.255.255.0 -j ACCEPT
/sbin/iptables --append FORWARD -s 192.168.1.0/255.255.255.0 -d 192.168.200.0/255.255.255.0 -j ACCEPT
If the SME configuration looks OK, there are still issues with getting SMB shares to work in a routed network. I found this post that provides suggestions for avoiding the issues:
http://www.tldp.org/HOWTO/SMB-HOWTO-12.htmlOther things to consider:
* Recent Windows 10 updates disabled SMB v1 used by SME 9.2 / Samba 3.6. There are procedures available online for enabling SMB v1 on the windows systems
* Samba may be looking for port 445, which is not enabled for Samba on SME 9.2 by default (more googling)