Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Im running Red Hat Linux Enterprise 4 as a Gateway/Firewall with samba 3.0.10.
| GW FW HTTP SMB ...|
| NIC: 192.168.2.1
| | NIC: 192.168.2.2
WINDOWS XP client --------
NIC: 192.168.2.50 | router |
| NIC: 192.168.3.1
WINDOWS XP client
From 192.168.2.50 I can access the shared samba folders but form 192.168.3.2 I cannot.
The Firewall configuration accepts input, output and forward by default and it is not running dhcp and DNS services. Everyone has inet access.
My smb.conf file is:
workgroup = MYGROUP
server string = Samba Server
host allow = 192.168.1. 192.168.2. 192.168.3. 127.
security = share
interfaces = 192.168.2.1/24 192.168.1.2/24
remote browse sync = 192.168.1.255 192.168.2.255 192.168.3.255
remote announce = 192.168.1.255/MYGROUP 192.168.2.255/MYGROUP 192.168.3.255/MYGROUP
local master = yes
domain master = yes
preferred master = yes
wins support = yes
dns proxy = no
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bind/false
winbind use default domain = no
comment = Test
path = /export/samba/test (chmod 777)
browseable = yes
read only = no
guest ok = yes
public = yes
Why I dont see the shared folders from 192.168.3.0 network?
Distribution: suse, opensuse, debian, others for testing
you need to make sure that broadcasts actually get to the 192.168.3.x network. I don't think this is standard routing behaviour.
here's a way to solve it posted on a samba mailing list. basically you need to put a 2nd samba server in the 192.168.3.x subnet that syncs with your main samba server and communicates with the xp clients there.
Thanks rtspitz. I need to make it works with only one samba server. Hope someone can shed some ligth on this, meanwhile Im trying with different routers to see if I can broadcast to 192.168.3.0 (thanks for the advice).