First MSDSS sync fails

  • Thread starter Thread starter Dick Knowles
  • Start date Start date
D

Dick Knowles

Hi

I have installed MSDSS successfully, but the first synchronization fails
with the messages below. I have checked that the NDS schema has extended
correctly. The NDS account name and password must be good, because if I
enter them wrongly, I cannot get to the next window. We are using Netware
5.1 and eDir 8.6.2. Does this mean that these are not supported or is there
another explanation?

Dick

------------------------------------------

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The session was created successfully.

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The reverse synchronization session has started.

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The read provider failed to open the base object
'NDS://ABC/O=ABCD/OU=MDSS-Test/OU=Test1'. Please verify that the object path
and credentials are valid.

Error code (0x800704b8): An extended error has occured (0x8890).

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The read provider for the publisher failed to initialize.

Error code (0x800704b8): An extended error has occurred.

Among the objects mapped,
0 objects were written.
0 objects failed.
0 objects were added to the Failed Object List.


From the Failed Object List,
0 objects were successfully written,
0 objects expired.


Error code (0x800704b8): An extended error has occurred.

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The forward synchronization session has started.

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The write provider failed to log in. Please verify that credentials are
valid.

Error code (0x800704b8): An extended error has occured (0x8890).

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The write provider for the subscriber failed to initialize.

Error code (0x800704b8): An extended error has occurred.

Session (7): AD:sw,ab,abcde to NDS:ABCD/MDSS-Test/Test1

The forward synchronization session has terminated with a failure. Objects
will be re-read from source directory. Before the failure,
0 objects were read,
0 objects were mapped.

Among the objects mapped,
0 objects were written.
0 objects failed.
0 objects were added to the Failed Object List.


From the Failed Object List,
0 objects were successfully written,
0 objects expired.


Error code (0x800704b8): An extended error has occurred.
 
Dick,



It looks like we failed to read 'NDS://ABC/O=ABCD/OU=MDSS-Test/OU=Test1',
can you re-verify the syntax?



Also, make sure the following is true.

- 1. NetWare client is at lease 4.83 SP2 or above.

- - http://download.novell.com/filedist/pages/PublicSearch.jsp

- 2. MSDSS SP1 is installed.

- - http://www.microsoft.com/windows2000/sfn/msdsssp1.asp



Finally, is there an event log error?



Kindly post the result on this group so we can all try to help.



Sincerely,
Ming Chen, MCSE, MCSA, MCDBA, CNE
Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please Reply to Group via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided AS IS with no warranties, and confers no rights.
 
Ming

I had not found the Service Pack, so I downloaded it and applied.

The Netware Client is 4.83 SP2.

I browsed for the OU and Domain, so I assume the syntax generated was
correct..

The messages in the original posting are from the event log. (edited to
remove company identification).

I reran the synchronisation attempt, but got the same set of messages.

Dick
 
Hmmm..



Dick,



1. Put both IP & IPX on MSDSS.

2. Create a test OU on NDS without spaces in the name, put just the user in
it.

- Create a new MSDSS session, verify we are using Admin account for both
NDS and AD and migrate the test users, does it still have the same error?



Finally, as a long shot, install MSDSS on a different DC and see if you have
the same result.



Hope the information helped.



Sincerely,
Ming Chen, MCSE, MCSA, MCDBA, CNE
Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please Reply to Group via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided AS IS with no warranties, and confers no rights.
 
Ming

1. The server is setup with both protocols. Is that what you mean?

2. The OU that I was synchronising is a test OU and there are no spaces in
any of the names. I deleted all the other test objects, leaving just one
account

3. The NDS account is Admin, but the AD account is Administrator. Am I
supposed to create an additional AD account?

4. This is a test prior to creating a production Domain server. This is the
only domain server we have.

I retried with as many variations as I could (different password rules, with
and without filters, etc), but always get the same result.

Dick
 
At last, I made progress. For anyone else suffering the same problem , the
eventaul solution was to reinstall the Netware client on the Windows server.
This time I selected both IPX and IP protocols.

(We use IPX Network address restrictions for our accounts. In order for this
to work, machines must log in using the IPX protocol. If we install the
Workstation Netware clients with both protocols, they try to log in using
IP, even though they are set up with IPX as the preferred protocol)

In attempting to resolve the problem, I created new Netware servers in new
trees with various Netware versions, patch levels and server applications.
None of these would fail, so I do not know what is going on.

Dick
 
Back
Top