The samba server also acts as the router. That is correct, a pc on subnet 1 cannot access a pc on subnet 2 through samba, but works fine using other protocols.
Both subnet 1 and subnet 2 have pc that run Windows 7 x64, or Windows XP, or Linux (usually Fedora 17). The server itself runs on Archlinux. >> It seems that WINS is not the problem. Then what is ? ________________________________ From: Gaiseric Vandal <[email protected]> To: [email protected] Sent: Thursday, January 3, 2013 11:02 PM Subject: Re: [Samba] Samba 3 master browser on two networks plus WINS Presumably pc on subnet1 does NOT need to access a share from 192.168.7.1 since it can access 192.168.5.1. Presumably pc on subnet2 does NOT need to access a share from 192.168.5.1 since it can access 192.168.7.1. If you have a dual homed server + a router between subnets your routing could get a little tricky when access shares on the "other subnet" IP of the samba server. Or is the samba server also the router? But to clarify your issue is that a /*single-homed client */ PC on subnet1 (e.g. LIVINGROOM) can not access shares on single-homed client PC on subnet2 (e.g. ACERJUNKI)- even though they can ping each other? It seems that WINS is not the problem. On 01/03/13 15:41, Gala Dragos wrote: > Subnet 1 : > 192.168.5.1/24, wins 192.168.5.1 > > subnet 2: > 192.168.7.1/24, wins 192.168.7.1 > > all pc are allocated ip's from their respective subnet via dhcp. > > a pc on subnet 1 cannot access a share from e pc on subnet 2, not even by ip. > Same happens from subnet 2 to subnet 1. > > > The firewall is setup as to allow all traffic between the 2 subnets, > effectively considering them as a single zone (I use shorewall as an UI to > iptables) > > I have not specified any ports in smb.conf, but I have binded samba to the > required ethernet interface. > > Here is the wins.dat. I can see references from both subnets. > >>>>>>>> wins.dat follows >>>>>> > VERSION 1 0 >> "WORKGROUP#1e" 1357503758 0.0.0.0 e4R >> "ARCHROUTEUSB#03" 1357503758 192.168.5.1 192.168.7.1 66R >> "WORKGROUP#00" 1357503758 0.0.0.0 e4R >> "ROUTERJUNKIE#03" 1357503758 192.168.5.1 192.168.7.1 64R >> "LIVINGROOM#20" 1357541821 192.168.5.91 64R >> "LINUXJUNKIE#00" 1357511721 192.168.5.118 64R >> "ROUTERJUNKIE#00" 1357503758 192.168.5.1 192.168.7.1 64R >> "ARCHROUTEUSB RO#03" 1357258441 192.168.5.1 192.168.7.1 64R >> "FUJILAPPY#20" 1357497461 192.168.7.16 64R >> "ARCHROUTEUSB#00" 1357503758 192.168.5.1 192.168.7.1 66R >> "WORKGROUP#1b" 1357503758 192.168.5.1 192.168.7.1 64R >> "LIVINGROOM#00" 1357541816 192.168.5.91 64R >> "LINUXJUNKIE#20" 1357511723 192.168.5.118 64R >> "ARCHROUTEUSB RO#20" 1357258441 192.168.5.1 192.168.7.1 64R >> "WORKGROUP#1c" 1357503758 192.168.5.1 192.168.7.1 e4R >> "ACERJUNKIE#00" 1357381531 192.168.7.15 64R >> "FUJILAPPY#00" 1357497461 192.168.7.16 64R >> "ACERJUNKIE#20" 1357381531 192.168.7.15 64R >> "ARCHROUTEUSB RO#00" 1357258441 192.168.5.1 192.168.7.1 64R >> "ARCHROUTEUSB#20" 1357503758 192.168.5.1 192.168.7.1 66R >> "ROUTERJUNKIE#20" 1357503758 192.168.5.1 192.168.7.1 64R >>>>>>>>>>>>>>> end wins.dat >>>>>>>>>> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
