Shouldn't have. The server guy used a spiffy application that takes a copy of all data on the HD, then swaps it over to the new server, and then does something with HAL to make the software match up with the hardware.
I doubt it's a timeout issue, because it takes about 10 seconds before the error pops up. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Saturday, October 18, 2008 7:06 PM To: arslist@ARSLIST.ORG Subject: Re: Urgent: Active Directory Connection is Failing ** Not sure what you upgraded, but did the upgrade change your AD timeout settings? Rick On Sat, Oct 18, 2008 at 4:50 PM, Opela, Gary L CTR USAF AFMC 72 CS/SCBAH <[EMAIL PROTECTED]> wrote: ** Well, I hope someone out there is watching the list tonight. So, here's the deal, we just upgraded servers, and now my active directory server quit working. We kept the same server name, new IP though, and new MAC. I have applied all licenses successfully. We are running Windows environment with SQL server database. I called remedy, but due to my support level, they won't help me on weekends L I'm getting an error that is just saying Failed to Connect to Active Directory Server. The documentation on the error states the following: 3375 Error Cannot connect to the directory service. This error message appears when the host name or port number for the directory service are incorrect or when authentication with the directory service fails. Any ideas? Thanks, Gary Opela, Jr. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
