Guest zack Posted August 3, 2007 Posted August 3, 2007 Hi, We are running terminal services on a windows 2003 member server, with windows server 2003 r2 on our domain controller. I removed Client for microsoft networks, in an attempt to sort another problem out. On reboot I re-installed. On the DC I am getting this error "The dns server has encountered a critical error from the active directory: ID 4015 . and 4004 : The dns server was unable to complete directory service enumeration of sone sunnyfield.local. Our local users are logging on fine. On the terminal server, Group policy is not being applied and this event is being logged. 1053: Windows cannot determine the user or computer name. Any ideas on what could be the problem? Thanks Zakaria //..
Guest Helge Klein Posted August 3, 2007 Posted August 3, 2007 Re: Group policy errors on Terminal Services You do need the Client for Microsoft Networks both on Terminalservers and Domain Controllers. Where did you remove it? Did you reinstall it on the same system after removal? Did you reboot after the reinstallation? Have the errors appeared after a reboot after the reinstallation? Helge ================== Please visit my blog: http://it-from-inside.blogspot.com ================== On 3 Aug., 14:55, zack <zacde...@gmail.com> wrote: > Hi, > > We are running terminal services on a windows 2003 member server, with > windows server 2003 r2 on our domain controller. I removed Client for > microsoft networks, in an attempt to sort another problem out. On > reboot I re-installed. On the DC I am getting this error "The dns > server has encountered a critical error from the active directory: ID > 4015 . and 4004 : The dns server was unable to complete directory > service enumeration of sone sunnyfield.local. Our local users are > logging on fine. On the terminal server, Group policy is not being > applied and this event is being logged. 1053: Windows cannot determine > the user or computer name. > Any ideas on what could be the problem? > > Thanks > Zakaria //..
Guest zack Posted August 3, 2007 Posted August 3, 2007 Re: Group policy errors on Terminal Services On Aug 3, 3:04 pm, Helge Klein <Helge.Kl...@googlemail.com> wrote: > You do need the Client for Microsoft Networks both on Terminalservers > and Domain Controllers. Where did you remove it? Did you reinstall it > on the same system after removal? Did you reboot after the > reinstallation? Have the errors appeared after a reboot after the > reinstallation? > > Helge > > ================== > Please visit my blog:http://it-from-inside.blogspot.com > ================== > > On 3 Aug., 14:55, zack <zacde...@gmail.com> wrote: > > > > > Hi, > > > We are running terminal services on a windows 2003 memberserver, with > > windowsserver2003 r2 on our domain controller. I removed Client for > > microsoft networks, in an attempt to sort another problem out. On > > reboot I re-installed. On the DC I am getting this error "Thedns > >serverhas encountered a critical error from the activedirectory: ID > > 4015 . and4004: Thednsserverwasunabletocompletedirectory > >serviceenumerationof sone sunnyfield.local. Our local users are > > logging on fine. On the terminalserver, Group policy is not being > > applied and this event is being logged. 1053: Windows cannot determine > > the user or computer name. > > Any ideas on what could be the problem? > > > Thanks > > Zakaria //..- Hide quoted text - > > - Show quoted text - I have re-installed on the DC. And it was only removed on the DC. I just noticed that the DNS service was not started , I manually started it and its up now. On the terminal server I am still getting GP errors though. Event ID 1030 Windows Cannot query for the list of Group policy objects. Thanks
Guest Helge Klein Posted August 3, 2007 Posted August 3, 2007 Re: Group policy errors on Terminal Services The errors on the TS are probably due to that fact that it still thinks it cannot contact the DC. A reboot of the TS should help. Helge ================== Please visit my blog: http://it-from-inside.blogspot.com ================== On 3 Aug., 15:16, zack <zacde...@gmail.com> wrote: > On Aug 3, 3:04 pm, Helge Klein <Helge.Kl...@googlemail.com> wrote: > > > > > You do need the Client for Microsoft Networks both on Terminalservers > > and Domain Controllers. Where did you remove it? Did you reinstall it > > on the same system after removal? Did you reboot after the > > reinstallation? Have the errors appeared after a reboot after the > > reinstallation? > > > Helge > > > ================== > > Please visit my blog:http://it-from-inside.blogspot.com > > ================== > > > On 3 Aug., 14:55, zack <zacde...@gmail.com> wrote: > > > > Hi, > > > > We are running terminal services on a windows 2003 memberserver, with > > > windowsserver2003 r2 on our domain controller. I removed Client for > > > microsoft networks, in an attempt to sort another problem out. On > > > reboot I re-installed. On the DC I am getting this error "Thedns > > >serverhas encountered a critical error from the activedirectory: ID > > > 4015 . and4004: Thednsserverwasunabletocompletedirectory > > >serviceenumerationof sone sunnyfield.local. Our local users are > > > logging on fine. On the terminalserver, Group policy is not being > > > applied and this event is being logged. 1053: Windows cannot determine > > > the user or computer name. > > > Any ideas on what could be the problem? > > > > Thanks > > > Zakaria //..- Hide quoted text - > > > - Show quoted text - > > I have re-installed on the DC. And it was only removed on the DC. I > just noticed that the DNS service was not started , I manually started > it and its up now. On the terminal server I am still getting GP errors > though. Event ID 1030 Windows Cannot query for the list of Group > policy objects. > > Thanks
Recommended Posts