Jump to content

bornin50

Members
  • Posts

    6
  • Joined

  • Last visited

Reputation

0 Neutral

About bornin50

Personal Information

  • Occupation
    Network Manager
  • Location
    Loughborough
  1. Hi, Good news, after rebooting the Domain Controller and restarting the Exchange services the system is now online again. Thanks to Sukh for all the help along the way.
  2. Back again, "Can the users access the shared calendars as expected?" - no, Outlook reports - the connection to the Microsoft Exchange server is unavailable. "Is the issue only with the management console, i.e when trying to connect or is there a Exchange issue?" - there is an Exchange issue "What do you mean by you can see the Exchange server from the workstatation? What actions are you performing? Are you using the console successfully from the workstation?" - I can see the Exchange server in Network neighbourhood, type \\exchange2007\c$ into an explorer address line and the c: drive is browse-able. Remote desktop returns an error. "Can you logon interactively on the Exchange server and launch the console?" - I can logon to the Exchange Server from the XEN management program - via the vm console, Windows remote desktop access from a workstation will not work. "Have you checked the remote desktpo settings on the OS?" - The 2K8 Exchange Server has Remote Desktop enabled. On the Exchange Server - if I run Exchange Management Console it returns an error message - -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- The following error(s) were reported while loading topology information: get-ExchangeServer Failed Error: An Active Directory error 0x8007052E occurred while searching for domain controllers in domain ADMIN.INTERNAL: Logon failure: unknown user name or bad password. Logon failure: unknown user name or bad password. get-UMServer Failed Error: An Active Directory error 0x8007052E occurred while searching for domain controllers in domain ADMIN.INTERNAL: Logon failure: unknown user name or bad password. Logon failure: unknown user name or bad password. ____________________________________________________________________________ The most recent Exchange event in the event log is -------------------------------------------------------------------------------- Applications event log 12.31 MSEXCHANGE ADAccess 2080 Process MAD.EXE (PID=4152). Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: admin_server.ADMIN.INTERNAL CDG 1 7 7 1 0 1 1 7 1 Out-of-site: ------------------------------------------------------------------------------------------ I hope this is of some use, most of the services have reported loaded ok, including the Exchange and Blackberry ones. I think the computer account in AD is frazzled.
  3. Hi thanks for the reply, "Can you explain your setup, exchange version, OS, also how did your issue come about?" Mmmm I sorta wish you hadn't asked that, ok here goes - Xen Server hosting several VMs, one of which is 64bit 2008 r2 Windows Server running 2007 exchange server. Exchange server is purely a calendar sharing tool for the management team, who all have Blackberrys. It has taken a fair bit of setting up, but has been running nicely since November 2010. I have overview of the Network Management, but the technician who set it up is on holiday and excommunicado. Monday morning the Xen Server fell over, cause unknown, never happened before. Rebooted fine and the hosted 2k8 server also started up fine. However Exchange Management Console is not connecting to AD. I can see the Exchange server from a workstation, and connect to explore the c: drive, but I cannot remote desktop it. I have called in all favours, but Exchange triggers the 'short intake of breath' syndrome with my contacts so far, and the BB word just causes gales of hysterical laughter. I have spent hours on Google, and almost gave up but then I found this thread ...................... "Log in locally and check the event logs and post here. Look for Dsaccess for DC/GC discovery. If you have Exchange 2003 you you will have to up the logging for dsaccess." Ok I'll do this now. Colin
  4. Hi, we are in the same situation with Exchange not logging in to the domain. I have found the reset computer account mentioned as a fix, but no mention of certification services. Could you explain that to a novice please? Colin
×
×
  • Create New...