DFS and Windows 2000 Pro clients

  • Thread starter Thread starter D-Beau
  • Start date Start date
D

D-Beau

Guest
For some reason none of our Windows 2000 Pro SP4 clients can see our DFS
shares.

When trying to access them I get an error either that they can't be found or
that I don't have access.


Is there anything I need to install or enable on these clients?
 
Re: DFS and Windows 2000 Pro clients

Hello D-Beau,

How did you setup the share permissions and the folder permissions? Please
post the complete error message you get. How did you try to access the shares?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> For some reason none of our Windows 2000 Pro SP4 clients can see our
> DFS shares.
>
> When trying to access them I get an error either that they can't be
> found or that I don't have access.
>
> Is there anything I need to install or enable on these clients?
>
 
Re: DFS and Windows 2000 Pro clients


"D-Beau" <DBeau@discussions.microsoft.com> wrote in message
news:6A9EDDEA-8302-49D8-ADCA-9AF6A65E32D2@microsoft.com...
> For some reason none of our Windows 2000 Pro SP4 clients can see our DFS
> shares.

Clarify carefully what "see" means...

> When trying to access them I get an error either that they can't be found
> or
> that I don't have access.

See frequently means that a server doesn't show up in the Browser (Network
Neighborhood) which is possibly merely a Browsing issue, including WINS
Server or Client problems if you have more than one subnet.

"Can't be found" usually means a NAME RESOLUTION problem, either
NetBIOS or DNS -- usually DNS with DFS but both are possible.

No access is usually an authentication problem although it could be
a permission issue.

Authentication in AD domains is almost always a DNS problem,
either client settings, DCs settings, or issues with the DNS server
itself.

> Is there anything I need to install or enable on these clients?

No.

But you do need to clarify which problem, or problems you actually
have.

Isolate the symptoms.

Can you ping? By name and IP or just by IP? If only by IP then
you have (at least) a name resolution problem. If NOT by IP
then you have a basic IP/routing/network issue and need to fix
this before worrying about name resolution and other things....

Are you authenticated?

Can you explicitly "net use" or "net view" to see and use a share?

And explicitly authenticate as an admin or someone who clearly
has permission?

net view \\ServerOrDFSName

net use * \\ServerOrDFSName\Sharename

net use * \\ServerOrDFSName\Sharename * /user:DomainName\Administrator

(Administrator or some other privileged user on the share.)

Problems are easy to solve usually -- FINDING the problem is the hard part.
 
Re: DFS and Windows 2000 Pro clients

Hello Herb,

where do you live? See you the complete day/night here. :-)

Best regards from Germany

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> "D-Beau" <DBeau@discussions.microsoft.com> wrote in message
> news:6A9EDDEA-8302-49D8-ADCA-9AF6A65E32D2@microsoft.com...
>
>> For some reason none of our Windows 2000 Pro SP4 clients can see our
>> DFS shares.
>>
> Clarify carefully what "see" means...
>
>> When trying to access them I get an error either that they can't be
>> found
>> or
>> that I don't have access.
> See frequently means that a server doesn't show up in the Browser
> (Network Neighborhood) which is possibly merely a Browsing issue,
> including WINS Server or Client problems if you have more than one
> subnet.
>
> "Can't be found" usually means a NAME RESOLUTION problem, either
> NetBIOS or DNS -- usually DNS with DFS but both are possible.
>
> No access is usually an authentication problem although it could be a
> permission issue.
>
> Authentication in AD domains is almost always a DNS problem,
> either client settings, DCs settings, or issues with the DNS server
> itself.
>> Is there anything I need to install or enable on these clients?
>>
> No.
>
> But you do need to clarify which problem, or problems you actually
> have.
>
> Isolate the symptoms.
>
> Can you ping? By name and IP or just by IP? If only by IP then you
> have (at least) a name resolution problem. If NOT by IP then you have
> a basic IP/routing/network issue and need to fix this before worrying
> about name resolution and other things....
>
> Are you authenticated?
>
> Can you explicitly "net use" or "net view" to see and use a share?
>
> And explicitly authenticate as an admin or someone who clearly has
> permission?
>
> net view \\ServerOrDFSName
>
> net use * \\ServerOrDFSName\Sharename
>
> net use * \\ServerOrDFSName\Sharename *
> /user:DomainName\Administrator
>
> (Administrator or some other privileged user on the share.)
>
> Problems are easy to solve usually -- FINDING the problem is the hard
> part.
>
 
Re: DFS and Windows 2000 Pro clients


"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb669c8428ca89c401eb4e3b@msnews.microsoft.com...
> Hello Herb,
>
> where do you live? See you the complete day/night here. :-)

Austin, TX -- Central Time Zone US

> Best regards from Germany

Danke. Ich bin zwei jahre auf Mainz, aber ich spreche nicht noch gut
deutsch.


> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> "D-Beau" <DBeau@discussions.microsoft.com> wrote in message
>> news:6A9EDDEA-8302-49D8-ADCA-9AF6A65E32D2@microsoft.com...
>>
>>> For some reason none of our Windows 2000 Pro SP4 clients can see our
>>> DFS shares.
>>>
>> Clarify carefully what "see" means...
>>
>>> When trying to access them I get an error either that they can't be
>>> found
>>> or
>>> that I don't have access.
>> See frequently means that a server doesn't show up in the Browser
>> (Network Neighborhood) which is possibly merely a Browsing issue,
>> including WINS Server or Client problems if you have more than one
>> subnet.
>>
>> "Can't be found" usually means a NAME RESOLUTION problem, either
>> NetBIOS or DNS -- usually DNS with DFS but both are possible.
>>
>> No access is usually an authentication problem although it could be a
>> permission issue.
>>
>> Authentication in AD domains is almost always a DNS problem,
>> either client settings, DCs settings, or issues with the DNS server
>> itself.
>>> Is there anything I need to install or enable on these clients?
>>>
>> No.
>>
>> But you do need to clarify which problem, or problems you actually
>> have.
>>
>> Isolate the symptoms.
>>
>> Can you ping? By name and IP or just by IP? If only by IP then you
>> have (at least) a name resolution problem. If NOT by IP then you have
>> a basic IP/routing/network issue and need to fix this before worrying
>> about name resolution and other things....
>>
>> Are you authenticated?
>>
>> Can you explicitly "net use" or "net view" to see and use a share?
>>
>> And explicitly authenticate as an admin or someone who clearly has
>> permission?
>>
>> net view \\ServerOrDFSName
>>
>> net use * \\ServerOrDFSName\Sharename
>>
>> net use * \\ServerOrDFSName\Sharename *
>> /user:DomainName\Administrator
>>
>> (Administrator or some other privileged user on the share.)
>>
>> Problems are easy to solve usually -- FINDING the problem is the hard
>> part.
>>
>
>
 
Back
Top