I wouldn't be too sure on that cease-fire since master browser election can happen at
anytime 2+ machines see each other.
OK, a DHCP solution that does not require a DC or even a server OS assuming you have
a router like a Linksys WRT w/ DD-WRT firmware (many other brand routers can also):
DNSMasq
It's controlled DHCP using "static" IP leases based on MAC addresses. You enter all
the MAC's & corresponding IP's for your systems into the router. Switch on your
systems & they will then grab the correct IP via DHCP which also configures them to
ask the router for DNS lookups. Result is now local lookups are by DNS not WINS/LM
eliminating master browser issues.
Using DHCP w/ leases to map "static" IP's to DNS entries:
http://www.dd-wrt.com/wiki/index.php/DNSMasq_as_DHCP_server
I point this out because then EVERYTHING relies on the router giving central control,
most everyone has these routers, and it's simply web page interface. So no more wrong
IP, subnet masks, etc... on a system making you scratch your head when routing
doesn't work. Added benefit you are still in full control of the IP mappings but from
a central spot. Need to change a system's IP, simply navigate the router's DHCP
webpage, make change & reboot the changed system to force a new DHCP lease.
Sure beats settings guessing game PC by PC!
DHSinclair wrote:
jmaccraw,
I do so understand your focus on a DC and DHCP. I use neither. But,
when I decide to do either, I will seek you out for proper guidance.
ATM, my grumbling clients seem to have settled into a mutual
"cease-fire." LOL!
Best,
Duncan
At 00:05 04/23/2009 -0700, you wrote:
If it's not a domain controller, then it's just another copy of
windows adding another master browser wannabe to the crowd.
DHCP reservations & linked DNS updates trounce the moronic master
browser thing anyday. Bottom line is if you can get there by IP
address, 'net is broken for sure!
