One more item... If you implement a WINS server or specify a DC in the LMHOST file you may want to make sure the DHCP is specifying the node type as "H". It's one of the DHCP options on an NT DHCP Server.
""Matthew Tighe"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > My recollection is that a client will broadcast out for the DC and either > the DC or the Master Browser for the subnet will respond with a name. > Regardless, windows is heavily reliant on being able to resolve Netbios > names. It is a definite possibility you should explore. You also may have > a client on the VLAN without a DC acting as a Master Browser, which can > cause all sort of problems for your clients on that network if he has > bad/corrupted information. > > One way to make sure would be to add an entry for the DC on a single host > and (after rebooting) see if it can connect. There is an option in the > LMHOST file to specify a box as a DC for the domain. > > ""Priscilla Oppenheimer"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > I do know a lot about NetBIOS naming, but is this really a naming problem? > > They can't find the domain controller. Do they try to find it by name? > > > > I'll find out if there is a WINs server or if they are configured as > b-nodes > > or other. I already asked the client that but didn't get an answer. > > > > But I'm failing to see the connection with naming and the domain > > controller..... Perhaps it's too convoluted to explain, considering it is > > Microsoft. ;-) > > > > We'll try a domain controller in each subnet too. > > > > Priscilla > > > > Matthew Tighe wrote: > > > > > > Actually, if there is no NetBios Name Server (WINS), all the > > > clients will > > > resort to broadcast (B-node) resolution (m-node, h-node) or > > > simply fail > > > (p-node). I'd recommend checking out the following Microsoft KB > > > articles: > > > > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;102725 > > > > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;119493 > > > > > > The first link describes the LMHOST file located on all Windows > > > clients, > > > which might be your savior here if the network is small enough > > > (simply add > > > the DC to the LMHOST file and reboot). The other describes > > > Netbios naming > > > in general. > > > > > > I agree with James' statement about a DC on each subnet. It > > > really seems to > > > help legacy Windows networks. > > > > > > ""Priscilla Oppenheimer"" wrote in > > > message > > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > > James Willard wrote: > > > > > > > > > > Priscilla, > > > > > > > > > > You'll need to either have a domain controller on each > > > segment > > > > > or set > > > > > the "ip helper-address x.x.x.x" on the DC-less interface on > > > the > > > > > router > > > > > that's routing the two segments. In other words, if > > > ethernet0 > > > > > is on > > > > > subnet 1 without a DC, and ethernet1 is on subnet 2 with a > > > DC, > > > > > place the > > > > > command on ethernet0. NetBIOS will attempt to resolve names > > > by > > > > > broadcast, and the helper address will turn that broadcast > > > into > > > > > a > > > > > unicast towards the IP of the DC you specify in the config. > > > Let > > > > > me know > > > > > how that works. > > > > > > > > I may be showing my ignorance here, but that would address > > > naming if the > > > > nodes were broadcast nodes (B-nodes), but does it address the > > > customer's > > > > complaint that "clients can't find a domain controller for > > > authentication?" > > > > > > > > Anyway, we tried what you said and it didn't help, but there > > > could be > > > > something else wrong too. Maybe the best solution is what you > > > said about > > > > having a domain controller in both subnets?? > > > > > > > > Thanks for your help and any additional suggestions. > > > > > > > > Priscilla > > > > > > > > > > > > > > James Willard > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > > > > Sent: Thursday, January 02, 2003 5: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=60153&t=60136 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
