Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your "DC Not Found" issue should be resolved then.
More Administratively intensive solution is to modify the LMHOSTS file to have the following entry on every Windows Workstation/Server in the troubled subnet. IP.ADD.RE.SS MachineName #PRE #DOM:Domain-Name HTH's Mark -----Original Message----- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 02, 2003 4:16 PM To: [EMAIL PROTECTED] Subject: O/T more campus design issues [7:60136] You all remember my very simple campus network re-design that I've been helping out with? It sure has been keeping me humble. ;-) So we upgraded the single subnet to two subnets and two VLANs. Everything is working OK except for Windows networking. The PCs on the new subnet can't find a domain controller for authentication. So, you can feel free to yell at me for not gathering more information on the symptoms, but the client hasn't told me much. ;-) But does this ring a bell with anyone? Are there standard recommendations on how to handle this in a subnetted VLANed internetwork. I'm not too well informed on Windows networking. My co-author wrote that chapter in my troubleshooting book. Thank-you so much! Priscilla Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60144&t=60136 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
