OK Charles. I understand. As you know by now, I only really do this stuff at home. I have helped a buddy by putting a LEAF router at his office.
So, not being the guru and not having a great amount of time, I will eventually read bits and pieces. I only ended up with Win2K server because my drive crapped out on Tuesday and I figured that, what the heck. It would give me the ability to keep user profiles in one location. On this scale, it really comes down to what I'm willing to live with and for how long. Right now I timed it and I spend about 1 minute 'Preparing Network Connections'. That's really not too bad. Also, since this is only my home network, I run all servers on one box. It's name is WWW but has FTP and POP3/SMTP. I thought it great to define ftp.mullan.ca, mail.mullan.ca and www.mullan.ca and have them all point to the same box but thanks to M$ that doesn't work anymore as it seems to override my TinyDNS in this respect. (a little of my ranting too :) So really, would it be better to let my M$ box handle internal DNS and let LEAF handle dnscache for internet queries? Is there a package other than TinyDNS that is dynamic and will let the M$ box register hosts? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Steinkuehler Sent: February 8, 2003 10:26 PM To: John Mullan Cc: Leaf-User Subject: Re: [leaf-user] Win2K and LEAF John Mullan wrote: > OK. I did my research and found that Win2K Server 'Active Directory' > requires and DNS server with active/dynamic record keeping. My DNS is > TinyDNS on my LEAF box. TinyDNS does not register computer names (ie; > mullan2 = mullan2.mullan.ca). When the Win2K box boots up, it takes 5-10 > minutes to figure this out. > > Can anyone share with me a good way to make these two boxes co-exist > peacefully? IE; Make my private TinyDNS dynamic (probably not) or to make > the Win2K box forget about the DNS problem? Reinstall Win2K server without AD, or spend the time and effort to come up to speed on how M$ expects you to do networking (be prepared to buy about 3X more server licenses than you ever thought you'd need, as well as upgrade every box on your network to 2K or XP...or just live with the broken-ness Microsoft forces on you to try and get you to upgrade). It might help to through some online references as well...a google search for "microsoft co-opting internet standards" should turn up some good reading material. BTW: Can you tell I just had a junior network admin replace a failed NT domain controller with 2KServer (with Active Directory installed) because it "has to be better than NT, and we'll have to upgrade someday anyway, right?!?". <sigh> ...sorry about the rant :-/ -- Charles Steinkuehler [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html