Error Value 1355
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error Value 1355 The specified domain does not exist or could not be contacted Windows Server > Windows supersocket info (spnregister) error 1355 Server 2012 Setup Question 0 Sign in to vote Hi, I've just strated error 1355 domain join learning networking and (rightlyor wrongly) have decided to do so using Server 2012. The small charity I work for have kindly
Error 1355 A Time Server Could Not Be Located
let me use an old 2003 server they had stashed away in a store room (amazingly with Server 2003 still installed on it!) Anyway, Being a noobie, i foolishly just shoved in the Server
Error 1355 The Specified Domain
2012 cd and installed the server as you would windows 7, XP etc. It seemed to installed OK. I have to say that this box IS NOT connected to any network or the internet- I'm using it as a stand alone machine. I set up static ip (10.5.121.2), subnet (255.255.255.0); router ip (10.5.121.1) and preferred DNS (10.5.121.2); Computer Name= mytestlab; domain name: testlab.local (I've read that using .local error 1355 pdc role is down is not advised, but as this is a standalone box I assume it doesn't matter (?) So far so good. I then added the ADDS and DNS roles. Again all seemed to go well...until I then tried toset-upa DNS Reverse LookupZone. This is when I got the above message (amongst others) I also got the following I cannot access AD (even though its listed in Server Manager) using ADUC. I've been trying to get past this for about 3 days and am rapidly losing the will to live. I've read many many articles on how to solve this but, to be honest, huge chunks of it went way over my head. Can anyone out there take pity on me and point me in the direction of a solution which a noobie like me can make sense of? In the posts I have read, many have asked for uploads of the output of command line queriers ipconfig; nslookup; diag.exe etc. I'm sure that i will be asked the same.....unfortunately I dnt know how to do this :( I am probably the "noobiest of noobies" who has a keen interest in computing in general ...and really would like to learn more about servers\net
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for
Error 1355 Dcdiag
a Full Time Job Ways to Get Help Expand Search Submit Close Search error 1355 active directory Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > error 1355 a primary domain controller could not be located 'Primary' Domain controller not seeing global catalog Want to Advertise Here? Solved 'Primary' Domain controller not seeing global catalog Posted on 2012-12-21 Windows Server 2003 Active Directory 2 Verified Solutions 6 Comments https://social.technet.microsoft.com/Forums/sharepoint/en-US/c4b91e8e-a6b0-4ac5-829d-2723532c9f25/error-value-1355-the-specified-domain-does-not-exist-or-could-not-be-contacted?forum=winserver8setup 7,867 Views Last Modified: 2012-12-21 Situation: Active Directory domain with four total DC's. In main office subnet, One primary domain controller/DNS/DHCP server running Win2003. A secondary DC also serving DHCP and DNS but running Win2008. Two other DC's in two separate subnets. The main controller (PDXAD) is not able to view the global catalog, though the other DC's can. Unfortunately, this has had the https://www.experts-exchange.com/questions/27975655/'Primary'-Domain-controller-not-seeing-global-catalog.html effect of essentially disabling our exchange (2003) servers, as they are unable to start several exchange services - system attendant, MAT and Info Store. So, I suspect I could just shut down the PDXAD server and the exchange servers would turn to the other DC's for authentication, but I'd rather fix the problem rather than just address the symptom. The AD server in question is generating the following even log error entries; DIRECTORY SERVICES EVENT LOG: ----------------------------------------------------------------------- Event Type: Error Event Source: NTDS General Event Category: Global Catalog Event ID: 1126 Date: 12/21/2012 Time: 9:56:21 AM User: NT AUTHORITY\ANONYMOUS LOGON Computer: PDXAD Description: Active Directory was unable to establish a connection with the global catalog. Additional Data Error value: 1355 The specified domain either does not exist or could not be contacted. Internal ID: 3200cf3 User Action: Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the nltest utility to diagnose this problem. ----------------------------------------------------------------------- Event Type: Error Event Source: NTDS General Event Category: Global Catalog Event ID: 1126 Date: 12/21/2012 Time: 10:56:33 AM User: NT AUTHORITY\ANONYMOUS LOGON Compu
Crossing Join the Community! Creating your account only takes a few minutes. Join Now Hey all! So I have a client who has contacted me https://community.spiceworks.com/topic/353557-active-directory-failure with a server issue. Their active directory seems to have completely failed. I http://www.eventid.net/errorsdisplay.asp?error_code=1355 do not manage the network so I dont know the setup and things like that but the symptoms are that there is an error in the ADDS role summary saying "Active Directory Domain Services was unable to establish a connection with the global catalog". The server is Server 2008 R2 error 1355 standard. Also if you try to browse into Users and computers or sites and services it says "Naming information cannot be located because: the specified domain either does not exist or could not be contacted. Contact your system administrator to verify that your domain is properly configured and is currently online. Any help would be awesome!!! Thanks! Reply Subscribe View Best Answer RELATED error 1355 a TOPICS: Active Directory Problems Active Directory in 30 days.... Do I really need Active Directory?   1 2 Next ► 38 Replies Mace OP Gary D Williams Jun 28, 2013 at 1:06 UTC hard to say anything without know the state of the network. Do they have domain controllers up and running? Are they just missing GC's and FSMO roles or have they actually lost the AD? Do they have backups and if so what type? Physical or virtual, etc, etc 2 Pure Capsaicin OP Little Green Man Jun 28, 2013 at 1:11 UTC I would also inquire about any backups and start digging through the log files for clues. Try to find out as much about the network as you can as Gary suggested above. 2 Serrano OP Rhys Hudson Jun 28, 2013 at 1:15 UTC Right, so they only have a single server as it appears to be a small business. Why they dont have SBS is beyond me! The server its self is up and running its just active directory. I will ask about b
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 the domain has not registered an "A" record for itself in DNS. Of course, network 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) 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 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 Tru