Hi, I am having the same problem. Did you figure out how to do this? Any help in how to remove stale WINS entries from Samba would be greatly appreciated. Cheers, -farshad
Hi, Farshad, I'm too new at this to be of much help. My WINS seems to be working, but I'm clueless as to why, just as I'm clueless as to why my DNS is not working. Eric Hines Farshad Abasi wrote:> Hi, > > I am having the same problem. Did you figure out how to do this? Any > help in how to remove stale WINS entries from Samba would be greatly > appreciated. > > Cheers, > > -farshad-- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln
Eric Hines wrote:> Hi, Farshad, > > I'm too new at this to be of much help. My WINS seems to be working, > but I'm clueless as to why, just as I'm clueless as to why my DNS is > not working. > > Eric Hines >The questions you need to ask yourself are simple. Where is my DNS server? Where is my machine that I am pinging from pointing to in terms of DNS? Does that DNS server have the records to do with my "lserver1" samba server? Are you running a local name server as per JHT's docs? Are you pointing your DNS on your "lserver1" samba server to an external name server? Answer each of these questions for us and we'll see where we can help. Regards Geoff Scott
Eric Hines wrote:
>
> My DNS server sits on lserver1. I'm trying to ping lserver1 from
Do:
ping lserver1.test.biz
Response is?
> lserver1. With nsswitch set only to files or only to wins (/e.g./,
> hosts: files), this is successful. With nsswitch set only to dns, I
> cannot get name resolution, although I can successfully ping by IP
> address. I can ping lserver1 by name or by IP successfully from
> mustelidae.
>
> Where is lserver1 pointing in terms of DNS? How do I tell? At this
John also mentions setting in resolv.conf
nameserver 127.0.0.1 (this is your loopback address)
nameserver 192.168.0.2 (this should be the ip of your router/firewall)
(you can have a maximum of 3 nameserver listed
> point, all I can say is that I've set up named.conf (and dhcpd.conf)
> as John has them in his Chapt 3 example, with the sole differences
> being that I'm using one subnet and not two (a DHCP issue), I'm
> calling my server lserver1.test.biz, vice diamond.abmas.biz, and
> lserver1's IP address is 192.168.1.103, vice the one John's using
in
> his example.
> Aside from these edits, named.conf (and dhcpd.conf) are cut and
> pastes from John's latest on line. Is /etc/resolv.conf part of this
> answer?
YES!
>
> My named.conf and dhcpd.conf are built from John's example, as
> mentioned above. /Etc/hosts has the IP address/name pairs he calls
> for. I think that means I'm running a local name server.
>
No. The hosts file bypasses dns eg. Nsswitch is usually set to "files dns
wins"
Check files 1st then dns, then wins to find names on your lan
Files is your hosts files the rest should be self explanitory
> As you can see, I have very little understanding of what's going on
> here; I've rather slavishly followed John's example, and I'm
clearly
> making mistakes I'm not recognizing.
>
You need to learn about DNS elsewhere.
Go here, and read this:
http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch14.ht
ml
Particularly this:
http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch14s06
.html
Then apply it to your situation.
> Thanks
>
> Eric Hines
The over view is this:
The way out of this mess from my point of veiw is to switch off dhcp from
the router/firewall.
Your samba server needs to know it can be a dns server. It finds this out
from the resolv.conf file. Make it have a static ip.
Any windows machine that is obtaining an IP address via DHCP needs to have
the wins server ipaddress handed to it otherwise it will use broadcasts.
You can see how to do this if your samba server becomes the dhcp server on
your lan, from john's section on configuring the dhcpd. It sounds like the
samba server is correctly configured for wins. (really you should show us
your resolv.conf and your smb.conf + your nsswitch.conf)
Most real servers have static IP's for fairly obvious reasons.
And then other things should start to fall into place for you.
Regards Geoff Scott
Eric Hines wrote:> Geoff Scott wrote: > >> Eric Hines wrote:>> >> The over view is this: >> The way out of this mess from my point of veiw is to switch off dhcp >> from the router/firewall. >> >> > How? I can't switch off the router/firewall. >No of course not. You mean to say that you can't get access to a web interface or commandline on the router to configure it? You might need to look at getting better hardware / strongarming your ISP for info on the router if it is ISP provided. Can you show us your zone files for test.biz & 192.168.1.0? What do your logs say for bind starting up? Can you restart bind and watch your logs? Do you have any errors for it? Regards Geoff Scott
Geoff, Sorry about the hour; I didn't realize you were still up--I went to bed.... A number of questions, and some updates. I can find no evidence of active named logging, although I did find one log with named entries. In particular, what is the relevant log(s)? There is no syslog or system log. Running a FIND on *log didn't turn up anything even remotely close. I've obviously not got logging turned on properly.... I also notice that, where John's example has several instantiations of named running, I have only one, and it's very difficult to terminate that one--I have to kill <pid> to do it. Service <daemon> restart works fine for all the others, and service named start works fine, too. Just service stop/restart do not work--the latter hangs on the stop part. In the files below, why all the changes to mail from lserver1? I thought from John's examples these were supposed to be the server name? Geoff Scott wrote:>Eric Hines wrote: > > >>Geoff Scott wrote: >> >> >>>What do your logs say for bind starting up? Can you restart bind and >>>watch your logs? Do you have any errors for it? >>> >>f you mean winbind, a tail -f on log.winbindd just showed it >> >> >No Berkely Internet Name Daemon - BIND >The daemon is actually named "named" > >Grep for the entries for that daemon (named)in the relevant log, >/var/log/....... Syslog? > >In log /var/log/messages, named starts successfully, loads all the zone files OK, and it outputs the log entry "lame server resolving 'lserver1.test.biz' (in 'test.biz'?): 206.16.250.17#53, also ... .18#53 several times. These are owned by a company in Barcelona, Spain. There also are cases (fewer) of resolving localhost.lserver1.test.biz to the same IP addresses/ports. tail -f messages and pinging lserver1 produced no immediate result. I could find no other log that had named entires in it. According to log.nmbd, Samba server LSERVER1 and samba name server LSERVER1 repeatedly became domain master browser and local master browser, respectively, on 192.168.1.103. tail -f log.nmbd also did not respond to an unsuccessful ping of lserver1. You asked whether I could tell my router/firewall not to send dhcp stuff to lserver1 only. That would take a specific MAC address exclusion capability, and this router/firewall does not have that. Can I, instead, tell lserver1 not to look to the router/firewall, but only to look to itself (/e.g./, via the dhcpd.conf or via lserver1's System Settings|Network GUI, using the DNS and/or hosts tab)? Or would that lock lserver1 into itself, never to get access to the Internet? I've done some other poking around in response to the DNS doc for which you sent me the URL last night, and noticed these things: /etc/sysconfig/networking/devices/ifcfg-eth0 is set as follows (emphasis added) DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet DHCP_HOSTNAME=*lserver1* I have the same thing for eth1 (there are two NIC chips on the motherboard), except it's turned off. dhcpd.leases has pserver1 (my print server) at 192.168.1.96, even though it's hardwired via its own setup functionality to a static address of 198.162.1.10, and it responds to pings at the .10 address. Finally, I made the zone file changes, and I still cannot ping lserver1 or lserver1.test.biz--unknown host in both cases.><snip> > >Regards Geoff Scott >-- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln
Eric Hines wrote:> Geoff, > > Sorry about the hour; I didn't realize you were still up--I went to > bed.... >I'm in Australia, GMT+10. You think I'm a party animal? Nah, I'm just at work. ;-)> A number of questions, and some updates. I can find no evidence of > active named logging, although I did find one log with named entries. > In particular, what is the relevant log(s)? There is no syslog orThe relevant log is whatever had instances of named logging to it, in your case from below it would appear to be /var/log/messages.> > In the files below, why all the changes to mail from lserver1? I > thought from John's examples these were supposed to be the server > name?You had an MX record in there. If you are going to learn to configure an MTA then the mailserver shouldn't be a cname. And seeing as you had mail.XXX.XXX CNAME'd to lserver1 I switched it around. It is considered bad form from what I have read, to use a CNAME for a mail server.> In log /var/log/messages, named starts successfully, loads all the > zone files OK, and it outputs the log entry "lame server resolving > 'lserver1.test.biz' (in 'test.biz'?): 206.16.250.17#53, also ... > .18#53 several times. These are owned by a company in Barcelona, > Spain. There also are cases (fewer) of resolvingOK. So your machine doesn't look to itself as being the master of that domain. John provides enough info for you to figure out why.> According to log.nmbd, Samba server LSERVER1 and samba name serverLSERVER1> repeatedly became domain master browser and local master browser, > respectively, on 192.168.1.103. tail -f log.nmbd also did not > respond to an unsuccessful ping of lserver1. > > You asked whether I could tell my router/firewall not to send dhcp > stuff to lserver1 only. That would take a specific MAC address > exclusion capability, and this router/firewall does not have that.No, I asked if you could turn off the DHCP server on your router / firewall completely and use the dhcp server on your samba server to deal with your local networks needs.> Can I, instead, tell lserver1 not to look to the router/firewall, but > only to look to itself (/e.g./, via the dhcpd.conf or via lserver1's > SystemAs people have said to you *many* times the easiest way to do this is by using a static ip on your server. USE A STATIC IP! CONFIGURE THINGS STATICALLY.> Settings|Network GUI, using the DNS and/or hosts tab)? Or would that > lock lserver1 into itself, never to get access to the Internet? > > I've done some other poking around in response to the DNS doc for > which > you sent me the URL last night, and noticed these things: > /etc/sysconfig/networking/devices/ifcfg-eth0 is set as follows > (emphasis added) > DEVICE=eth0 > BOOTPROTO=dhcp > ONBOOT=yes > TYPE=Ethernet > DHCP_HOSTNAME=*lserver1* > I have the same thing for eth1 (there are two NIC chips on the > motherboard), except it's turned off. >This is why I said to you originally to use the gui. It's easier to do it with the GUI, then poke around your system and see what's been changed. You need to read more about the basic configuration of your Linux flavour before you start on these tasks. That way you would know exactly what files control what configurations and where exactly to find them.> or lserver1.test.biz--unknown host in both cases. >It looks like your server doesn't "think" it's the authoritative master for your internal DNS. Or something is wrong with your zone files. Read the DNS docs again. And again. And again........ Geoff