Yep, the former (3172 -> VM TCPIP -> IUCV -> Linux. There use to be a problem with Samba and broadcasting on a point to point connection, but that has been resolved.
I moved all Samba images to a workgroup called "LinuxSamba", and that workgroup started poping up on many PCs. But not on all of them. So far, no reason for some and not others. In some places, with 10 PCs together, 2 show it. In other places, with 9 PCs together 7 show it. All W2K. Subnets don't seem to be the answer. But in this case, it's being passed off to the Network people to determine the problem/solution. Perhaps, buy the end of the month, they can get to it. Funny, that in it's own workgroup all Samba images are showned. When I was using the default "workgroup" workgroup, only Linux22 showed. I still think that was something in the "windows" world that didn't refresh properly. So a new workgroup name was all new to cache stuff. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 05/04/05 2:08 PM >>> > > This isn't OSA (yet), it's a 3172 via escon to VM's TCPIP > (z/VM 4.2). > > There was a problem with Samba and broadcast on this setup, but not > > anymore. > > Hmm. The topology is: > > 3172 -> VM TCPIP -> Linux (guest LAN/IUCV/CTC)? > > or is it > > 3172 -> VM TCPIP (direct LCS attach) > 3172 -> Linux 1 (direct LCS attach) > 3172 -> Linux 2 > . > . > . > 3172 -> Linux N > > If the former, how are the Linuxen connected to the VM TCPIP stack? If > guest LAN, then 4.2 GLANs didn't do broadcast at all (the driver when > using a GLAN is the same as the OSA driver), so nmbd *can't* > work. Ditto > with IUCV and CTC -- those drivers do multicast, but not broadcast. > > > What might be a factor, was in the case of Linux22, Linux22 was > > installed, SP1 applied, then Samba brought up (which called > > for a series > > of packages to be installed. Note SP1 fixes may not be on > these newly > > installed packages). Samba shows as "Samba 3.0.4-SUSE". > > > > All other images (which don't work properly), were > installed with SP1 > > installed at Linux install time (SP1 was part of the CD > collection and > > was used by the install process). This Samba shows as "Samba > > 3.0.9-2.1.5-SUSE". > > Hmm. Dunno on that one. > > > It doesn't seem that the "man" pages were updated by SP1, > as when you > > use Yast to update the Samba parameters, parms such as "local > > master" as > > set to true/false, but the man pages shows yes/no. That > shoots a hole > > in my confidence in that part of the 'man' pages. > > I think I'd trust the man pages over yast, myself. Samba gets more > testing...8-) > > > On the Linux22 side, I keep getting: > > > > May 4 12:11:17 linux22 nmbd[12130]: [2005/05/04 12:11:17, 0] > > nmbd/nmbd_incoming > > dgrams.c:process_master_browser_announce(385) > > > May 4 12:11:17 linux22 nmbd[12130]: > > process_master_browser_announce: > > Not conf > > igured as domain master - ignoring master announce. > > > which tells me that some machine continues to think that > this image is > > a "master browser". Which it was, for a short time a week or > > two ago. > > Perhaps no other system has taken over as a "master browser". > > A master announce packet is telling you that some OTHER > system has been > elected master, and any other masters should stand down and let the > elected one do it's job. > > > All my Samba images (Linux22 to Linux26), all specify > either "backup > > domain controller" or "no DC", and "domain master = no". Some may > > specify "local master = true" and some "local master=false". > > This may be the problem. Is Linux26 one of the ones that has local > master = true? If so, then if those machines cannot hear the others, > then they elect themselves local master browser. A local > master browser > will then try to find the domain master browsers if there are any. If > none respond or the instance can't hear any response, then the local > browser elects itself domain master as well -- but you've told it it > can't be a domain master, so it says "sorry, i'm not configured to do > this, ignoring the announcement" > > > > So, is there a Windows command (or Linux command) that will > > tell me who > > is the PDC and/or the "master browser"? Perhaps that command > > will help > > me understand when I actually made a change to this process. > > You'll need to interrogate the WINS server database, or use a > sniffer, I > think. I don't know of any way to get a Windows box to cough up this > information. > > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
