We have been looking for a way to notify our users when they are running low on disk quota, without sending them mail. WinPopup actually seemed like the best way, so my partner began looking at feeding quota output into smbclient -M when quota was getting tight. The only problem is that smbclient -M frequently fails to find the client's host name. The -I parameter will often fix it, but I am concerned about the -M problem nonetheless. I have a machine configured to be a WINS server, and all of the lab machines are DHCP-configured to use that server. What exactly is the -M parameter looking for? What would I do to address the problem? I asked a question a week or so ago along the same lines (with no response :( ), regarding why Samba appears to do a reverse DNS lookup on clients (using gethostbyaddr() in util.c if I remember right). Why does it need to do this? Our DNS servers (maintained by another group) were cut off due to a WAN outage a week or so ago. At that point, EVERYTHING Samba-related stopped working due to this lookup. Yuck! (I have since installed a local caching DNS server. Will this prevent it from happening in the future? I'd still like to know that a DNS failure won't stop my lab from working.) The reason I ask is that all of our lab machines are dynamically given IP addresses, with a lease period of 2 hours. None of these machines is in the DNS system, simply because Lab10 could have different IPs throughout the day. Is there any way to deal with the lookup problems I mentioned above? Thanks in advance. Daryl Daryl Biberdorf darylb@superserve.com
You wrote: | The only problem is that smbclient -M frequently fails to find | the client's host name. The -I parameter will often fix it, but | I am concerned about the -M problem nonetheless. I have a machine | configured to be a WINS server, and all of the lab machines | are DHCP-configured to use that server. Hmmn: I'd look at wins ttl, actually. I suspect that the DHCP IP-address leases are timing out in 2 hours and the WINS name-address mappinga are timing out in three days... That means if they're not sucessfully replaced when the pc boots and tries to claim its name, that you will get a mismatch. This can be confirmed/denied by going through a list of all the names calling nmblookup for each name. For example, ``nmblookup elsbeth'' should give you ``129.155.8.39 elsbeth<00>''. If the address doesn't match the name, you've found the problem. --dave -- David Collier-Brown, | Cherish your enemies. They're harder to 185 Ellerslie Ave., | come by than friends and more motivated. Willowdale, Ontario | davecb@canada.sun.com, hobbes.ss.org N2M 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb
Sarma Seetamraju <sarma@usa.net> wrote:> Darryl, > the world is waiting for a standard way to integrate the DHCP & DNS > servers. I am waiting too.http://search.ietf.org/internet-drafts/draft-ietf-dhc-dhcp-dns-08.txt> There is NO WAY the DNS server is gonna > know what IP address DHCPS assigned to a specific mahine. > The reason the integration > is difficult because the DNS is of the galactic-scale heritage, while DHCP is > a typical micro-departmental feature.With respect, that is highly misleading: the DNS is **specifically** designed to scale up from departmental to worldwide, so that one can find hosts anywhere in the world. If it didn't, it wouldn't be worth having.> Making your network entirely microsoft is the only way out.Surely you jest! This **is** the samba list, after all... Try nmblookup, anyway: dns is the wrong place to look (The light is better inside the house, but the jewel was lost out in the garden (;-)) --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | davecb@hobbes.ss.org, canada.sun.com N2M 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb