Re: dsscopescan Ex5.5 to 2003 upgrade
anonymous_at_discussions.microsoft.com
Date: 09/20/04
- Next message: james: "can't open calendar after Exch5.5 migration"
- Previous message: matty: "public folders 5.5-->2k3"
- In reply to: Al Mulnick: "Re: dsscopescan Ex5.5 to 2003 upgrade"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 20 Sep 2004 12:31:16 -0700
Thanks Al, got it to work.
When I ran LDAP.exe it connected with no problem but I
was unable to authenticate. On the Exchange 5.5 server,
under site protocols for LDAP, Authentication was set to
clear text. Under Server protocols for LDAP, 'site
defaults for all properties' was checked.
I made the following change under the Site, LDAP
protocols, Authentication, checked:
Clear Text
clear text with SSL
Win NT challenge/Response
Win NT challenge/Response SSL
After I was able to authenticate with LDAP.exe and the
DSSCOPESCAN executed with no errors. Now I can move
forward.
Thanks for your help in troubleshooting.
>-----Original Message-----
>Let's start with the basics:
>
>You only have to change the LDAP port if you put 5.5 on
a 2000 DC.
>Otherwise, not to worry 'cause there is nothing to worry
about.
>Next, let's verify that you can even connect to the
directory service on the
>5.5 server. Open up the 5.5 server's LDAP provider with
LDP.EXE from the
>server you're installing it on. Can you see anything?
Remember to
>authenticate.
>Next, verify that RPC is working using RPCPING from the
Exchange
>tools/reskit (can't remember which one it comes in).
>
>Let us know what you find out.
>
>Al
><anonymous@discussions.microsoft.com> wrote in message
>news:34c901c49cf8$811c3b30$a601280a@phx.gbl...
>> thanks for the reply.
>> i changed the default LDAP port as per another message
I
>> read that port 389 may conflict with AD and the GC.
this
>> made no difference.
>>
>> I put the LDAP port back to the default. WINS was not
>> running in the environment, I removed it thinking DNS
>> would be enough.
>> Just readded WINS to a 2003 server running AD, GC, DNS,
>> dhcp.. When i look at the WINS table it seems to have
>> populated correctly.
>> When i ping my 5.5 server (exch-01) it resolves with
exch-
>> 01.onehouse.local and the correct IP. Still have the
>> same error when using DSSCOPESCAN, unable to
communicate
>> with 5.5 server.
>> Put a hard coded entry in the hosts file and tried to
>> ping 5.5 server, resolved with exch-01 and the correct
>> IP. Same error.
>> Reapplied SP6a on the exchange 5.5 server... same
error.
>>
>> This is exteremly frustrating. I'm sure its something
>> real simple but what????
>>>-----Original Message-----
>>>Why did you change the default port for LDAP? Is this
>> not installed on NT4?
>>>
>>>What about your name resolution for short names (i.e.
>> WINS)? Is that
>>>working properly?
>>>
>>>Your connection to that server is via shortname and RPC
>> at that stage IIRC.
>>>But I'd still put the LDAP port back to the default and
>> read the readme that
>>>comes with Exchange 2003 ;0)
>>>
>>>"anthonyv" <anonymous@discussions.microsoft.com> wrote
>> in message
>>>news:22e601c49cb3$f112b2b0$a401280a@phx.gbl...
>>>> Environment as follows. NT4 SP6a Exchange 5.5 SP4
BDC,
>>>> Win2003 AD, Windows 2003 stand alone server for
>> exchange
>>>> install.
>>>>
>>>> going through the EDT on exchange 2003 server. At
>> step 3
>>>> where the dsscopescan tool is run I get an error
>> message
>>>> in the logs as follows:
>>>>
>>>> Error: Could not connect to Exchange 5.5
server 'exch-
>>>> 01'. Tools that require an Exchange 5.5 server will
no
>>>> run.
>>>>
>>>> As per previous postings I have changed the LDAP on
>>>> exchange 5.5 from 389 to 390 (also tried 379)and
>>>> restarted the services but no luck.
>>>>
>>>> As far as I can tell DNS seems to be running
correctly,
>>>> BDC and AD PDC replicate, no errors in Event Logs.
>> Tried
>>>> using both administrator account and Exchange install
>>>> account(service account admin). Could not locate any
>>>> info in MS Knowledge base articles.
>>>>
>>>> Early into installation and very frustrated....
>>>
>>>
>>>.
>>>
>
>
>.
>
- Next message: james: "can't open calendar after Exch5.5 migration"
- Previous message: matty: "public folders 5.5-->2k3"
- In reply to: Al Mulnick: "Re: dsscopescan Ex5.5 to 2003 upgrade"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
