PLEASE help. The worker bee's need access to the new server in the morning... .i'm getting a error 53 on the 2008 dc that is set to host 4 vista clientsI have run dcdiag and have some errorsI can produce the dcdiag results if need be

someone please find this thread and help me solve this problemi cannot understand why clients cannot join the domain but I do havea few errors after running dcdiag which probably stem from dns misconfigurations

Hello,Which version of Vista. I don't believe Vista Basic or Home series can join a domain. To join a domain you need Vista Business, Ultimate, or Enterprise.Plese check this things to do:-The Vista must have a DC as primary DNS-You would use the FQDN of the domain to join, like mycompany.com-The time difference between vista & domain must be < 5 mnAnd also Refer this Articel : http://technet.microsoft.com/en-us/library/bb727031.aspxhttp://www.eggheadcafe.com/conversation.aspx?messageid=33307939&threadid=33283350if problem persist again post the unedited Ipconfig and Dcdiag results and event error also.Thanks... Deva --Self-trust is the first secret of success.

vista businessthe dc is the dns server, win2k8i'm going to post those things in about 2 hours from this postthank you so farall firewalls are off on client and servernetbios is enabled but no wins neededfile and printer sharing on client and server all on

Hi A client connected to an Ethernet switch may receive several logon-related error messages during startupPlease check this out : http://support.microsoft.com/kb/202840http://support.microsoft.com/kb/944353Please paste unedited Ipconfig and Dcdiag results.Thanks... Deva --Self-trust is the first secret of success.

Here is the dcdiag results Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\Administrator>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = Gorilla * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\GORILLA Starting test: Connectivity ......................... GORILLA passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\GORILLA Starting test: Advertising ......................... GORILLA passed test Advertising Starting test: FrsEvent ......................... GORILLA passed test FrsEvent Starting test: DFSREvent ......................... GORILLA passed test DFSREvent Starting test: SysVolCheck [GORILLA] An net use or LsaPolicy operation failed with error 53, The network path was not found.. ......................... GORILLA failed test SysVolCheck Starting test: KccEvent An Warning Event occurred. EventID: 0x80000B46 Time Generated: 10/04/2009 11:02:01 Event String: The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate, Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds that are performed on a cleartext (non-SSL/TLS-encrypted) connection. E ven if no clients are using such binds, configuring the server to reject them wi ll improve the security of this server. ......................... GORILLA passed test KccEvent Starting test: KnowsOfRoleHolders ......................... GORILLA passed test KnowsOfRoleHolders Starting test: MachineAccount Could not open pipe with [GORILLA]:failed with 53: The network path was not found. Could not get NetBIOSDomainName Failed can not test for HOST SPN Failed can not test for HOST SPN ......................... GORILLA passed test MachineAccount Starting test: NCSecDesc ......................... GORILLA passed test NCSecDesc Starting test: NetLogons [GORILLA] An net use or LsaPolicy operation failed with error 53, The network path was not found.. ......................... GORILLA failed test NetLogons Starting test: ObjectsReplicated ......................... GORILLA passed test ObjectsReplicated Starting test: Replications ......................... GORILLA passed test Replications Starting test: RidManager ......................... GORILLA passed test RidManager Starting test: Services Could not open Remote ipc to [Gorilla.alphamedicalaids.local]: error 0x35 "The network path was not found." ......................... GORILLA failed test Services Starting test: SystemLog An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:16:13 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:21:15 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:26:17 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:31:19 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:36:22 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:41:24 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:42:51 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:42:53 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:47:55 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:52:57 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 10:58:00 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Warning Event occurred. EventID: 0x80060005 Time Generated: 10/04/2009 11:00:45 Event String: The Virtual Storage Filter Driver is disabled through the registry. It is inactive for all disk drives. An Warning Event occurred. EventID: 0x8000001D Time Generated: 10/04/2009 11:01:57 Event String: The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Sma rt card logon may not function correctly if this problem is not resolved. To cor rect this problem, either verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate. An Warning Event occurred. EventID: 0x825A000C Time Generated: 10/04/2009 11:02:07 Event String: Time Provider NtpClient: This machine is configured to use the domai n hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to s ynchronize with an external time source. Otherwise, this machine will function a s the authoritative time source in the domain hierarchy. If an external time sou rce is not configured or used for this computer, you may choose to disable the N tpClient. An Warning Event occurred. EventID: 0x00002724 Time Generated: 10/04/2009 11:02:16 Event String: This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses. An Error Event occurred. EventID: 0xC0001B72 Time Generated: 10/04/2009 11:02:31 Event String: The following boot-start or system-start driver(s) failed to load: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 11:05:36 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 11:06:22 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 11:10:38 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: An Error Event occurred. EventID: 0x00000422 Time Generated: 10/04/2009 11:15:40 Event String: The processing of Group Policy failed. Windows attempted to read the file \\alphamedicalaids.local\sysvol\alphamedicalaids.local\Policies\{31B2F340- 016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not succes sful. Group Policy settings may not be applied until this event is resolved. Thi s issue may be transient and could be caused by one or more of the following: ......................... GORILLA failed test SystemLog Starting test: VerifyReferences ......................... GORILLA passed test VerifyReferences Running partition tests on : ForestDnsZones Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Running partition tests on : Schema Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Running partition tests on : Configuration Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Running partition tests on : alphamedicalaids Starting test: CheckSDRefDom ......................... alphamedicalaids passed test CheckSDRefDom Starting test: CrossRefValidation ......................... alphamedicalaids passed test CrossRefValidation Running enterprise tests on : alphamedicalaids.local Starting test: LocatorCheck ......................... alphamedicalaids.local passed test LocatorCheck Starting test: Intersite ......................... alphamedicalaids.local passed test Intersite <<<<<<<<the error from the client machine attempting to join the machine is this>>>>>>>>>>>>>>> network path not found hence, the client cannot join the domain

Hi there, please find the following event which is the possible root cause for the issue Could not open Remote ipc to [Gorilla.alphamedicalaids.local]: error 0x35 "The network path was not found."please check the following a) NIC and NIC bindingsb) DNS server settings. Questions=======a) are you able to access \\FQDN of the DC , i would like to see if vista client can open the sysvol folderb) are you able to access any shares on the DC ? c) Does the vista client belongs to same subnet as of DC or different subnet d) are you able to successfully stop and start the server and workstation service ?e) Please provide the value of the following registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parametersPlease note The following policies are enabled on a member computer that is running Windows Vista Service Pack 1 or Windows Server 2008 in the same domain: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always) Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (If server agrees) If you are running vista sp1 , a relevant mrxsmb.sys file version is relased Mrxsmb10.sys 6.0.6001.22156 sainath !analyze

thanks, sainath: Let me answer what i know and provide what i don't know right now later on. i'm using the embedded nic on the dc it has file and printer sharing, ipv4, ipv6 removed the dns is a static mapping of .2 to the isp server c: yes d: yes i was able to ping the dc from the clients those machines have internet access but not domain access when they try to join the domain they network path not found comes on i'll get the other info as soo nas i get to work

c: yes they are both on the same subnet

Hi tykehere, Thanks for the information , can you please post the output of ipconfig /all from the clientsainath !analyze

Sainath: Thank you for getting back w/me. I need to get to the office to provide you with what you've requested. If it's not too much to ask, could you please wait a few hours until i'm able to get you what you need? Your help is much appreciated.

Hi tykehere, thought of following up on the issue , did you had a chance to progress further ?