1355 Error
Contents |
One games Xbox 360 games PC 1355 error joining domain games Windows games Windows phone games Entertainment All error 1355 the specified domain Entertainment Movies & TV Music Business & Education Business Students &
Dcdiag Error 1355
educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
Dcgetdcname Pdc Required Call Failed Error 1355
Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft spnregister error 1355 Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 29 Sep 2016 19:08:07 GMT by s_hv1000 (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 http://www.eventid.net/errorsdisplay.asp?error_code=1355 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 http://www.networksteve.com/enterprise/topic.php/Can't_get_machine_to_join_the_domain_/_error_1355/?TopicId=59421&Posts=5 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 error 1355 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 1355 error joining 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 Trusts, File Service Product Operations Guide, Diagnosing an
another Task Sequence (on a Lenovo M90P) and have the machine join the domain and cant get it to work. I always end up with the following in the Task Sequence event log : ==============================[ OSDNetSettings.exe ]=========================== Command line: "osdnetsettings.exe" configure Setting %SystemRoot% to "C:\Windows" Loading existing answer file "C:\Windows\panther\unattend\unattend.xml" Configuring global network settings Join type: 0 Joining domain: XXXXX Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "x86" DNS domain: DNS domain search order: IP filter sec enabled: false No adapters found in environment. Performing global configuration only. Writing configuration information to C:\Windows\panther\unattend\unattend.xml Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml Configuring "OSDNetSettings.exe finalize" to run on first bootOSDNetSettings finished: 0x00000000. Concerning the No Adapters found in environment, I suspected a problem with the NIC driver so I checked the network settings using F8 and when the join domain command runs, I confirmed that I have an IP address on my network and can ping the DC. Even when the PC boots up at the end (but not on the domain) the network drivers are present and working so I dont think it is a NIC driver issue I also reapplied the NIC driver and added a reboot before adding the computer to the domain, just in case, with no luck I confirmed the account has the rights to add a computer to the domain. Also tried different OU, no OU (so it would go in Computers), still not working. I also checked the following log file and here is what I have C:\Windows\panther\unattendGC\setupact.LOG Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355] Error [DJOIN.EXE] Unattended Join: Unable to join; gdwerror = 0x54b The file C:\Windows\Debug\Netsetup.log has nothing new but what has been done when I first created the base image (joining the domain to WORKGROUP) Does anybody have a clue of what could be the problem? I also tried to recreate and recapture the Base image, with no luck. Could that be a problem with the unattend.xml that I use while creating the base image ? Do I need something special in there ? Or is it really something on the network that could prevent OSD from reaching the DC even if it can be pinged but would not allow OSD to communicate to add the computer to the domain ? I am kinda stuck right now so thanks for all the input you can bring J July