The #DOM entry will create a 1C entry for the domain on the local box when queried, if you add the #PRE it will actually stick it in your netbios cache right away and won't expire...
However, Windows 2K+ machines hitting Windows 2K+ domains don't use WINS, they use DNS. Unfortunately the hosts file will not take SRV records which is what needs to be found. joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Singler Sent: Saturday, June 05, 2004 8:59 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] locate DC, no DNS Thanks for the responses. joe - i only have the gateway defined on the public interface of the DC. All - doesn't KB180094 imply that you *could* do what i am trying to do? Am i misreading that? This article <http://tinyurl.com/24wgl> seems to support the idea of being able to do this using lmhosts: <snip> Adding Domain Controllers by Using #DOM Using the #DOM keyword to designate domain controllers causes the computer to add entries to a cache of domain names that the computer uses to contact available controllers to process domain requests. </snip> Also, from what i understand, as part of the logon process the client locates a DC using WINS, DNS or lmhosts. so, again, this should work? Finally - this is more of an exercise in curiosity than a project with a future (but thanks for the concern about my health, joe!). john Quoting joe <[EMAIL PROTECTED]>: > I again have to agree with Al here. This is troublesome configuration > which would add years of issues ot your life. :o) > > Additionally, by any chance do you have gateways on both of the NIC configs? > Just an FYI that that can bite you pretty nicely as well. > > joe > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al > Sent: Friday, June 04, 2004 4:48 PM > To: '[EMAIL PROTECTED]' > Subject: RE: [ActiveDir] locate DC, no DNS > > If I understand you correctly, you want to have the lab > workstation/member contact the lab DC via the private network only. > That about right? Save yourself a lot of trouble and install DNS in > the lab and keep them logically separate (network as well if you need > to). That'll also save you a lot of issues later. > > Install DNS in the lab environment and remove the public interface. > You can transfer the zone first if you need to and then use that for lab purposes. > Active Directory relies on DNS. If you > can't reference it, you can't have it. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Singler > Sent: Friday, June 04, 2004 1:54 PM > To: [EMAIL PROTECTED] > Subject: [ActiveDir] locate DC, no DNS > > Folks, > > Here's what i am trying to accomplish in a Lab environment. > > Simplified: > > 1 DC, 2 NICs (one on private network, one on public). We use BIND DNS > (no dynamic registrations) - DNS only available to public network. No > WINS. I have a machine that is a domain member, 2 NICs (one on > private network, one on public) which i would like to exist only on > the private network (no DNS available there) and still be a member of the domain. > > I thought i could do this by mod'ing the lmhosts file and point the > member server to the internal IP of the DC but so far that is not > working. The KB that i am referencing is: > > http://support.microsoft.com/default.aspx?scid=kb;EN-US;180094 > > All OS's are w2k3. > > Any ideas? > > tia, > > john List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
