Error 1355
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error 1355 - The specified domain either does not exists etc... Archived Forums I-L > Identity Lifecycle error 1355 server 2012 Manager Question 0 Sign in to vote This error happens when creating error 1355 all gc's are down a AD management agent pointing to another forest. I 've read here that this is a DNS-related error. Can it have
Supersocket Info (spnregister) Error 1355
another cause? Here is my environment: Forest A with MIIS in it and Forest B. I have set up a DNS zone transfer from Forest B to Forest A - so every
Error 1355 Domain Join
DNS-Information from Forest B can be found on the DNS-servers in Forest A. Zone transfer is working without errors. This can be proved - a nslookup in Forest A with a "ls -d -command" shows all infos from the DNS-zone in forest B. I tried to run the miisdcinfo-tool from the resource kit, but this gives me simply a "No domain controller is available or the domain error 1355 a time server could not be located does not exists" when entering the name of Forest B under "Directory Partition". The domain controllers in Forest B are reachable on port 88, 389, 464. What else can I check? Thanks for your answers Thursday, April 17, 2008 10:10 AM Answers 0 Sign in to vote Michael, have you tried to use the IP address of the target DC? If that works, you still have a DNS problem.. (See a post of Markus on : http://tech.groups.yahoo.com/group/MMSUG/message/6208) HTH, Peter Thursday, April 17, 2008 10:27 AM All replies 0 Sign in to vote Michael, have you tried to use the IP address of the target DC? If that works, you still have a DNS problem.. (See a post of Markus on : http://tech.groups.yahoo.com/group/MMSUG/message/6208) HTH, Peter Thursday, April 17, 2008 10:27 AM 0 Sign in to vote Michael, did you also check that the account specified in the ADMA connection info has the "Replicating Directory Changes"? http://support.microsoft.com/?kbid=303972 HTH,Peter Thursday, April 17, 2008 10:36 AM 0 Sign in to vote That is weird! I added the ip addresses of the dcs (as preferred domain controllers) of the target forest and it works! Thanks for t
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 00:23:31 GMT by s_ac4 (squid/3.5.20)
EventID.Net Make sure that the Domain Controller is not offline or that its name is not mistyped. Try to ping the FQDN (Fully Qualified Domain Name) of the DC. For example, this problem can occur if a domain controller in http://www.eventid.net/errorsdisplay.asp?error_code=1355 the domain has not registered an "A" record for itself in DNS. Of course, network http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located connectivity and DNS problems could cause this problem, so check for this type of problems too. Here are some examples when this error may occur: - M228328 - This behavior can occur if there is no network protocol installed on the computer. - M239897 - In this case, the computer was unable to contact a Domain Name Server (DNS) error 1355 server. - M252137 - The computer was unable to contact a global catalog server. - M258832 - In this case, NetBIOS over TCP/IP was disabled on the client computer. - M259374 - This problem can occur if the server that is running the Domain Name System (DNS) service has not registered an "A" record for itself in DNS. - M279212 - The error appears if you provide an incorrect domain name when you are prompted error 1355 a for your credentials. - M298656 - Domain Name System (DNS) server problems caused the error in this case. - M299563 - This error can appear if the Netlogon service is not started. - M312467 - This article describes a situation in which IPSec policies were configured to allow only secure communication between the Exchange 2000 server and the Global Catalog server. - M810402 - Norton Internet Security 2002 prevented clients from joining a domain in this case. M839880 shows information on how to troubleshoot RPC Endpoint Mapper errors. See the links below for further information on this error. Links: M227747, M228328, M239897, M247151, M252137, M256083, M257623, M258832, M259374, M264008, M266324, M273428, M274320, M279212, M283133, M285800, M286360, M287918, M289549, M297096, M298656, M299563, M306101, M310461, M312467, M314366, M324174, M324949, M325874, M327121, M810402, M810812, M812680, M827182, M828813, M832214, M834826, M834859, M839880, M840518, M875429, Troubleshooting E-mail services, Active Directory Operations Overview, Replication Features and Forest to Forest Trusts, File Service Product Operations Guide, Diagnosing and Troubleshooting Active Directory Problems, Solution Operations Guide - Directory Services Search: Keywords: error code 1355 and Network: Google - Bing - Microsoft - Yahoo Keywords: The specified domain either does not exist or could not be contacted. ERROR_NO_SUCH_DOMAIN: Google - Bing - Microsoft - Yahoo Feedback: If you have additional details about this error code, please send it to us.
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Domain Controller DCdiag error - A Global Catalog Server could not be located up vote 3 down vote favorite 1 I've set up a replica DC in a remote location. It's connected to the main site through a VPN connection. DCdiag passes on the primary DC, but I get the following error on the replica DC: Running enterprise tests on : mydomain.co.uk Starting test: LocatorCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. ......................... mydomain.co.uk failed test LocatorCheck Is it giving this error just because it is not the global catalogue server, or is there some connectivity issue where it does not think there is one at all, as the error seems to imply? If so, it seems odd, as all other tests were passed. What do I do about this? windows-server-2008-r2 domain-controller active-directory share|improve this question asked Mar 16 '12 at 2:35 paradroid 62931022 How's DNS set up on the replica? –Shane Madden♦ Mar 16 '12 at 2:58 @ShaneMadden: It was set up through netdom join. I assumed that was all that was needed. The DNS entries appear to have been replicated, apart from the DCs themselves (the original DC appears on both DNS databases, but the replica only appears through dig on the original, but with two entries, one being an out-of-date address). –paradroid Mar 16 '12 at 3:24 1 Are you in some kind of recovery scenario? The server is doing SRV record lookups to try and find the server holding the PDC Emulator FSMO role as well as looking for a Global Catalog server. I believe Shane was referring to the DNS client settings on the NIC of the remote ser