Thanks for the reply. It is a bit weird. The client cannot even see \\DS1 for
shares of any sort and if the client is rebooted all goes to normal.
Additionally all other clients run normally all the time. I don't think it is
the server at all. But cannot see what might cause the client to stop seeing the
shares on only one server. Its access to other servers seems OK but I do usually
need to synchronize offline folders to get things going.
On Mon, 13 Oct 2008 08:43:02 -0700, John Angel [MSFT]
<> wrote:
>Hi David,
>
>In DS1, once it reboots have you checked that the DFS Namespace service is
>running?
>
>Regards,
>
>John
>
>"DaveMills" wrote:
>
>> I am not sure if this is a DFS issue or not. It may be though.
>>
>> My client PC is XP SP3 plus all WSUS delivered updates.
>> I have a W2003 R2 SP2 server "DS1" which has a few shares and is a DFS Root
>> server, but not a DC.
>> The client uses "\\domain\root\network admin" to access a share via the link to
>> "\\DS1\network admin$"
>>
>> All works fine until I reboot DS1. After that the client can no longer access
>> "\\domain\root\network admin". If I open "\\ds1" there are no shares. If I try
>> to open "\\ds1\network admin" it fails with network resource unavailable. I can
>> use task managed to kill "explorer" and restart it and still no access is
>> possible. I synchronize offline files, still no access.
>>
>> If I reboot the client then all is wonderful again.
>>
>> Any ideas?
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that don't.
>>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|