Problem. Server environment with 10 machines connect througha 20 port switch. Initially running NT server, half clients were 98, half were XP. The problem was the clients would get kicked off the server, not being able to access there documents. The conclusion was to restart the server, thus fixing the problem. This spiraled out of control forcing reboots 10 -20 times a day. We upgrade to 2003 server, full format and upgraded the ram. This solved the problem for a week until it rared it's ugly head again. We precedded to check the cabiling to the switch, and from the server to the switch, the switch itself, all of which didn't help our cause. Finally we replaced the network card to a high end 3com and this solved our problem for several months. Now, it has come back, not quite as bad, but still kicking people off the server, once again, our only option is to restart the server. Sometimes restarting up to four times until it starts working. Clients can be at any given time running large files such as Myob and Large PST files. Possbile problems: throughput? 1) check the server logs to find some critical, The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error. 2)The master browser has received a server announcement from the computer ANDREW that believes that it is the master browser for the domain on transport NetBT_Tcpip_{A93BEC78-6028-4A26-A9. The master browser is stopping or an election is being forced. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/even... 3)The Security System detected an authentication error for the server ldap/server.office. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request. (0xc000005e)".

"Clients can be at any given time running large files such as Myob and Large PST files." NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO! http://msexchangeteam.com/archive/2... TECH-NO-LOGICAL ROMANCE! http://www.homestarrunner.com/tgs12.html

Geeesh.. calm down heropsycho. You're going to blow a gasket. It is true that storing a PST on the network isn't supported but in the real world it does work the vast majority of the time. I'm not telling you to do it and if you read the article you'll see the reasons why. However. Try putting the PST files on the local machines and then have their hard drive die - which it will, and all their email and contacts along with it and see how easy that is to manage. You can talk to them about archiving all day long but the reality is that most users won't do it. I know that is their own problem, but that is the real world. So while it may not be officially supported, it is still done a lot and most that do it have it work just fine. That may not be the case in the text book world but it is the case in the real world so take that for what it is worth. Your errors point to DNS issues. I'd focus my attention there and read up on how the browser server works. Tell us about your network. Do you have a domain?

hmmm check that all related services to all operating systems are functioning. Try defraging the ad and hdd. Talk to microsoft about it

The symptoms are not in the slightest related to DNS misconfigurations or missing records. They are EXACTLY the symptoms of accessing PST's over the network, and these aren't just small PST's, they're large ones. The supposed DNS errors are caused because the system has depleted kernel memory and is not able to respond to DNS queries. This is why reboots temporarily fix the issue because it ends sessions and frees up kernel memory so the server can function again. Common sense: if you didn't touch DNS, how can DNS be the culprit when a simple reboot temporarily fixes it? "Your errors point to DNS issues. I'd focus my attention there and read up on how the browser server works. Tell us about your network." The master browser error is common, routine, and is completely unrelated to this or DNS. Glen apparently needs to read up on it himself because he doesn't seem to understand that this is NetBIOS/WINS related, and has nothing to do with DNS. (To the original poster, sorry, Glen tends to try to come in and "correct" my posts when it's unnecessary, such as this.) The real world is this is what happens when you have PST's being accessed over the network. You can make excuses as to why this is often done, but it doesn't change the consequences of doing so. "So while it may not be officially supported, it is still done a lot and most that do it have it work just fine." Not with large PST's and/or a large amount of users doing it. I worked for Microsoft Premier Product Support and saw this a bunch of times. As soon as he began describing the symptoms, I immediately skimmed his post for "PST" because I flat out knew what this is. I typed "NOOOOOOOOOOOOOOO!" as a joke and to add emphasis that this is with certainty the root cause. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

His error is -"The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly." No way that is DNS huh? WINS isn't needed or used by AD so I doubt the browser events are really causing a problem. The other error is ""There are currently no logon servers available to service the logon request." Look that up and then tell me that there is no way it is DNS.

"His error is -"The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly." No way that is DNS huh?" It has nothing to do with missing records or misconfigurations pertaining to DNS. It is indicative of the DNS service not responding to a query. Tell me in that error where it says, "this record is missing". It doesn't. "WINS isn't needed or used by AD so I doubt the browser events are really causing a problem." You said that he had DNS problems, and he needed to look into how the browser service worked due to the error related to a master browser election. As I've said, that error is routine, common, pertains to NetBIOS/WINS, and is completely unrelated. Why would you bring up the browser service or this error as reasons to think this whole thing is about DNS?! Simple - you thought master browser is related to DNS, when it isn't, and now you're changing your tune. "The other error is ""There are currently no logon servers available to service the logon request." Look that up and then tell me that there is no way it is DNS." Again, the reason is because the server has exhausted it's kernel memory. Look, if DNS were screwed, when he rebooted, DNS would be what? STILL SCREWED! So why does it work after a reboot? If DNS is screwed, why are users able to log in to Active Directory without a problem? If DNS is screwed, why did adding RAM temporarily alleviate the problem for awhile? Couldn't be that there was more RAM that needed to be consumed before the server entered a troubled state again. Does adding RAM correct missing DNS records or DNS misconfigurations? Sorry, this isn't a DNS problem, and you're completely ignoring the fact that the symptoms exhibited match EXACTLY with what happens when PST's are accessed over a network. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"