Yes Option A: I have solved the issue. I was using samba in version 10.1 of Linux and is requires many destination Ports to be manually opened in a Suse 10.2 Workstation ( I should update 10.1 Workstation and hence version of Samba to offset this issue.
ALL working Fine. The Samba Server running on 10.1 allows me to see all workgroups from the 10.2 Regards Scott James Watkins wrote: > On Saturday 14 April 2007 02:20, Registration Account wrote: > >> I have set up a samba server all o.k. I cannot even view any workgroup. >> This is a result of internal security which I control. I was of the >> belief that Samba uses Netbios for transmitting and advertising on the >> LAN and have enabled TCP/UDP 137-139 on the required route >> 192.168.100.0/24 that the workstations are on that I want Samba services >> to be available. >> > > Are you saying that: > > a) You have a linux machine that you are using to browse the network for > Windows shares and you cannot 'see' any workgroups or domains. > > or > > b) You have a linux machine that you are using to serve files to Windows > clients using Samba and the Windows machines cannot 'see' your linux box. > > If the answer is a), you may find that inserting the ip_conntrack_netbios_ns > module helps. After looking at the output of tcpdump it looks like the > following is happening, your browsing software broadcasts UDP packets on > destination port 137 using a randomly chosen source port above 1024 and the > Windows machines in the network reply using this same port as the destination > port. Therefore, allowing these returned packets through your firewall is > not a simple matter of opening any one specific port, hence the need for the > connection tracking module. > > If the answer is b), not having nmbd running could be the problem. > > BTW, I recommend using tcpdump to look at the network traffic when attempting > to diagnose network problems, it's very useful. > > HTH, > James. >
smime.p7s
Description: S/MIME Cryptographic Signature
