britevo
asked on
Exchange 55. to 2003 migration - ADC will not bind to 5.5
Hi,
Migrating to 2003 and following the exchange 2003 check list - All ran ok up to the active directory connector which failed with the error cannot bind to server. I have checked the permissions on exchange 5.5 and the port number for ldap, and given administrator admin rights to the connector etc as in the documentation.
I also then tried to do the migration by building a seperate domain windows 2003 with exchange 2003 setting up trusts etc and using the mail migration tool in exchange 2003 - but this failed with cannot connect to the server - even though the permissions are correct
Any help? or ideas?
Migrating to 2003 and following the exchange 2003 check list - All ran ok up to the active directory connector which failed with the error cannot bind to server. I have checked the permissions on exchange 5.5 and the port number for ldap, and given administrator admin rights to the connector etc as in the documentation.
I also then tried to do the migration by building a seperate domain windows 2003 with exchange 2003 setting up trusts etc and using the mail migration tool in exchange 2003 - but this failed with cannot connect to the server - even though the permissions are correct
Any help? or ideas?
Hi some questions for you.
1. did you use the ADC that came with the Exchange 2003 CD or the native WIndows 2000 one?
2. Is the Exchange 5.5 Server running on NT4 or Windows 2000? If it is running on W2k you will need to change the LDAP port on Exchange 5.5 to something else as W2k grabs port 389 on startup.
3. Have you tried using telnet to access the Port on the Exchange 5.5 Server from the Exchange 2003.
4. Can you ping the Exchange 5.5 server both by name and ipaddress from the 2003 Server.
Regards.
1. did you use the ADC that came with the Exchange 2003 CD or the native WIndows 2000 one?
2. Is the Exchange 5.5 Server running on NT4 or Windows 2000? If it is running on W2k you will need to change the LDAP port on Exchange 5.5 to something else as W2k grabs port 389 on startup.
3. Have you tried using telnet to access the Port on the Exchange 5.5 Server from the Exchange 2003.
4. Can you ping the Exchange 5.5 server both by name and ipaddress from the 2003 Server.
Regards.
ASKER
1 - yes
2 - nt4
3 - yes can connect - type anything and get ----- etc.
4 - yes
2 - nt4
3 - yes can connect - type anything and get ----- etc.
4 - yes
ASKER
comments for kidego-
Nothing in the event log and a two way trust
One question is - I am able to use either route to migrate - which one would be best? The migrate to another domain and use the mail migration tool or up grade the PDC to w2003 and use ADC then install 2003 exchange as per the book
Nothing in the event log and a two way trust
One question is - I am able to use either route to migrate - which one would be best? The migrate to another domain and use the mail migration tool or up grade the PDC to w2003 and use ADC then install 2003 exchange as per the book
ASKER
I can give remote access to the test serevrs - One is a ghost image of the nt4 5.5 BDC on same Hardware the other is either a new 2003 server with 2003 exchange or an upgraded nt4 server to 2003 (server built in both ways then ghosted)
"The migrate to another domain and use the mail migration tool or up grade the PDC to w2003 and use ADC then install 2003 exchange as per the book"
I'd migrate to another domain. Install the ADMT, move the user and computer accounts, and groups if you need to. then install the ADC, and move exchange users, AFTER the AD migration has happened.
Now, back to the connection. Does the exchange 5.5 site or org name have any illegal characters? Second, have you tried using a host file instead, drop it on both servers, with identical entries for each server's IP and name? Otherwise, make the 5.5 server point to the DNS of the new AD domain controller, and make sure the DNS zone has an entry for your 5.5 server.
d
I'd migrate to another domain. Install the ADMT, move the user and computer accounts, and groups if you need to. then install the ADC, and move exchange users, AFTER the AD migration has happened.
Now, back to the connection. Does the exchange 5.5 site or org name have any illegal characters? Second, have you tried using a host file instead, drop it on both servers, with identical entries for each server's IP and name? Otherwise, make the 5.5 server point to the DNS of the new AD domain controller, and make sure the DNS zone has an entry for your 5.5 server.
d
and yes, I'd be glad to take a look thru remote access for your test servers, if you want to do so. I'm using windows 2003 and the remote desktop tool as the connection client.
D
D
ASKER
I am in the uk so its home time - plus getting kiked out by the cleaners - 'and make sure the DNS zone has an entry for your 5.5 server.'
Whats that? is it a static entry?
Whats that? is it a static entry?
yes, a static DNS entry in your AD server. It's easier with the host file, that's why I suggested it first. It ensures that both exchange servers, know EXACTLY how to contact the other.
d
d
ASKER
I have tried this build on site and got as far as installing exchange 2003 (acd ran ok) but on the install adding to existing exchange thingy it bombed out with unable to bind to exchange server - although the acd is working - I could create a new user and this was replicated to exchange 5.5 ok - just consious that i might get to the same position with the test setup
check the setup log, on the root of the C: drive. Post the error(s) where it fails to bind, we'll take a look...
D
D
ASKER
Errors from ADC setup log
[11:26:26] Entering ScHavePermissionToCreateDS Object
[11:26:26] Leaving ScHavePermissionToCreateDS Object
[11:26:26] FAnyCompPrevInstalled (f:\titanium\admin\src\eds s\edssetup \welcome.c xx:158)
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:26] FAnyCompPrevInstalled (f:\titanium\admin\src\eds s\edssetup \welcome.c xx:158)
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:27] FAnyCompPrevInstalled (f:\titanium\admin\src\eds s\edssetup \welcome.c xx:158)
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:27] FAnyCompPrevInstalled (f:\titanium\admin\src\eds s\edssetup \welcome.c xx:158)
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:27] FAnyCompPrevInstalled (f:\titanium\admin\src\eds s\edssetup \welcome.c xx:158)
Error code 0XC0070002 (2): The system cannot find the file specified.
Errors from running ADC step 3 resourse mailbox wizard
<?xml version="1.0" encoding="unicode"?><NTDSN oMatchErro rs><config uration><a ccount>Exc hange</acc ount><doma in>POLLARD </domain>< date>12/10 /03 11:37 AM</date><ex55Server>POLL0 2</ex55Ser ver><port> 389</port> <version>6 944</versi on></confi guration>< error><cod e>0XC00000 B5</code>< errormessa ge>Could not bind to the Microsoft Exchange Directory server POLL02. The Microsoft Exchange Server computer does not respond.
</errormessage></error></N TDSNoMatch Errors>
[11:26:26] Entering ScHavePermissionToCreateDS
[11:26:26] Leaving ScHavePermissionToCreateDS
[11:26:26] FAnyCompPrevInstalled (f:\titanium\admin\src\eds
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:26] FAnyCompPrevInstalled (f:\titanium\admin\src\eds
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:27] FAnyCompPrevInstalled (f:\titanium\admin\src\eds
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:27] FAnyCompPrevInstalled (f:\titanium\admin\src\eds
Error code 0XC0070002 (2): The system cannot find the file specified.
[11:26:27] FAnyCompPrevInstalled (f:\titanium\admin\src\eds
Error code 0XC0070002 (2): The system cannot find the file specified.
Errors from running ADC step 3 resourse mailbox wizard
<?xml version="1.0" encoding="unicode"?><NTDSN
</errormessage></error></N
Haven't seen this before, seems to me like it's having an issue readin the cd, is this a copy? If so, try copying the CD contents to a folder on the hard drvie, and run ADC setup from there. I can't find this error anywhere.....
D
D
OK, searching on that error code, everything I've seen is that it really can't find the file, as if it's either not there, or the files are not readable on the CD. It could also be looking for something that's been installed then removed, but still thinks it's there. this machine had exchange installed previously, then removed....maybe??
D
D
ASKER
no - used to be NT4 clean build PDC then upgraded to windows 2003
ASKER
Th cd it installed from is a downloaded image from microsoft select - but on the customers site got the same error when running ADC using an original 2003 exchange cd
ASKER
I can mail the emtire log if required?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
D