Subj : Re: Network bindings ques To : Rohan Beckett From : NL Date : Sun Apr 01 2001 05:39 pm From: Jan van Hoek (NL) >> Why would you NOT use DHCP? Well, WE (=the company where I work for) don't use DHCP for 80% of our workstations. We have a number of good reasons IMnsHO: - fault tolerance: you can have multiple domain controllers, but you cannot have multiple DHCP servers on a WAN. Moreover, without a working WAN you can still logon via cached logon credentials. But without an IP address you won't get very far - DHCP won't travel through our WAN routers - some external services require NAT (I can't help that), and hence they require fixed IP addresses on the workstation side >> If a company is big enough to need NT Server (...) I'm not sure that we are big enough in your terminology. But with 100 NT servers and 500 NT workstations, we are not really small. But I'll compromise: we use DHCP on 100 head office workstations, but that's all. All servers, printers, routers etc etc within our head office have fixed IP addresses, and same applies to all branch office equipment. Fixed IP addresses are also assigned to the workstations on the branch office level for good reasons (as mentioned before). >> then you may as well run DHCP on the network, >> and ease maintenance issues. I'm not that sure that DHCP eases anything. We have a rule to choose domain name (workstation name) and IP address in a similar numbering scheme (you have to come up with unique machine names anyway, so why not assigning IP addresses in a similar fashion). For example: XXX015WKS005 (XXX = company name, 15 = branch office number, WKS = workstation, 5= teller position). The IP address of the same PC is 10.2.15.5 (2 = XXX's branch offices network, 15 = branch office, 5 = teller position). So precisely what is DHCP making easier on my maintainance burden?? Jan van Hoek (NL) Sun, 01 Apr 2001 23:55 +0200 CET --- BBBS/NT v4.00 MP * Origin: Barktopia Gating Project http://HarborWebs.com:8081 (1:379/45) .