Re: net use z: \\FQDN\share issue
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Wed, 23 Nov 2005 07:28:04 -0500
In news:5503BDD9-DEFF-46D7-B535-0A31EE19CA49@xxxxxxxxxxxxx,
agcastle2000 <agcastle2000@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which
I then commented about below:
> Just a follow-up.
>
> It's worth noting that in my example, fabricorp.costoso.com is the
> internal DNS domain and \\fabricorp.costoso.com\globalshare is the
> domain-based DFS root or host server.
>
> Going back to the issue.
>
> AD (DS) client was installed on NT machines and "few hours later" z:
> is lost. XP machines are experiencing the same. OTOH, the other map
> drive to \\server.fabricorp.costoso.com\apps on the same script is
> still intact.
>
> So I went to Command Prompt on NT:
>
> net use z: \\fabricorp.costoso.com\globalshare
> System 53 has occurred.
>
> but when I do
> net use z: \\server.fabricorp.costoso.com\globalshare
> The command completed successfully.
>
> This leads me to ask whether in domain-based DFS roots mapping a
> drive to the root using just the domain name like the one below (with
> the left-most host part stripped) technically acceptable or advisable?
>
> net use z: \\subdom.domain.com\share
What IP DNS IP address is the NT client using? I hope only your internal
DNS, as well as all of your cl ients and DCs. This is a common mistake and
can cause issues. I just want to ensure your machines are using the correct
DNS servers.
Are there any errors on your DCs' Event logs?
Ace
.
- Follow-Ups:
- Re: net use z: \\FQDN\share issue
- From: Ace Fekay [MVP]
- Re: net use z: \\FQDN\share issue
- References:
- Re: net use z: \\FQDN\share issue
- From: Ace Fekay [MVP]
- Re: net use z: \\FQDN\share issue
- Prev by Date: Re: net use z: \\FQDN\share issue
- Next by Date: Re: WINDOWS 2003
- Previous by thread: Re: net use z: \\FQDN\share issue
- Next by thread: Re: net use z: \\FQDN\share issue
- Index(es):
Relevant Pages
|
Loading