Well, I've poked around the documentation without any success... I've got several samba servers running, but I've never been required to deal with Samba as a client on a workstation until now. The workstation is RH 7.2, Samba-common 2.2.1a and it's on a LAN with a 2.2.0 server and a pile of winXX workstations (no NT). KDE is the X environment. I needed to get linpopup going to converse with winpopup on the MS boxes. Fine, I found it, installed it and proved that it can send messages. Problem comes when I try to send a message to the Linux workstation! The netbios name is not known on the network. Looking in browse.dat and wins.dat on the Samba server reveals that the workstation is not on either list. This is presumably because the workstation is quiet in the true Unix way. But, as the network is DHCP controlled, I can't use static hosts files to specifically map the workstation to an IP. Because the workstation is not configured to be a server, it doesn't have any more samba packages installed than RedHat specified in the default install. There is an smb.conf file however. Does it have a use in a client computer? I've set a WINS server entry, netbios name, etc. but still don't see the box on the network. So, how does a person cause a Linux workstation to be visible on the DHCP network from Windows machines? Is there documentation out there somewhere dealing with samba as a client? A final note, linpopup starts, but does mutter something about not finding 'smbstatus'. Not sure if that relates or not, as linpopup does successfully find MS boxes by netbios name... presumably it uses WINS, but it could be doing a broadcast too I guess... R Brock Nanson, P.Eng. Kamloops BC Canada
> From: samba-admin@lists.samba.org > [mailto:samba-admin@lists.samba.org]On > Behalf Of Brock Nanson > Sent: Thursday, March 14, 2002 1:16 AM > To: samba@lists.samba.org > Subject: [Samba] samba as client, adding to browse list > > So, how does a person cause a Linux workstation to be visible > on the DHCP > network from Windows machines? Is there documentation out > there somewhere > dealing with samba as a client?Use DHCP 3.0x and enable DDNS? Charles
I suppose the answer to this question may be obvious to many people, but it was something I couldn't find documented! I suspect Charles' answer below would probably solve the problem, but the simple answer (for those people like me searching the archives) is to install the server end of the package. In hindsight it's very clear, but not from where I was standing! Linux/Unix are quiet on TCP/IP networks. Therefore, why would workstations advertise their presence if they have nothing to offer? But, when configured to behave as a server (even with nothing to serve), the WINS settings and announce settings suddenly become active, because now there's a reason for the machine to be seen on the network. My requirement for linpopup may be an unusual case as it requires the machine to be seen, even though it doesn't necessarily provide any services. I think it would be useful to include this little tidbit in the doc's somewhere! Sometimes the act of writing the question helps one to answer it! Thanks Charles for your response! Brock | From: "Charles Marcus" <CharlesM@Media-Brokers.com> | To: "Samba Maillist (E-mail)" <samba@lists.samba.org> | Subject: RE: [Samba] samba as client, adding to browse list | Date: Thu, 14 Mar 2002 10:32:08 -0500 | | > From: samba-admin@lists.samba.org=20 | > [mailto:samba-admin@lists.samba.org]On | > Behalf Of Brock Nanson | > Sent: Thursday, March 14, 2002 1:16 AM | > To: samba@lists.samba.org | > Subject: [Samba] samba as client, adding to browse list | >=20 | > So, how does a person cause a Linux workstation to be visible=20 | > on the DHCP | > network from Windows machines? Is there documentation out=20 | > there somewhere | > dealing with samba as a client? | | Use DHCP 3.0x and enable DDNS? | | Charles