Resend... Ouch, that one isn't fun. If you want a recommendation, if that machine called XXX02 is one of the new machines, I would rename it to follow the de facto standard you have going. This is the kind of deviation that can bite you again and again. joe
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mikael Svennungsson Sent: Wednesday, May 05, 2004 5:18 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] ADC setup Hi all, Problem Solved. The ADC CA is up and running. (X400 still to set up) Please note that the ADC between DomB and E55 in DomC should be setup with the "Inter Organizational onnection Agreement" in the Advanced tab. There was an irritating flaw during the naming of the servers. The Domain was called XXXODOM (O=letter) The PDC was called XXXO1 (O=letter) The Exchange was called XXX02 (0=number) (and yes, I did not configure this name :-)) Using XXXO2 (O=letter) in lmhost file gave an error when trying to find objects when setting up the CA. and the error on duplicate names. Sorry guys, but we were four persons looking into the problem not see this obvious one. The difference between O and 0 is small in Exchange 5.5 admin :-). A set in a command prompt made it visible. Regards, /MS _____ From: [EMAIL PROTECTED] on behalf of joe Sent: Wed 2004-05-05 05:17 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] ADC setup I think the simplest way to work this would be to do a network trace and look at what bombs. If it is name res, you will see it quickly on the WINS/DNS/Broadcast calls. If it is not name res you will see it make it past that stuff and fail on something else, most likely it sounds like on some kind of call to retrieve some specific object. joe _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mikael Svennungsson Sent: Tuesday, May 04, 2004 5:56 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] ADC setup Dear all, I would like your advice concerning a setup of ADC. We have two different Exchange organizations that we want to interconnect. Our idea is to set up a X400 connector to handle mailrouting and using ADC to synchronize the directories. When setting up tha ADC-CA we run into problems that might be related to nameresolution (?). The error message is "no such object on server" when we try to choose the E5.5 container. We have added the E5.5 server as a "plain" IP entry in the lmhost file as well as added the domain and the pdc. Adding the E5.5 server in the other WINS (as Unique) gives the same error. Trying to do a net use to the E5.5 netbios name from the AD exchange box gives a error message complaining over duplicate names. Any suggestions? I am on the right track when looking for netbios name resolution problems? Any other way to acheve the same result? Tech stuff: Three Domains: DomA (NT4), DomB( W2K3), DomC (NT4)( this is the new one) DomA-DomB two-way trust (same WINS) and DomB-DomC two-way trust (using LMHOST entries) Two Ex-orgs EoA (for DomA and DomB) , EoC (for DomC), different Org and Site names DomA-E5.5, DomB-E2K3, DomC-E5.5 ADC CA's up and running between Ex in DomA and DC in DomB DomA and DomB sharing WINS, DomC separate WINS Want to create ADC between DomB and E55 in DomC. Accounts used: domain admin and exch system admin. X400 between EoA and EoC to handle mail routing TIA, /MS
<<attachment: winmail.dat>>
