Error 1355 Migration Failed |
Post Reply |
Author | |
boatasiaus
Newbie Joined: 09 Feb 2010 Status: Offline Points: 2 |
Post Options
Thanks(0)
Posted: 09 Feb 2010 at 9:14am |
Trying to migrate user profiles/join a sbs 2003 domain from a workgroup, and am getting the above referenced error. All other steps in the migration, as displayed in the User Profile Wizard, complete fine to that point. This occurrs on both XP Pro SP3 and WIN 7 Pro machines. A manual join to the domain works fine.
NIC DNS is pointing to SBS server, and DHCP is enabled on the workstations
Any pointers to resolve the issue would be appreciated.
|
|
Support
Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1844 |
Post Options
Thanks(0)
|
Hi,
As you have implied, this problem is usually down to a name resolution issue. Error 1355 is a Windows System error meaning "The specified domain either does not exist or could not be contacted."
How are you specifying the domain name? If you are using a flat, NetBIOS name, you may have a WINS issue not a DNS issue. As a general point, you must ensure there are "Forwarders" entries to the new domain DNS on any existing DNS servers. Windows does not just need to resolve the domain and DC names to an IP address, it also needs to resolve service location (SRV) resource records.
As a quick and dirty test, if you are using a NetBIOS domain name try a DNS name, and vice versa.
|
|
boatasiaus
Newbie Joined: 09 Feb 2010 Status: Offline Points: 2 |
Post Options
Thanks(0)
|
Thanks for the reply
Just to close this thread out for future searches, error 1355, implies an issue with DNS.
When I ran dcdiag, a connectivity issue with DNS was reported. The exact error was "the host (GUID XXXXX)_msdcs.failedserver.local could not be resolved to an ip address. Check DNS, DHCP, server name, etc. Although the GUID XXXX )_msdcs.failedserver.local DNS name couldn't be resolved the server name resolved the the IP address and is pingable".
To resolve, I ended up deleteing the entry in the DNS Forward lookup zone _mscds folder. I then ran netdiag /fix, which forced the server roles to re-register in DNS. Running dcdiag /fix & netdiag /fix without deleting the existing DNS entry failed to resolve the problem. Edited by boatasiaus - 10 Feb 2010 at 8:56am |
|
Support
Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1844 |
Post Options
Thanks(0)
|
Thanks for letting us know. This is really useful
|
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |