samba and network browsing / cross-subnet browsing / master browsers
John E Hein
jhein at fallschurch.esys.com
Fri Jan 23 17:11:36 GMT 1998
John Dong wrote at 17:29 -0500 on Jan 22:
> John,
>
> I saw your posting about brwosing problem. I have the exact same problem with samba. Sambas was set up as
> local master browser, however it could not find domain master browser, which limit its scope to its subnet only.
> All computer in the same subnet as samba only see computer in the same subnet.
>
> Do you resolve your problem yet ? I am interested in the response you got.
>
> Thanks,
>
> John Dong
> Lucent Technologies
> jdong at lucent.com
Nope, we haven't gotten it fixed. Simon Hyde responded
with one suggestion about 'os level' (he said to increase
the os level higher than the NTAS machine which, according
to BROWSING.txt, is 32). I tried that to no avail.
In reality, I don't really CARE who the domain or local master browsers are
(PCs or Samba), as long as a PC on one subnet can see a PC in the same
workgroup on a different subnet when browsing in the network neighborhood,
AND VICE-VERSA.
I have never been able to get this to occur. If anyone could
suggest a way to debug this or offer any possible reason to explain
this behavior, I'd be grateful. It's at least somewhat reassuring
that I'm not the only person who has suffered this problem.
Simon also suggested I make sure all the PCs are pointing to the
same NTAS WINS server (they are).
Is there anything special I should have to do on the NTAS WINS server
to make it serve browse lists for the workgroup I am interested in?
I don't have access to the WINS server - I chose not to make
our Samba server be a WINS server since it isn't able to speak
the replication protocol that allows WINS servers to replicate
to each other. So, since there is already an NTAS WINS server
on the net, I figured we could just use that?
Could there be a problem with a name duplication between my workgroup
and another workgroup or NT domain? Obviously I am grasping for
straws here, but I can't think of any reason I am unable to browse
across subnets for my workgroup.
> > domain master browser
> >
> > John E Hein (jhein at fallschurch.esys.com)
> > Thu, 18 Dec 1997 03:14:38 +1100
> >
> > * Messages sorted by: [ date ][ thread ][ subject ][ author ]
> > * Next message: Herb Lewis: "Re: SMB printing client driver data serving w/ Samba"
> > * Previous message: Edward Quillen: "SMB printing client driver data serving w/ Samba"
> > * Next in thread: Simon Hyde: "Re: domain master browser"
> >
> > If my samba server is NOT the domain or local master browser even though
> > I am trying to set it up that way, then which machine on the net is?
> > How do I find out?
> >
> > I'd like my Samba server (currently running 1.9.17p4) to be a Domain
> > Master Browser for a workgroup (let's call it 'ENGINEER').
> >
> > I set it up according to BROWSING.txt, but yet Windows NT/95 PCs on other
> > subnets are unable to browse and see computers on this subnet
> > (even if those PCs are also in the same workgroup).
> > Hmmm... why not? What could cause this?
> >
> > It appears that the Samba is not acting as the Domain Master Browser
> > ... at least as far as I can tell... and this is where I need
> > help in verification of my setup. Maybe it's just that there
> > is already a domain or local master browser selected when
> > I start Samba. If I give Samba a high 'os level', should it
> > immediately take over as a master browser or does it wait
> > until a current master browser gives that up?
> >
> > 192.207.166.161 (aka lorax) is the IP address of my samba server.
> >
> > Below is the output of nmblookup with debug level of 5.
> > Notice the [slightly misspelled] warning:
> > Warning: inconsistant interface 192.207.166.161
> > After looking at this code in nmblookup.c/interface.c, I am convinced this
> > is because of a minor bug in the code where the network mask is passed
> > in as 0.0.0.0
> > So, I don't think that has anything to do with my problem...
> > which again is that PCs in the same workgroup on other subnets
> > don't see PCs on this subnet.
> > There is no NT domain named the same as the workgroup. There is an
> > NT server acting as a WINS server (199.170.224.6 as specified
> > as the 'wins server').
> >
> > I've tried raising the os level to 33 also... that did not give different
> > results.
> >
> > Anyone have any ideas? Do I need to have the WINS server be the
> > domain master browser instead of Samba (BROWSING.txt seems to
> > clearly indicate that Samba can be the Domain Master Browser).
> >
> > notice that nbtstat on a Win NT machine does not mention my samba machine as
> > a master browser...
> >
> > H:\tmp\tmp>nbtstat -A 192.207.166.161
> >
> > NetBIOS Remote Machine Name Table
> >
> > Name Type Status
> > ---------------------------------------------
> > LORAX <00> UNIQUE Registered
> > LORAX <03> UNIQUE Registered
> > LORAX <20> UNIQUE Registered
> > ENGINEER <00> GROUP Registered
> > ENGINEER <1B> UNIQUE Registered
> > ENGINEER <1C> GROUP Registered
> > ENGINEER <1E> GROUP Registered
> >
> > MAC Address = 00-00-00-00-00-00
> >
> > % nmblookup -d 5 -B lorax __SAMBA__
> > Initialising global parameters
> > Processing configuration file "/usr/local/samba/lib/smb.conf"
> > Processing section "[global]"
> > doing parameter browseable = yes
> > doing parameter domain logons = yes
> > doing parameter guest account = nobody
> > doing parameter load printers = yes
> > doing parameter logon script = hi.bat "S: %S" "P: %P" "u: %u" "g: %g" "U: %U" "G: %G" "H: %H" "v: %v" "h: %h" "m: %m" "L: %L" "M: %M" "d: %d" "a: %a" "I: %I" "T: %T"
> > doing parameter lpq command = /usr/ucb/lpq -P%p
> > doing parameter print command = /usr/ucb/lpr -P%p %s;/bin/rm -f %s
> > doing parameter printcap name = /usr/local/smb/printcap
> > doing parameter printing = sysv
> > doing parameter security = user
> > doing parameter smbrun = /usr/local/samba/bin/smbrun
> > doing parameter username map = /usr/local/smb/user.map
> > doing parameter workgroup = ENGINEER
> > doing parameter wins support = no
> > doing parameter wins server = 199.170.224.6
> > doing parameter domain master = yes
> > doing parameter local master = yes
> > doing parameter preferred master = yes
> > doing parameter os level = 2
> > doing parameter log file = /var/adm/log/log.mMuUhLv.%m,%M,%u,%U,%h,%L,%v,
> > doing parameter lock directory = /var/spool/samba/locks
> > doing parameter share modes = yes
> > pm_process() returned Yes
> > adding IPC service
> > Warning: inconsistant interface 192.207.166.161
> > Added interface ip=192.207.166.161 bcast=192.207.166.161 nmask=0.0.0.0
> > bind succeeded on port 0
> > Socket opened.
> > Sending queries to 192.207.166.161
> > 11/24/97 18:30:01 sending a packet of len 50 to (192.207.166.161) on port 137
> > 11/24/97 18:30:01 received a packet of len 62 from (192.207.166.161) port 137
> > nmb packet from 192.207.166.161(137) header: id=30452 opcode=Query(0) response=Yes
> > header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
> > header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
> > answers: nmb_name=__SAMBA__(0) rr_type=32 rr_class=1 ttl=14400
> > answers 0 char D..... hex 4400C0CFA6A1
> > Got a positive name query response from 192.207.166.161 (192.207.166.161)
> > 192.207.166.161 __SAMBA__
> >
> > * Next message: Herb Lewis: "Re: SMB printing client driver data serving w/ Samba"
> > * Previous message: Edward Quillen: "SMB printing client driver data serving w/ Samba"
> > * Next in thread: Simon Hyde: "Re: domain master browser"
>
>
>
More information about the samba
mailing list