SysVol Referrals

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm having problems with some of my SysVol Referrals, I have a mixed
2000/2003 Active Directory structure. We are in the process of upgrading all
servers to 2003. I ran into a few authentication problems after I upgraded
one of my Corp servers from 2000 to 2003 (rebuild of server not an upgrade).
During troubleshooting of the problem I noticed that on some servers I was
unable to open \\company.com\sysvol. When I attempted to access it on the
server I would receive an error that a duplicate computer name existed on the
network. If I tried from a client server I would receive "Access Denied".

I could open \\company.com and it would list the SysVol and Netlogon share
but I couldn't access them. I checked the DFS Properties on SysVol and
noticed that it was pointing to a server that didn't exist. I looked for my
local DC and it wasn't listed so I pointed to my Corp server. This fixed
both my 1030 and 1058 errors and after I did that I was able to open
\\company.com\sysvol without a problem.

My problem is that I have been adding new DC's to AD and some of them are
listed on the DFS Properties and others are not. We had a new office start
up last month and that server should be listed but instead it shows my FSMO
server in my Corp office. It works but I would think it should have the
local server active so clients would not have to go across my WAN link to get
GPO and Login scripts.

When I ping company.com it returns the IP Address of my local DC, I would
think that if I wanted to connect to \\company.com\sysvol this would cause
problems since I had errors when the DFS Properties had an inactive server
would return errors.

I need to know how to replicate the information out so that I can fix my DFS
Referrals to point to the local DC's.

I have not deployed SP1 on my 2003 boxes and really didn't want to untiil I
was able to deploy it network wide. I did see some KB's with notes on 2003
SP1 if I'm going to be forced to install SP1 then I'll need to redesign my
2003 deployment plan.

Thanks for your help with regards to this strange AD problem.
.

Relevant Pages

  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)
  • Re: GPOs cannot be saved because files being used by another proce
    ... Excessive Replication of FRS Data in Sysvol and DFS ... Check if FRS is currently running on the target server. ... Checking NtFrs related Registry Keys for possible problems...passed ...
    (microsoft.public.windows.server.active_directory)
  • Re: HELP - cant access domain!
    ... The SYSVOL folder had stopped sharing for some reason. ... also I think you may have a dns problem... ... Testing server: Brampton\SSTERM01 ... 'HOSTING': Cannot find DC to get DC list from. ...
    (microsoft.public.windows.server.active_directory)
  • Re: HELP - cant access domain!
    ... The SYSVOL folder had stopped sharing for some reason. ... also I think you may have a dns problem... ... Testing server: Brampton\SSTERM01 ... 'HOSTING': Cannot find DC to get DC list from. ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to recover from DC without GC?
    ... all the files in the SYSVOL folder though? ... A Global Catalog Server could not be located - All GC's are ... You've got DNS problems. ...
    (microsoft.public.windows.server.active_directory)