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):
DNS
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
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!
DHSin
It appears that this {still strange 2me} glitch seems to be fixed.
My WinXP clients have NOW re-populated their NetNeighborhood views with
everybody else that are currently alive/hot.
And, following a re-boot of my W2K server, its' NetNeighborhood window also
shows everybody else that are curren
Oddly enough I must focus on "How", "Why", and "WTF" way too much...
I finally just did a ReStart of the suspect machine. All LAN Clients are
now back in the NN/Workgroup. I just give up! I found nothing except
several information entries in the Event Log between 0732 and 0759 this am
