Cannot access \\domain\sysvol

[willsmyth]

I have been triyng to get this problem resolved but have drawn a blank so far!

Infrasturcture
Windows 2000 server SP4 – dc - TO BE RETIRED ONCE PROBLEM RESOLVED
Servers - Windows 2003 64Bit R2 x 2. Both are dc’s.

Site 1 -
Windows 2000 Server SP4, Server Name – Larsen-belfast, IP 192.168.1.2
Windows 2003 Server 64bit R2 SP2, Server Name – Belfastdc IP 192.168.1.150
Will be adding a new Server2003 DC after problem resolved.

Site 2 – via 128kb leased line
Windows 2003 Server 64 bit R2 SP2, Server Name – Dublindc IP 192.168.2.150

Intersite replication is working fine
DNS is not logging any errors
FRS is not logging any errors
All servers correctly respond to ping by both IP and name
NSLookup returns correct belfastdc.larsen-building.co.uk
As the errors are being generated on all servers and the replication appears
to be working correctly we have focused
our efforts on the servers in Site 1

Events being logged on the Servers and the workstations.

Id: 1030
Windows cannot query for the list of Group Policy objects. Check the event
log for possible messages previously logged by the policy engine that
describes the reason for this.

Id: 1058
Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=larsen-building,DC=co,DC=uk..
The file must be present at the location
<\\larsen-building.co.uk\sysvol\larsen-building.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
(Configuration information could not be read from the domain controller,
either because the
machine is unavailable, or access has been denied. ). Group Policy
processing aborted.


On Windows Server 2003
If you type
"\\larsen-building.co.uk\sysvol\larsen-building.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\"
into an explorer address window, you get a "Windows cannot find ..." error.
However, if you type the name of the server,
\\belfastdc\sysvol\larsen-building.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\
, you are taken to the correct folder where the gpt.ini resides (as you would
expect).
\\larsen-building.co.uk – shows the contents ie shares etc but if I select
any entry in this window I get the not accessible error message
\\larsen-building.co.uk\sysvol - “is not accessible” error
\\larsen-building.co.uk\sysvol\larsen-building.co.uk - “is not accessible”
error
\\larsen-building.co.uk\sysvol\larsen-building.co.uk\policies - “is not
accessible” error
Etc etc
ie access to entire directory structure is barred


On Windows 2000 Server – NOT REALLY CONCERNED WITH THIS AS IT IS TO BE
RETIRED. HERE AS PART OF INFRASTRUCTURE IN CASE IT IS RELEVANT TO PROBLEM

\\larsen-building.co.uk\sysvol\larsen-building.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\
into an explorer address window, you are taken to the correct
\\larsen-belfast\sysvol\larsen-building.co.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\
into an explorer address window, you are taken to the correct
\\larsen-building.co.uk – not accessible. The network name cannot be found
\\larsen-building.co.uk\sysvol and subdirectories below work fine.

We have followed each of the following MS KB articles, as well as other
related posts.
839499
290647
887303
271213
259398
285923
258296
258213

All without resolution. Thanks for any help

[Jorge Silva]

Hi
On the workstations that are getting the error, do a ping to
larsen-building.co.uk. What DC responds? Check what DC is repsonding then
try to access to that DC \\dc\sysvol\etc....
You probably will get the same error, and the problem resides there, I
already see to many different ways to solve this, sounds that in each case
is a unic case... eheheh.
Some of them:
-Reboot that DC, make sure that the DC has a valid online alternate DNS
server before doing restart.
-Force full replication among all existing DCs, then try again...
-Reset the computer account and re-add the workstation to the domain...
also check:
http://www.eventid.net/display.asp?e...serenv&phase=1


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

[willsmyth]

Hi Jorge

Site 1

From
Belfastdc 192.168.1.150
Ping larsen-building.co.uk returns192.168.1.150

From
Larsen-belfast 192.168.1.2
Ping larsen-building.co.uk returns 192.168.1.2

From workstations
Ping larsen-building.co.uk returns192.168.1.150

Site 2
From
Dublindc 192.168.2.150
Ping larsen-building.co.uk returns192.168.2.150

From workstations
Ping larsen-building.co.uk returns192.168.2.150

From belfastdc & site1 workstations
\\larsen-building.co.uk OK
\\larsen-building.co.uk\sysvol is not accessible
\\belfastdc\ OK
\\belfastdc\sysvol OK

NSLookop
Default Belfastdc.larsen-building.co.uk
Address:192.168.1.150
>Larsen-building.co.uk
Server: belfastdc.larsen-building.co.uk
Address:192.168.1.150

Name: Larsen-building.co.uk
Addresses: 192.168.1.2, 192.168.1.150, 192.168.2.150

Replication is working correctly with no errors and sysvol contents being
replicated correctly


"Jorge Silva" wrote:

> Hi
> On the workstations that are getting the error, do a ping to
> larsen-building.co.uk. What DC responds? Check what DC is repsonding then
> try to access to that DC \\dc\sysvol\etc....
> You probably will get the same error, and the problem resides there, I
> already see to many different ways to solve this, sounds that in each case
> is a unic case... eheheh.
> Some of them:
> -Reboot that DC, make sure that the DC has a valid online alternate DNS
> server before doing restart.
> -Force full replication among all existing DCs, then try again...
> -Reset the computer account and re-add the workstation to the domain...
> also check:
> http://www.eventid.net/display.asp?e...serenv&phase=1
>
>
> --
> I hope that the information above helps you.
> Have a Nice day.
>
> Jorge Silva
> MCSE, MVP Directory Services
>
>

[Jorge Silva]

as I told before, read the alternatives in the link, also have a look at
eventlog to search for errors or additional warnings.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

[willsmyth]

We have spent the last 2 days working through the suggested link.
No resolution.
There is one item that we are having problems with
KB:839499 require a restart of the workstation & server services as opposed
to a server reboot. When I try to restart the workstation service it will not
stop and as a result I have reboot the server. The suggestion is that a
server restart my reset the keys, this not the case as the changed key
remains after the reboot.

One of the posts suggest taking a workstation of the domain and reseting the
account. We carried this out and now when the workstation is joined to the
domain it cannot see the windows 2000 dc at all.

As you suggest that these problems are not unique I welcome any other
suggestions.

Regards

Willy


"Jorge Silva" wrote:

> as I told before, read the alternatives in the link, also have a look at
> eventlog to search for errors or additional warnings.
>
> --
> I hope that the information above helps you.
> Have a Nice day.
>
> Jorge Silva
> MCSE, MVP Directory Services
>

[Jorge Silva]

-Running dcdiag and netdiag on the servers may help to identify if the DCs
have any problem.
-For workstation part, henerally re-adding the worstation to the domain
clears the error.
-Also need to have a look at FW copnfigurations, DNS,, etc..

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services