Jump to content

sch2000

Members
  • Posts

    1
  • Joined

  • Last visited

About sch2000

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Ireland
  1. Hi, last week the school found that windows XP SP3 clients connected to a windows 2003 R2 domain controller had issues connecting to the server when using Antivirus 4.x. The issue was that they could not connect to the domain controller using the FQDN based paths, associated with windows File replication service and Sysvol. Through trial and error, the issue appeared to be that ESET was causing authentication to fail when clients were connecting to the server using the FQDN based path, \\ourdomain.local\sysvol They could connect using the path \\servername\sysvol This blocked the group policy settings from being applied, unable to connect to gpt.ini and the associated policy scripts. When the antivirus was disabled, the group policy worked. When the clients were upgraded to Eset endpoint antivirus 5, the group policy worked. The upgrade of the AV had to be done manually as there were IPC errors when trying to upgrade using the remote console. It was not a DNS resolution error, pinging the FQDN worked.
×
×
  • Create New...