When logging into our server hosting Exchange, with a domain account, it hangs for an absurd amount of time (an hour or more) before actually bringing up a desktop. However when logging in with the local administrator account, it passes the welcome screen but then hangs on "Personal Settings." From here, I can at least pull up the task manager and navigate to the control panel and such, but never do I get a task bar or see the "Personal Settings" dialog box disappear.
Also, during all of this it never is seen on the network. After the aforementioned hour or so, it finally will start pinging and bring up the domain account profile and let me use the desktop as normal. When I look at the services, many have not started and will be stuck in "starting" or "stopping" stage without any option to control.
If I look in the event logs, many of the errors are claiming "Topology Discovery Failed" or something along the lines of not receiving a response from any of the domain controllers.
This is a HP Proliant server running HP Branded Server 2008 x64, Exchange 2010 and Blackberry Enterprise Server. At one point, everything was working great even though the OS was reporting not genuine. After a reboot though, this is when the login issues began. I was able to get the activation resolved by Microsoft and everything began working properly, so i thought it solved it - also the three mailboxes on the server were communicating fine on the clients end. I had performed a couple update rollups to the exchange server and installed some roles to be able to access OWA and it seemed to be fine for the rest of that day. Then today, no go.
Back to taking over an hour to log in with a domain account, exchange services are not starting and getting the errors regarding Topology Discovery Failure and not receiving a response from the domain controllers. We have many other servers set up in the same fashion with no problems such as this.
Any more information I can provide? Any ideas on what the heck is wrong with it?
I wish I could just start over on the entire setup but we have three mailboxes migrated to it from our corporate server and I would be TOAST if I lost them. I already am since they can't be accessed at the moment.
Any help would be water in this very dry desert I've hit.
Also, during all of this it never is seen on the network. After the aforementioned hour or so, it finally will start pinging and bring up the domain account profile and let me use the desktop as normal. When I look at the services, many have not started and will be stuck in "starting" or "stopping" stage without any option to control.
If I look in the event logs, many of the errors are claiming "Topology Discovery Failed" or something along the lines of not receiving a response from any of the domain controllers.
This is a HP Proliant server running HP Branded Server 2008 x64, Exchange 2010 and Blackberry Enterprise Server. At one point, everything was working great even though the OS was reporting not genuine. After a reboot though, this is when the login issues began. I was able to get the activation resolved by Microsoft and everything began working properly, so i thought it solved it - also the three mailboxes on the server were communicating fine on the clients end. I had performed a couple update rollups to the exchange server and installed some roles to be able to access OWA and it seemed to be fine for the rest of that day. Then today, no go.
Back to taking over an hour to log in with a domain account, exchange services are not starting and getting the errors regarding Topology Discovery Failure and not receiving a response from the domain controllers. We have many other servers set up in the same fashion with no problems such as this.
Any more information I can provide? Any ideas on what the heck is wrong with it?
I wish I could just start over on the entire setup but we have three mailboxes migrated to it from our corporate server and I would be TOAST if I lost them. I already am since they can't be accessed at the moment.
Any help would be water in this very dry desert I've hit.
Last edited:
Facebook
Twitter