Print Page | Close Window

Error 1722

Printed From: ForensiT
Category: ForensiT Support
Forum Name: Domain Migration
Forum Discription: User Profile Wizard questions, suggestions, comments and bug reports
URL: http://forum.ForensiT.com/forum_posts.asp?TID=45
Printed Date: 20 Jun 2019 at 8:40am


Topic: Error 1722
Posted By: aristaken
Subject: Error 1722
Date Posted: 18 Jul 2007 at 6:50pm
I am tring to migrate profiles on a nt4 domain to a new 2003 AD domain I keep getting an error message of
 
Finding Domain Controller for domain ARISTAgroup... Done.
Using Domain Controller: file://\\dc1.Aristagroup.local - \\dc1.Aristagroup.local .
Binding to Active Directory...Fails.
Error 1722.
 
What am i doing wrong?
Thanks


-------------
Arista Ken



Replies:
Posted By: Support
Date Posted: 18 Jul 2007 at 7:55pm
Hi,
 
Error 1722 is a Windows error meaning "The RPC server is unavailable." Please refer to the "Troubleshooting" chapter of the http://www.forensit.com/Downloads/User%20Profile%20Wizard%202.5%20User%20Guide.pdf - User Guide .


Posted By: aristaken
Date Posted: 18 Jul 2007 at 10:55pm
I have my dns from both domains working (i.e. I can ping by name into both domains)  I still get the RPC server is unavaliable Error or an Unable to bind to domain.local.
 
Now what?


Posted By: aristaken
Date Posted: 18 Jul 2007 at 11:15pm
ok now more to this question
What is the proper syntax for this operation the help files are not overly clear.  I tried this two different ways and get two different errors.
 
below are the two diferent way I tried this.
 
Finding Domain Controller for domain ARISTAgroup... Done.
Using Domain Controller: file://dc1.aristagroup.local/ - \\dc1.Aristagroup.local .
Binding to Active Directory...Fails.
Error 1722.
http://www.ForensiT.com -  
Finding Domain Controller for domain ARISTAgroup.local... Done.
Using Domain Controller: file://\\DC1 - \\DC1 .
WARNING: DC cannot return DNS names.
Binding to Active Directory... Done.
Getting Domain SID for user " mailto:kenb@aristagroup.local - kenb@aristagroup.local "... Fails.


-------------
Arista Ken


Posted By: Support
Date Posted: 19 Jul 2007 at 9:49am
Your network is not optimally configured. The fact that the DC is unable to return a name in DNS format underlines this. Have you added a "Forwarders" entry for your new domain on your existing DNS server as stated in the "Troubleshooting" chapter of the User Guide? If you haven't you will have problems.
 
The fact that you can ping your DC is irrelevant here: the Wizard has already found the DC. The RPC subsystem on the workstation separately needs to locate the DC and negotiate a connection. When you specify a the domain name in NetBIOS format, RPC cannot find a DC to bind to. When you specify the domain name DNS format, the bind request can be routed but the DC cannot resolve the UPN user name.
 


Posted By: aristaken
Date Posted: 19 Jul 2007 at 8:55pm
Hi
OK i fixed my dns and netbois and lmhost files.
I was even able to get through a user profile wizard up until it tried to join the domain.  the error said I had to many open sessions with the server so I closed everything and tried again.  This time the profile I wanted to use is not listed the way it was the first time.  now it had a bunch of numbers infront of it.
 
so now what?
 
I like this utility but I can't see buying it for the rest of my conversion if I can't get it to work for one user.
 


-------------
Arista Ken


Posted By: Support
Date Posted: 19 Jul 2007 at 9:26pm
When you ran the Wizard it migrated the profile before trying to join the domain. If you then logged on again with the original user account, Windows will have created a new profile. To migrate the original profile select "Show Unassigned Profiles" on the "Select a User Profile Page" and choose the profile.



Print Page | Close Window