Huh. I thought it was concerned with the GUID. Alright. I will give that a try. Thanks.
From: Michael B. Smith [mailto:mich...@owa.smithcons.com] Sent: Tuesday, April 21, 2009 4:32 PM To: NT System Admin Issues Subject: RE: Error authenticating to exchange Database portability works fine. So...you are fine with your DC process (as long as you make it a GC first before disconnecting it from the domain). Then delete the exchange server from the lab ad. build a new server, name it the same thing, join it to the lab ad, and then restore the database. Exchange doesn't care about the server GUID. Only it's name. ________________________________ From: Jason Gauthier [jgauth...@lastar.com] Sent: Tuesday, April 21, 2009 4:25 PM To: NT System Admin Issues Subject: RE: Error authenticating to exchange Slap me silly and hand me a Ba but I can never get netdom resetpwd to work. EVER. The machine account password for the local machine could not be reset. The specified domain either does not exist or could not be contacted. The command failed to complete successfully. How would you approach it This process is usually perfect for me to get a lab instance of my domain and exchange. Im open to alternatives. From: Michael B. Smith [mailto:mich...@owa.smithcons.com] Sent: Tuesday, April 21, 2009 4:18 PM To: NT System Admin Issues Subject: RE: Error authenticating to exchange There are SO many potential problems here, it isn't even funny. Try a "netdom resetpwd". If that doesn't work - I'd probably approach this problem differently. ________________________________ From: Jason Gauthier [jgauth...@lastar.com] Sent: Tuesday, April 21, 2009 4:15 PM To: NT System Admin Issues Subject: Error authenticating to exchange Hey all, It *appears* to work f I can log in, and the services ru I installed Office onto the DC so I can do some tests with outlook. When my MAPI profile attempts to connect to exchange, I am prompted for a passw I enter my credentials, my exchange service account credentials, and anything that will work. however, none do :( I see the event log below Things of interest to note The "Logon Process" text is high asc The status code "0xC000006D" usually means bad username/passwor That is definitely not the case here. Any suggestion Dcdiag, netdiag all pass basic tes All servers are win2k3 with Exchange is also 2003 with SP2. Thanks for any help! Logon Failure: Workstation Name: LABDC Status c 0xC000006D Transited Service - ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
