Results 1 to 8 of 8

Thread: Domain cannot be found

  1. 06-01-2008 #1
    karlman Guest

    Domain cannot be found

    I am getting several client errors related to the domain not being
    found (listed below). I am running a single domain controller
    (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    domain appears to be working okay becuase DNS, shares, exchange, SQL
    are all accessible. Originally the logon script was working fine but
    then I noticed this error cropping up. Not sure what I may have
    changed.

    Any ideas on what to check?

    Thanks
    Karl


    From XP Pro clients:
    =====================================
    Event Type: Error
    Event Source: Userenv
    Event Category: None
    Event ID: 1054
    Date: 1/5/2008
    Time: 9:46:34 AM
    User: NT AUTHORITY\SYSTEM
    Computer: COMP-A
    Description:
    Windows cannot obtain the domain controller name for your computer
    network. (The specified domain either does not exist or could not be
    contacted. ). Group Policy processing aborted.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

    -- AND --

    Event Type: Error
    Event Source: UserInit
    Event Category: None
    Event ID: 1000
    Date: 1/5/2008
    Time: 2:06:29 PM
    User: N/A
    Computer: VWORKINGBOX
    Description:
    Could not execute the following script Logon.vbs. The system cannot
    find the file specified.
    ..

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.


    -- AND --

    Event Type: Error
    Event Source: Userenv
    Event Category: None
    Event ID: 1053
    Date: 1/5/2008
    Time: 2:06:44 PM
    User: NT AUTHORITY\SYSTEM
    Computer: VWORKINGBOX
    Description:
    Windows cannot determine the user or computer name. (The specified
    domain either does not exist or could not be contacted. ). Group
    Policy processing aborted.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.


    I also get this from my Virtual Server 2005 running on the DC
    ==================================================
    Event Type: Warning
    Event Source: Virtual Server
    Event Category: Virtual Server
    Event ID: 1136
    Date: 1/5/2008
    Time: 1:46:57 PM
    User: NT AUTHORITY\NETWORK SERVICE
    Computer: MATRIX
    Description:
    An error has occured during the creation of Service Connection points
    for Virtual Server in Active Directory. Either a domain controller is
    not available to complete the operation or there is a security problem
    accessing the domain. This operation will be retried the next time the
    service starts. Error 0x80070005 - Access is denied.


    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Reply With Quote Reply With Quote
  2. 06-01-2008 #2
    karlman Guest

    Re: Domain cannot be found

    On Jan 5, 2:23 pm, karlman <karlma...@gmail.com> wrote:
    > I am getting several client errors related to the domain not being
    > found (listed below). I am running a single domain controller
    > (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    > domain appears to be working okay becuase DNS, shares, exchange, SQL
    > are all accessible. Originally the logon script was working fine but
    > then I noticed this error cropping up. Not sure what I may have
    > changed.
    >
    > Any ideas on what to check?
    >
    > Thanks
    > Karl
    >
    > From XP Pro clients:
    > =====================================
    > Event Type: Error
    > Event Source: Userenv
    > Event Category: None
    > Event ID: 1054
    > Date: 1/5/2008
    > Time: 9:46:34 AM
    > User: NT AUTHORITY\SYSTEM
    > Computer: COMP-A
    > Description:
    > Windows cannot obtain the domain controller name for your computer
    > network. (The specified domain either does not exist or could not be
    > contacted. ). Group Policy processing aborted.
    >
    > For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
    >
    > -- AND --
    >
    > Event Type: Error
    > Event Source: UserInit
    > Event Category: None
    > Event ID: 1000
    > Date: 1/5/2008
    > Time: 2:06:29 PM
    > User: N/A
    > Computer: VWORKINGBOX
    > Description:
    > Could not execute the following script Logon.vbs. The system cannot
    > find the file specified.
    > .
    >
    > For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
    >
    > -- AND --
    >
    > Event Type: Error
    > Event Source: Userenv
    > Event Category: None
    > Event ID: 1053
    > Date: 1/5/2008
    > Time: 2:06:44 PM
    > User: NT AUTHORITY\SYSTEM
    > Computer: VWORKINGBOX
    > Description:
    > Windows cannot determine the user or computer name. (The specified
    > domain either does not exist or could not be contacted. ). Group
    > Policy processing aborted.
    >
    > For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
    >
    > I also get this from my Virtual Server 2005 running on the DC
    > ==================================================
    > Event Type: Warning
    > Event Source: Virtual Server
    > Event Category: Virtual Server
    > Event ID: 1136
    > Date: 1/5/2008
    > Time: 1:46:57 PM
    > User: NT AUTHORITY\NETWORK SERVICE
    > Computer: MATRIX
    > Description:
    > An error has occured during the creation of Service Connection points
    > for Virtual Server in Active Directory. Either a domain controller is
    > not available to complete the operation or there is a security problem
    > accessing the domain. This operation will be retried the next time the
    > service starts. Error 0x80070005 - Access is denied.
    >
    > For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

    So I may have found out part of my problem. I found a reference in DNS
    to my old domain controller that was retired. After I removed that it
    seems to have corrected the issues with the clients. Time will tell.
    It is odd though because it was working fine earlier with that
    reference in there.

    I am still getting the issue when Virtual Server 2005 starts but they
    may be something to ask another group.

    Thanks
    Reply With Quote Reply With Quote
  3. 06-01-2008 #3
    Meinolf Weber Guest

    Re: Domain cannot be found

    Hello karlman,

    You wrote about a removed DC, how did you remove it?

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

    > On Jan 5, 2:23 pm, karlman <karlma...@gmail.com> wrote:
    >
    >> I am getting several client errors related to the domain not being
    >> found (listed below). I am running a single domain controller
    >> (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    >> domain appears to be working okay becuase DNS, shares, exchange, SQL
    >> are all accessible. Originally the logon script was working fine but
    >> then I noticed this error cropping up. Not sure what I may have
    >> changed.
    >>
    >> Any ideas on what to check?
    >>
    >> Thanks
    >> Karl
    >> From XP Pro clients:
    >> =====================================
    >> Event Type: Error
    >> Event Source: Userenv
    >> Event Category: None
    >> Event ID: 1054
    >> Date: 1/5/2008
    >> Time: 9:46:34 AM
    >> User: NT AUTHORITY\SYSTEM
    >> Computer: COMP-A
    >> Description:
    >> Windows cannot obtain the domain controller name for your computer
    >> network. (The specified domain either does not exist or could not be
    >> contacted. ). Group Policy processing aborted.
    >> For more information, see Help and Support Center
    >> athttp://go.microsoft.com/fwlink/events.asp.
    >>
    >> -- AND --
    >>
    >> Event Type: Error
    >> Event Source: UserInit
    >> Event Category: None
    >> Event ID: 1000
    >> Date: 1/5/2008
    >> Time: 2:06:29 PM
    >> User: N/A
    >> Computer: VWORKINGBOX
    >> Description:
    >> Could not execute the following script Logon.vbs. The system cannot
    >> find the file specified.
    >> .
    >> For more information, see Help and Support Center
    >> athttp://go.microsoft.com/fwlink/events.asp.
    >>
    >> -- AND --
    >>
    >> Event Type: Error
    >> Event Source: Userenv
    >> Event Category: None
    >> Event ID: 1053
    >> Date: 1/5/2008
    >> Time: 2:06:44 PM
    >> User: NT AUTHORITY\SYSTEM
    >> Computer: VWORKINGBOX
    >> Description:
    >> Windows cannot determine the user or computer name. (The specified
    >> domain either does not exist or could not be contacted. ). Group
    >> Policy processing aborted.
    >> For more information, see Help and Support Center
    >> athttp://go.microsoft.com/fwlink/events.asp.
    >>
    >> I also get this from my Virtual Server 2005 running on the DC
    >> ==================================================
    >> Event Type: Warning
    >> Event Source: Virtual Server
    >> Event Category: Virtual Server
    >> Event ID: 1136
    >> Date: 1/5/2008
    >> Time: 1:46:57 PM
    >> User: NT AUTHORITY\NETWORK SERVICE
    >> Computer: MATRIX
    >> Description:
    >> An error has occured during the creation of Service Connection points
    >> for Virtual Server in Active Directory. Either a domain controller is
    >> not available to complete the operation or there is a security
    >> problem
    >> accessing the domain. This operation will be retried the next time
    >> the
    >> service starts. Error 0x80070005 - Access is denied.
    >> For more information, see Help and Support Center
    >> athttp://go.microsoft.com/fwlink/events.asp.
    >>
    > So I may have found out part of my problem. I found a reference in DNS
    > to my old domain controller that was retired. After I removed that it
    > seems to have corrected the issues with the clients. Time will tell.
    > It is odd though because it was working fine earlier with that
    > reference in there.
    >
    > I am still getting the issue when Virtual Server 2005 starts but they
    > may be something to ask another group.
    >
    > Thanks
    >


    Reply With Quote Reply With Quote
  4. 06-01-2008 #4
    Kevin D. Goodknecht Sr. [MVP] Guest

    Re: Domain cannot be found

    Read inline please.

    In news:d8fc4d1e-8315-49f1-8371-b411dabfc8c6@i7g2000prf.googlegroups.com,
    karlman <karlman68@gmail.com> typed:
    > I am getting several client errors related to the domain not being
    > found (listed below). I am running a single domain controller
    > (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    > domain appears to be working okay becuase DNS, shares, exchange, SQL
    > are all accessible. Originally the logon script was working fine but
    > then I noticed this error cropping up. Not sure what I may have
    > changed.
    >
    > Any ideas on what to check?
    >
    > Thanks
    > Karl
    >
    >
    > From XP Pro clients:
    > =====================================
    > Event Type: Error
    > Event Source: Userenv
    > Event Category: None
    > Event ID: 1054
    > Date: 1/5/2008
    > Time: 9:46:34 AM
    > User: NT AUTHORITY\SYSTEM
    > Computer: COMP-A
    > Description:
    > Windows cannot obtain the domain controller name for your computer
    > network. (The specified domain either does not exist or could not be
    > contacted. ). Group Policy processing aborted.
    >
    > For more information, see Help and Support Center at
    > http://go.microsoft.com/fwlink/events.asp.
    >
    > -- AND --
    >
    > Event Type: Error
    > Event Source: UserInit
    > Event Category: None
    > Event ID: 1000
    > Date: 1/5/2008
    > Time: 2:06:29 PM
    > User: N/A
    > Computer: VWORKINGBOX
    > Description:
    > Could not execute the following script Logon.vbs. The system cannot
    > find the file specified.
    > .
    >
    > For more information, see Help and Support Center at
    > http://go.microsoft.com/fwlink/events.asp.
    >
    >
    > -- AND --
    >
    > Event Type: Error
    > Event Source: Userenv
    > Event Category: None
    > Event ID: 1053
    > Date: 1/5/2008
    > Time: 2:06:44 PM
    > User: NT AUTHORITY\SYSTEM
    > Computer: VWORKINGBOX
    > Description:
    > Windows cannot determine the user or computer name. (The specified
    > domain either does not exist or could not be contacted. ). Group
    > Policy processing aborted.
    >
    > For more information, see Help and Support Center at
    > http://go.microsoft.com/fwlink/events.asp.
    >
    >
    > I also get this from my Virtual Server 2005 running on the DC
    > ==================================================
    > Event Type: Warning
    > Event Source: Virtual Server
    > Event Category: Virtual Server
    > Event ID: 1136
    > Date: 1/5/2008
    > Time: 1:46:57 PM
    > User: NT AUTHORITY\NETWORK SERVICE
    > Computer: MATRIX
    > Description:
    > An error has occured during the creation of Service Connection points
    > for Virtual Server in Active Directory. Either a domain controller is
    > not available to complete the operation or there is a security problem
    > accessing the domain. This operation will be retried the next time the
    > service starts. Error 0x80070005 - Access is denied.

    Make sure all DNS Clients use only the internal AD DNS in TCP/IP properties,
    and that the (same as parent folder) A record in the AD Domain zone has not
    been modified from using only DCs for their IP addresses.

    Make sure the DFS Service on the DCs is running and set to Auto start.

    Also, the TCP/IP NetBIOS helper serive is required for accessing DFS shares.

    Open the DFS shares by using \\ADDomain\SYSVOL or \\ADDomain\NETLOGON right
    click in the window, choose properties, then select the Dfs tab of the
    properties sheet, select and check the Status of all DCs on the tab.



    --
    Best regards,
    Kevin D. Goodknecht Sr. [MVP]
    Hope This Helps

    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    http://support.wftx.us/
    http://message.wftx.us/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================


    Reply With Quote Reply With Quote
  5. 07-01-2008 #5
    karlman Guest

    Re: Domain cannot be found

    On Jan 5, 4:08 pm, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
    > Hello karlman,
    >
    > You wrote about a removed DC, how did you remove it?
    >
    > Best regards
    >
    > Meinolf Weber
    > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    > no rights.
    > ** Please do NOT email, only reply to Newsgroups
    > ** HELP us help YOU!!!http://www.dts-l.org/goodpost.htm
    >
    >
    >
    > > On Jan 5, 2:23 pm, karlman <karlma...@gmail.com> wrote:
    >
    > >> I am getting several client errors related to the domain not being
    > >> found (listed below). I am running a single domain controller
    > >> (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    > >> domain appears to be working okay becuase DNS, shares, exchange, SQL
    > >> are all accessible. Originally the logon script was working fine but
    > >> then I noticed this error cropping up. Not sure what I may have
    > >> changed.
    >
    > >> Any ideas on what to check?
    >
    > >> Thanks
    > >> Karl
    > >> From XP Pro clients:
    > >> =====================================
    > >> Event Type: Error
    > >> Event Source: Userenv
    > >> Event Category: None
    > >> Event ID: 1054
    > >> Date: 1/5/2008
    > >> Time: 9:46:34 AM
    > >> User: NT AUTHORITY\SYSTEM
    > >> Computer: COMP-A
    > >> Description:
    > >> Windows cannot obtain the domain controller name for your computer
    > >> network. (The specified domain either does not exist or could not be
    > >> contacted. ). Group Policy processing aborted.
    > >> For more information, see Help and Support Center
    > >> athttp://go.microsoft.com/fwlink/events.asp.
    >
    > >> -- AND --
    >
    > >> Event Type: Error
    > >> Event Source: UserInit
    > >> Event Category: None
    > >> Event ID: 1000
    > >> Date: 1/5/2008
    > >> Time: 2:06:29 PM
    > >> User: N/A
    > >> Computer: VWORKINGBOX
    > >> Description:
    > >> Could not execute the following script Logon.vbs. The system cannot
    > >> find the file specified.
    > >> .
    > >> For more information, see Help and Support Center
    > >> athttp://go.microsoft.com/fwlink/events.asp.
    >
    > >> -- AND --
    >
    > >> Event Type: Error
    > >> Event Source: Userenv
    > >> Event Category: None
    > >> Event ID: 1053
    > >> Date: 1/5/2008
    > >> Time: 2:06:44 PM
    > >> User: NT AUTHORITY\SYSTEM
    > >> Computer: VWORKINGBOX
    > >> Description:
    > >> Windows cannot determine the user or computer name. (The specified
    > >> domain either does not exist or could not be contacted. ). Group
    > >> Policy processing aborted.
    > >> For more information, see Help and Support Center
    > >> athttp://go.microsoft.com/fwlink/events.asp.
    >
    > >> I also get this from my Virtual Server 2005 running on the DC
    > >> ==================================================
    > >> Event Type: Warning
    > >> Event Source: Virtual Server
    > >> Event Category: Virtual Server
    > >> Event ID: 1136
    > >> Date: 1/5/2008
    > >> Time: 1:46:57 PM
    > >> User: NT AUTHORITY\NETWORK SERVICE
    > >> Computer: MATRIX
    > >> Description:
    > >> An error has occured during the creation of Service Connection points
    > >> for Virtual Server in Active Directory. Either a domain controller is
    > >> not available to complete the operation or there is a security
    > >> problem
    > >> accessing the domain. This operation will be retried the next time
    > >> the
    > >> service starts. Error 0x80070005 - Access is denied.
    > >> For more information, see Help and Support Center
    > >> athttp://go.microsoft.com/fwlink/events.asp.
    >
    > > So I may have found out part of my problem. I found a reference in DNS
    > > to my old domain controller that was retired. After I removed that it
    > > seems to have corrected the issues with the clients. Time will tell.
    > > It is odd though because it was working fine earlier with that
    > > reference in there.
    >
    > > I am still getting the issue when Virtual Server 2005 starts but they
    > > may be something to ask another group.
    >
    > > Thanks- Hide quoted text -
    >
    > - Show quoted text -

    I created a new DC and moved all the roles to it and then shut the old
    one down. There was more to it than that but it has been a little
    while so the memory is fuzzy. I did follow articles I found on the
    Microsoft website.

    Thanks
    Karl
    Reply With Quote Reply With Quote
  6. 07-01-2008 #6
    karlman Guest

    Re: Domain cannot be found

    On Jan 6, 7:37 am, "Kevin D. Goodknecht Sr. [MVP]"
    <ad...@nospam.WFTX.US> wrote:
    > Read inline please.
    >
    > Innews:d8fc4d1e-8315-49f1-8371-b411dabfc8c6@i7g2000prf.googlegroups.com,
    > karlman <karlma...@gmail.com> typed:
    >
    >
    >
    >
    >
    > > I am getting several client errors related to the domain not being
    > > found (listed below). I am running a single domain controller
    > > (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    > > domain appears to be working okay becuase DNS, shares, exchange, SQL
    > > are all accessible. Originally the logon script was working fine but
    > > then I noticed this error cropping up. Not sure what I may have
    > > changed.
    >
    > > Any ideas on what to check?
    >
    > > Thanks
    > > Karl
    >
    > > From XP Pro clients:
    > > =====================================
    > > Event Type: Error
    > > Event Source: Userenv
    > > Event Category: None
    > > Event ID: 1054
    > > Date: 1/5/2008
    > > Time: 9:46:34 AM
    > > User: NT AUTHORITY\SYSTEM
    > > Computer: COMP-A
    > > Description:
    > > Windows cannot obtain the domain controller name for your computer
    > > network. (The specified domain either does not exist or could not be
    > > contacted. ). Group Policy processing aborted.
    >
    > > For more information, see Help and Support Center at
    > >http://go.microsoft.com/fwlink/events.asp.
    >
    > > -- AND --
    >
    > > Event Type: Error
    > > Event Source: UserInit
    > > Event Category: None
    > > Event ID: 1000
    > > Date: 1/5/2008
    > > Time: 2:06:29 PM
    > > User: N/A
    > > Computer: VWORKINGBOX
    > > Description:
    > > Could not execute the following script Logon.vbs. The system cannot
    > > find the file specified.
    > > .
    >
    > > For more information, see Help and Support Center at
    > >http://go.microsoft.com/fwlink/events.asp.
    >
    > > -- AND --
    >
    > > Event Type: Error
    > > Event Source: Userenv
    > > Event Category: None
    > > Event ID: 1053
    > > Date: 1/5/2008
    > > Time: 2:06:44 PM
    > > User: NT AUTHORITY\SYSTEM
    > > Computer: VWORKINGBOX
    > > Description:
    > > Windows cannot determine the user or computer name. (The specified
    > > domain either does not exist or could not be contacted. ). Group
    > > Policy processing aborted.
    >
    > > For more information, see Help and Support Center at
    > >http://go.microsoft.com/fwlink/events.asp.
    >
    > > I also get this from my Virtual Server 2005 running on the DC
    > > ==================================================
    > > Event Type: Warning
    > > Event Source: Virtual Server
    > > Event Category: Virtual Server
    > > Event ID: 1136
    > > Date: 1/5/2008
    > > Time: 1:46:57 PM
    > > User: NT AUTHORITY\NETWORK SERVICE
    > > Computer: MATRIX
    > > Description:
    > > An error has occured during the creation of Service Connection points
    > > for Virtual Server in Active Directory. Either a domain controller is
    > > not available to complete the operation or there is a security problem
    > > accessing the domain. This operation will be retried the next time the
    > > service starts. Error 0x80070005 - Access is denied.
    >
    > Make sure all DNS Clients use only the internal AD DNS in TCP/IP properties,
    > and that the (same as parent folder) A record in the AD Domain zone has not
    > been modified from using only DCs for their IP addresses.
    >
    > Make sure the DFS Service on the DCs is running and set to Auto start.
    >
    > Also, the TCP/IP NetBIOS helper serive is required for accessing DFS shares.
    >
    > Open the DFS shares by using \\ADDomain\SYSVOL or \\ADDomain\NETLOGON right
    > click in the window, choose properties, then select the Dfs tab of the
    > properties sheet, select and check the Status of all DCs on the tab.
    >
    > --
    > Best regards,
    > Kevin D. Goodknecht Sr. [MVP]
    > Hope This Helps
    >
    > ===================================
    > When responding to posts, please "Reply to Group"
    > via your newsreader so that others may learn and
    > benefit from your issue, to respond directly to
    > me remove the nospam. from my email address.
    > ===================================http://www.lonestaramerica.com/http://support.wftx.us/http://message.wftx.us/
    > ===================================
    > Use Outlook Express?... Get OE_Quotefix:
    > It will strip signature out and morehttp://home.in.tum.de/~jain/software/oe-quotefix/
    > ===================================
    > Keep a back up of your OE settings and folders
    > with OEBackup:http://www.oehelp.com/OEBackup/Default.aspx
    > ===================================- Hide quoted text -
    >
    > - Show quoted text -

    DFS and TCP/IP Helper services are running and set to auto. When I
    followed you directions I get an error saying "The server <domain
    name> could not be found on the network." when I click properties of \
    \ADDomain\sysvol\. However the properties page does come up after
    pressing okay. On the DFS page it has a single listing which is my DC.
    When I press 'Check Status' it says that it is Okay.

    However, I do have a secondary DNS on my clients which is a public DNS
    server. I originally did this so that when the DC was down for any
    reason the clients could still reach the Internet. Should I remove
    that?

    Thank you
    Karl


    Reply With Quote Reply With Quote
  7. 07-01-2008 #7
    Meinolf Weber Guest

    Re: Domain cannot be found

    Hello karlman,

    Normally you remove a dc with running dcpromo again and following the wizard.
    If this fails you can try it with dcpromo /forceremoval. If this also does
    not work the last step is, to shut it down and use adsiedit to remove all
    existing entries from Active directory. Then you should NEVER connect it
    again to the network.

    How to remove data in Active Directory after an unsuccessful domain controller
    demotion
    http://support.microsoft.com/kb/216498

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

    > On Jan 5, 4:08 pm, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
    >
    >> Hello karlman,
    >>
    >> You wrote about a removed DC, how did you remove it?
    >>
    >> Best regards
    >>
    >> Meinolf Weber
    >> Disclaimer: This posting is provided "AS IS" with no warranties, and
    >> confers
    >> no rights.
    >> ** Please do NOT email, only reply to Newsgroups
    >> ** HELP us help YOU!!!http://www.dts-l.org/goodpost.htm
    >>> On Jan 5, 2:23 pm, karlman <karlma...@gmail.com> wrote:
    >>>
    >>>> I am getting several client errors related to the domain not being
    >>>> found (listed below). I am running a single domain controller
    >>>> (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    >>>> domain appears to be working okay becuase DNS, shares, exchange,
    >>>> SQL are all accessible. Originally the logon script was working
    >>>> fine but then I noticed this error cropping up. Not sure what I may
    >>>> have changed.
    >>>>
    >>>> Any ideas on what to check?
    >>>>
    >>>> Thanks
    >>>> Karl
    >>>> From XP Pro clients:
    >>>> =====================================
    >>>> Event Type: Error
    >>>> Event Source: Userenv
    >>>> Event Category: None
    >>>> Event ID: 1054
    >>>> Date: 1/5/2008
    >>>> Time: 9:46:34 AM
    >>>> User: NT AUTHORITY\SYSTEM
    >>>> Computer: COMP-A
    >>>> Description:
    >>>> Windows cannot obtain the domain controller name for your computer
    >>>> network. (The specified domain either does not exist or could not
    >>>> be
    >>>> contacted. ). Group Policy processing aborted.
    >>>> For more information, see Help and Support Center
    >>>> athttp://go.microsoft.com/fwlink/events.asp.
    >>>> -- AND --
    >>>>
    >>>> Event Type: Error
    >>>> Event Source: UserInit
    >>>> Event Category: None
    >>>> Event ID: 1000
    >>>> Date: 1/5/2008
    >>>> Time: 2:06:29 PM
    >>>> User: N/A
    >>>> Computer: VWORKINGBOX
    >>>> Description:
    >>>> Could not execute the following script Logon.vbs. The system cannot
    >>>> find the file specified.
    >>>> .
    >>>> For more information, see Help and Support Center
    >>>> athttp://go.microsoft.com/fwlink/events.asp.
    >>>> -- AND --
    >>>>
    >>>> Event Type: Error
    >>>> Event Source: Userenv
    >>>> Event Category: None
    >>>> Event ID: 1053
    >>>> Date: 1/5/2008
    >>>> Time: 2:06:44 PM
    >>>> User: NT AUTHORITY\SYSTEM
    >>>> Computer: VWORKINGBOX
    >>>> Description:
    >>>> Windows cannot determine the user or computer name. (The specified
    >>>> domain either does not exist or could not be contacted. ). Group
    >>>> Policy processing aborted.
    >>>> For more information, see Help and Support Center
    >>>> athttp://go.microsoft.com/fwlink/events.asp.
    >>>> I also get this from my Virtual Server 2005 running on the DC
    >>>> ==================================================
    >>>> Event Type: Warning
    >>>> Event Source: Virtual Server
    >>>> Event Category: Virtual Server
    >>>> Event ID: 1136
    >>>> Date: 1/5/2008
    >>>> Time: 1:46:57 PM
    >>>> User: NT AUTHORITY\NETWORK SERVICE
    >>>> Computer: MATRIX
    >>>> Description:
    >>>> An error has occured during the creation of Service Connection
    >>>> points
    >>>> for Virtual Server in Active Directory. Either a domain controller
    >>>> is
    >>>> not available to complete the operation or there is a security
    >>>> problem
    >>>> accessing the domain. This operation will be retried the next time
    >>>> the
    >>>> service starts. Error 0x80070005 - Access is denied.
    >>>> For more information, see Help and Support Center
    >>>> athttp://go.microsoft.com/fwlink/events.asp.
    >>> So I may have found out part of my problem. I found a reference in
    >>> DNS to my old domain controller that was retired. After I removed
    >>> that it seems to have corrected the issues with the clients. Time
    >>> will tell. It is odd though because it was working fine earlier with
    >>> that reference in there.
    >>>
    >>> I am still getting the issue when Virtual Server 2005 starts but
    >>> they may be something to ask another group.
    >>>
    >>> Thanks- Hide quoted text -
    >>>
    >> - Show quoted text -
    >>
    > I created a new DC and moved all the roles to it and then shut the old
    > one down. There was more to it than that but it has been a little
    > while so the memory is fuzzy. I did follow articles I found on the
    > Microsoft website.
    >
    > Thanks
    > Karl


    Reply With Quote Reply With Quote
  8. 07-01-2008 #8
    Meinolf Weber Guest

    Re: Domain cannot be found

    Hello karlman,

    Remove them, use the internal DNS server only for the clients and configure
    a forwarder on the DNS server properties in the DNS management console to
    your ISP's DNS server.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

    > On Jan 6, 7:37 am, "Kevin D. Goodknecht Sr. [MVP]"
    > <ad...@nospam.WFTX.US> wrote:
    >
    >> Read inline please.
    >>
    >> Innews:d8fc4d1e-8315-49f1-8371-b411dabfc8c6@i7g2000prf.googlegroups.c
    >> om, karlman <karlma...@gmail.com> typed:
    >>
    >>> I am getting several client errors related to the domain not being
    >>> found (listed below). I am running a single domain controller
    >>> (Win2003) and it is also running Exchange 2003 and SQL 2005. The
    >>> domain appears to be working okay becuase DNS, shares, exchange, SQL
    >>> are all accessible. Originally the logon script was working fine but
    >>> then I noticed this error cropping up. Not sure what I may have
    >>> changed.
    >>>
    >>> Any ideas on what to check?
    >>>
    >>> Thanks
    >>> Karl
    >>> From XP Pro clients:
    >>> =====================================
    >>> Event Type: Error
    >>> Event Source: Userenv
    >>> Event Category: None
    >>> Event ID: 1054
    >>> Date: 1/5/2008
    >>> Time: 9:46:34 AM
    >>> User: NT AUTHORITY\SYSTEM
    >>> Computer: COMP-A
    >>> Description:
    >>> Windows cannot obtain the domain controller name for your computer
    >>> network. (The specified domain either does not exist or could not be
    >>> contacted. ). Group Policy processing aborted.
    >>> For more information, see Help and Support Center at
    >>> http://go.microsoft.com/fwlink/events.asp.
    >>>
    >>> -- AND --
    >>>
    >>> Event Type: Error
    >>> Event Source: UserInit
    >>> Event Category: None
    >>> Event ID: 1000
    >>> Date: 1/5/2008
    >>> Time: 2:06:29 PM
    >>> User: N/A
    >>> Computer: VWORKINGBOX
    >>> Description:
    >>> Could not execute the following script Logon.vbs. The system cannot
    >>> find the file specified.
    >>> .
    >>> For more information, see Help and Support Center at
    >>> http://go.microsoft.com/fwlink/events.asp.
    >>>
    >>> -- AND --
    >>>
    >>> Event Type: Error
    >>> Event Source: Userenv
    >>> Event Category: None
    >>> Event ID: 1053
    >>> Date: 1/5/2008
    >>> Time: 2:06:44 PM
    >>> User: NT AUTHORITY\SYSTEM
    >>> Computer: VWORKINGBOX
    >>> Description:
    >>> Windows cannot determine the user or computer name. (The specified
    >>> domain either does not exist or could not be contacted. ). Group
    >>> Policy processing aborted.
    >>> For more information, see Help and Support Center at
    >>> http://go.microsoft.com/fwlink/events.asp.
    >>>
    >>> I also get this from my Virtual Server 2005 running on the DC
    >>> ==================================================
    >>> Event Type: Warning
    >>> Event Source: Virtual Server
    >>> Event Category: Virtual Server
    >>> Event ID: 1136
    >>> Date: 1/5/2008
    >>> Time: 1:46:57 PM
    >>> User: NT AUTHORITY\NETWORK SERVICE
    >>> Computer: MATRIX
    >>> Description:
    >>> An error has occured during the creation of Service Connection
    >>> points
    >>> for Virtual Server in Active Directory. Either a domain controller
    >>> is
    >>> not available to complete the operation or there is a security
    >>> problem
    >>> accessing the domain. This operation will be retried the next time
    >>> the
    >>> service starts. Error 0x80070005 - Access is denied.
    >> Make sure all DNS Clients use only the internal AD DNS in TCP/IP
    >> properties, and that the (same as parent folder) A record in the AD
    >> Domain zone has not been modified from using only DCs for their IP
    >> addresses.
    >>
    >> Make sure the DFS Service on the DCs is running and set to Auto
    >> start.
    >>
    >> Also, the TCP/IP NetBIOS helper serive is required for accessing DFS
    >> shares.
    >>
    >> Open the DFS shares by using \\ADDomain\SYSVOL or \\ADDomain\NETLOGON
    >> right click in the window, choose properties, then select the Dfs tab
    >> of the properties sheet, select and check the Status of all DCs on
    >> the tab.
    >>
    >> --
    >> Best regards,
    >> Kevin D. Goodknecht Sr. [MVP]
    >> Hope This Helps
    >> ===================================
    >>
    >> When responding to posts, please "Reply to Group"
    >>
    >> via your newsreader so that others may learn and
    >>
    >> benefit from your issue, to respond directly to
    >>
    >> me remove the nospam. from my email address.
    >>
    >> ===================================http://www.lonestaramerica.com/htt
    >> p://support.wftx.us/http://message.wftx.us/
    >>
    >> ===================================
    >>
    >> Use Outlook Express?... Get OE_Quotefix:
    >>
    >> It will strip signature out and
    >> morehttp://home.in.tum.de/~jain/software/oe-quotefix/
    >>
    >> ===================================
    >>
    >> Keep a back up of your OE settings and folders
    >>
    >> with OEBackup:http://www.oehelp.com/OEBackup/Default.aspx
    >>
    >> ===================================- Hide quoted text -
    >>
    >> - Show quoted text -
    >>
    > DFS and TCP/IP Helper services are running and set to auto. When I
    > followed you directions I get an error saying "The server <domain
    >
    name>> could not be found on the network." when I click properties of \
    name>>
    > \ADDomain\sysvol\. However the properties page does come up after
    > pressing okay. On the DFS page it has a single listing which is my DC.
    > When I press 'Check Status' it says that it is Okay.
    >
    > However, I do have a secondary DNS on my clients which is a public DNS
    > server. I originally did this so that when the DC was down for any
    > reason the clients could still reach the Internet. Should I remove
    > that?
    >
    > Thank you
    > Karl


    Reply With Quote Reply With Quote
« Disconnected Network Drive - Zombie Drive? | Scheduled Task Exit Code »

Similar Threads

  1. Domino 7 - No route found to domain gmail.com from server
    By Maudy in forum Technology & Internet
    Replies: 7
    Last Post: 24-05-2010, 04:05 PM
  2. network path was not found when trying to join domain
    By RW in forum Windows Server Help
    Replies: 6
    Last Post: 29-08-2009, 05:16 AM
  3. "The Network Path Was Not Found" (joining domain)
    By hozzie in forum Windows Server Help
    Replies: 6
    Last Post: 06-07-2009, 10:39 PM
  4. Server 2003 sp3 error - Domain controller cannot be found ?
    By Mmaxx in forum Active Directory
    Replies: 20
    Last Post: 12-07-2008, 09:23 AM
  5. Domain controller not found
    By Jim in forum Windows Server Help
    Replies: 18
    Last Post: 01-11-2007, 09:51 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules

Page generated in 1,714,306,914.16577 seconds with 18 queries