Home
Extended ECM
API, SDK, REST and Web Services
Network Path not found
Fokko_Stalman_(stalmanf_-_(deleted))
We're using LL9.0.0.1 on windows2000 with directory services 2.2.0. We're using NTLM synchronisation with a local NT-usergroup containing lots of users from several domains (NT4 and Windows2000 domains).Our Livelink servers are in the Netherlands. We also want to synchronise some users from a windows 2000 domain in Nigeria. The users from the domain in Nigeria are not synchronised.The synchronisation-logfile shows Synchronizing domain\user1Synchronizing domain\user2Synchronizing domain\user3Synchronizing domain\user4But user1, user2, user3 and user4 are not created in Livelink.Usually the synchronisation-logfile showsSynchronizing domain\user1 Found user 'domian\user1' in NTLM with ID 1234567 Updating domain\user1 ....Synchronizing domain\user2 Found user 'domian\user2' in NTLM with ID 2345678 Updating domain\user2 ....Synchronizing domain\user3 Found user 'domian\user3' in NTLM with ID 3456789 Updating domain\user3 ....So, we don't have an error-message but the users are not created in Livelink.We also tried to synchronise these users on a testenvironment on NT4. This resulted in a error-message in the synchronisation-logfile:Network Path not found.We checked the trust between de domains and it seems ok.The connection is low-speed.Is there something like a max-time-out that is exceeded?Kind regards,Fokko StalmanFCDF
Find more posts tagged with
Comments
James Mernin
I'm not an expert but I always thought that you needed LDAP for W2k AD domain synchronization. Another suggestion would be to start the Livelink service using a domain account that has Account Operators rights to both domains. I don't thik that the livelink query is any heavier on network traffic than a normal user login from the Netherlands to Nigeria. If it is then try adding just one account at a time from the Nigeria domain.
Chris_Wagg
Message from Chris Wagg via eLinkNo, you don't need to use LDAP to synchronise W2K AD domain, NTLM will work as well.The Network path error is almost always related to a trust issue, or, possibly a DNS issue that makes it so the Livelink servercan't resolve the NT server name.Chris