How long does it take to run W2K Server before clients can log in? [fsmo roles] [netlogon]
Q: Client Systems (w2k/XP) can not immediately log into the domain immediately after W2K Server has been up. The server has all the FSMO roles, and Net started, but it takes a while before customers can log in? Is there something going on the server side that can be adapted for a faster logon process?
The domain is setup just for fun and practice, its not a real world environment, FYI:)
Best Answer: A million other members with big piles of virtually worthless ptz are also trying.
The big prizes are "sold out" within seconds of the redemption random starting time. Your odds of actually being able to redeem any of your ptz for even the junk prizes are practically nil.
Those YouTube videos showing members with piles of prizes were posted by shills.
If you like longshots, buy a lottery ticket. At least you won't be wasting hours of your time.
Don
Re:Alrighty, did as you guys suggested. Removed ISP's dns from tcpip settings of client machines and server. Enabled forwarding on server. Voila, instant log on
Merci
Re:Very interesting information. I recall my prof telling me that it may be a good idea to list the ISP's dns server ip the same for both primary and secondary. From what you guys tell me, now I can understand why.
Many of the things about Server are not in the book (the Resource kit may mention it), and have to be learned thru encountering problems and trial and error.
Thankyou fellas for the help
Re:In practise, I see the client often try to reach both at the same time, and sometimes even the seconday first
I'll second guy's experience. Seen it happen all the time. MS operating systems just up and query the secondary without even trying the primary – ever! Or blurt out to all four name servers if you have four configured (god only knows why you'd need more than two) and take the first answer that comes back as true.
oh well, try eliminating the ISP name server. Depending on your server setup you might want to consider running your DNS as a caching server – where it queries the root servers for name servers and asks the name server directly. you'll get more accurate information this way and a quicker response.
Re:But since in W2K and XP allows for more that two DNS server entries, would it matter anyhow whether I have the ISP's DNS in there, so long as I have my internal DNS as the primary?
My experience with Win2k clients is that they don't always attempt to reach the Primary DNS server first. I have verified this with packet sniffing on various networks, both live and test.
As MS would tell it, the client should attempt to contact the primary first. If the primary fails to return an answer, the search fails. If the client fails to reach the DNS server altogether, only then would it try to reach a secondary.
In practise, I see the client often try to reach both at the same time, and sometimes even the seconday first. I like to eliminate this possibility by ensuring clients are only pointed at in-house DNS servers. If you want to put something in the secondary (for fault tolerance), bring up a second in house DNS server.
Re:Ah, now there's something new I knew about but never practiced. Months out of school and I forgot already! Ah, ok I see, so I don't need ISP's dns entry in client machines. The client hits the DC's dns and it will forward it out automatically. I have to remove the *.* root from DNS for that to happen I believe. But since in W2K and XP allows for more that two DNS server entries, would it matter anyhow whether I have the ISP's DNS in there, so long as I have my internal DNS as the primary? I guess the ISP's dns should be removed if, per say, I want all clients to be going through a proxy.
Yup, dns has the proper folders in place in forward dns zone, and wins server is active also.
Re:The only time I would construct an LMHOST file with entries for DC's would be if I was running a Win2k domain without NetBIOS.
You should take the entry for your ISP's DNS server out of the TCP/IP Settings. Make sure your DNS server is forwarding to your ISP DNS. Also ensure that your forward lookup zone contains the four automatically registered folders _tcp, _udp, _sites, _mscds. They shoud be sub-folders under your forward lookup zone folder.
Re:Thx guys, I'll double check on the dns. I'm sure the clients have it down as primary, and then the external ISP's dns as the secondary. About the host files being on the client machines, is it really helpful if I manually add in the entry for the DC? The nic and ip settings, host/lmhost files are loaded and utilized by the client machine before or after user logs on? I'm assuming before, otherwise how would it be able to find the DC eh.
Re:guy, I had the same problems as you are having, but as guy and guy said, I set my clients to default to my domain controller as primary DNS. The delay went away immediately after the change….
Re:Win2k clients use DNS to locate the DC. As soon as the DNS service is up clients can log on. This generally happens after the "Preparing Network Connections" stage of boot, but sometimes it doesnt finish until sometime after that.
Re:Are you running either WINS or DNS ? If not, do you have hosts files on all of the workstations ? It could be that they cannont find the server untill the NetBIOS broadcasts take effect. Using Any of the above would take care of that prob.
Related posts
Tags: fsmo roles, netlogon