OH ALMIGHTY GOD SOMEONE HELP! W2k3 Server File Sharing Issue.

ah...ok heres the deal and I can't figure it to save my life.
Ok the problem in its most basic form, the part my brain doesn't have
computing power to solve is this.
On a windows server 2003 platform I have shared folders in the root drive.
I can share these folers with the 'everyone' read access default. No problem.
However if a user (or even me as an admin) attempts to map this network
drive via (tools ...map network drive...etc) It gives me the following error:
"configuration information could not be read from the domain
controller,either because the machine is unavailable, or access has been
denied" The mapping is the typical \\server\share.
Now heres the kicker. I learned that I can map network drivers (after making
them avail. to be shared) by using (tools..map network drive.etc) and
specifying the option to 'map as a different user'. I've used admin and
domain user accounts and they both work as normal and I can see the contents
of the share.
--
Ok so how exactly do I fix this problem!!!
Thank you Tech Community,!!

"ktillman" <(E-Mail Removed)> wrote:

>ah...ok heres the deal and I can't figure it to save my life.
>Ok the problem in its most basic form, the part my brain doesn't have
>computing power to solve is this.
>On a windows server 2003 platform I have shared folders in the root drive.
>I can share these folers with the 'everyone' read access default. No problem.
>However if a user (or even me as an admin) attempts to map this network
>drive via (tools ...map network drive...etc) It gives me the following error:
>"configuration information could not be read from the domain
>controller,either because the machine is unavailable, or access has been
>denied" The mapping is the typical \\server\share.
>Now heres the kicker. I learned that I can map network drivers (after making
>them avail. to be shared) by using (tools..map network drive.etc) and
>specifying the option to 'map as a different user'. I've used admin and
>domain user accounts and they both work as normal and I can see the contents
>of the share.

You may have DNS or AD issues. I'd suggest getting NETDIAG and DCDIAG
(google & download) and running them. If they get any errors, try running
them with /FIX; if that doesn't help, analyse the problem.

Can you map the drives from the server back to itself?

/kenw
Ken Wallewein
K&M Systems Integration
Phone (403)274-7848
Fax (403)275-4535
(E-Mail Removed)
www.kmsi.net

Ken thank you for responding. I've done as you said and got the following
feedback returned from the command line: It refers to DNS could this be issue?
----
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'gateway366.thetillmans.local.'. [ERROR_TIMEOUT]
The name 'gateway366.thetillmans.local.' may not be registered
in DN
S.
[FATAL] File \config\netlogon.dns contains invalid DNS entries.
[FA
TAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL] No
DNS s
ervers have the DNS records for this DC registered.


The command completed successfully

C:\Documents and Settings\Administrator.GATEWAY366>

"(E-Mail Removed)" wrote:

> "ktillman" <(E-Mail Removed)> wrote:
>
> >ah...ok heres the deal and I can't figure it to save my life.
> >Ok the problem in its most basic form, the part my brain doesn't have
> >computing power to solve is this.
> >On a windows server 2003 platform I have shared folders in the root drive.
> >I can share these folers with the 'everyone' read access default. No problem.
> >However if a user (or even me as an admin) attempts to map this network
> >drive via (tools ...map network drive...etc) It gives me the following error:
> >"configuration information could not be read from the domain
> >controller,either because the machine is unavailable, or access has been
> >denied" The mapping is the typical \\server\share.
> >Now heres the kicker. I learned that I can map network drivers (after making
> >them avail. to be shared) by using (tools..map network drive.etc) and
> >specifying the option to 'map as a different user'. I've used admin and
> >domain user accounts and they both work as normal and I can see the contents
> >of the share.
>
> You may have DNS or AD issues. I'd suggest getting NETDIAG and DCDIAG
> (google & download) and running them. If they get any errors, try running
> them with /FIX; if that doesn't help, analyse the problem.
>
> Can you map the drives from the server back to itself?
>
> /kenw
> Ken Wallewein
> K&M Systems Integration
> Phone (403)274-7848
> Fax (403)275-4535
> (E-Mail Removed)
> www.kmsi.net
>

Definitely. DNS is critical to Active Directory. If the /FIX options
don't help, you'll need to dig. The Minasi.com web site has some good
info. I can't help you much further here; you need to understand how to
coinfigure DNS.

/kenw

"ktillman" <(E-Mail Removed)> wrote:

>Ken thank you for responding. I've done as you said and got the following
>feedback returned from the command line: It refers to DNS could this be issue?
>----
>DNS test . . . . . . . . . . . . . : Failed
> [WARNING] Cannot find a primary authoritative DNS server for the
>name
> 'gateway366.thetillmans.local.'. [ERROR_TIMEOUT]
> The name 'gateway366.thetillmans.local.' may not be registered
>in DN
>S.
> [FATAL] File \config\netlogon.dns contains invalid DNS entries.
>[FA
>TAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL] No
>DNS s
>ervers have the DNS records for this DC registered.
>
>
>The command completed successfully
>
>C:\Documents and Settings\Administrator.GATEWAY366>
>
>"(E-Mail Removed)" wrote:
>
>> "ktillman" <(E-Mail Removed)> wrote:
>>
>> >ah...ok heres the deal and I can't figure it to save my life.
>> >Ok the problem in its most basic form, the part my brain doesn't have
>> >computing power to solve is this.
>> >On a windows server 2003 platform I have shared folders in the root drive.
>> >I can share these folers with the 'everyone' read access default. No problem.
>> >However if a user (or even me as an admin) attempts to map this network
>> >drive via (tools ...map network drive...etc) It gives me the following error:
>> >"configuration information could not be read from the domain
>> >controller,either because the machine is unavailable, or access has been
>> >denied" The mapping is the typical \\server\share.
>> >Now heres the kicker. I learned that I can map network drivers (after making
>> >them avail. to be shared) by using (tools..map network drive.etc) and
>> >specifying the option to 'map as a different user'. I've used admin and
>> >domain user accounts and they both work as normal and I can see the contents
>> >of the share.
>>
>> You may have DNS or AD issues. I'd suggest getting NETDIAG and DCDIAG
>> (google & download) and running them. If they get any errors, try running
>> them with /FIX; if that doesn't help, analyse the problem.
>>
>> Can you map the drives from the server back to itself?
>>
>> /kenw
>> Ken Wallewein
>> K&M Systems Integration
>> Phone (403)274-7848
>> Fax (403)275-4535
>> (E-Mail Removed)
>> www.kmsi.net
>>
Ken Wallewein
K&M Systems Integration
Phone (403)274-7848
Fax (403)275-4535
(E-Mail Removed)
www.kmsi.net

OK! Thanks for getting me this far. I will scour the Minasi.com website and
find a solutions. Thanks for everything,!!

k

"(E-Mail Removed)" wrote:

> Definitely. DNS is critical to Active Directory. If the /FIX options
> don't help, you'll need to dig. The Minasi.com web site has some good
> info. I can't help you much further here; you need to understand how to
> coinfigure DNS.
>
> /kenw
>
> "ktillman" <(E-Mail Removed)> wrote:
>
> >Ken thank you for responding. I've done as you said and got the following
> >feedback returned from the command line: It refers to DNS could this be issue?
> >----
> >DNS test . . . . . . . . . . . . . : Failed
> > [WARNING] Cannot find a primary authoritative DNS server for the
> >name
> > 'gateway366.thetillmans.local.'. [ERROR_TIMEOUT]
> > The name 'gateway366.thetillmans.local.' may not be registered
> >in DN
> >S.
> > [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> >[FA
> >TAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL] No
> >DNS s
> >ervers have the DNS records for this DC registered.
> >
> >
> >The command completed successfully
> >
> >C:\Documents and Settings\Administrator.GATEWAY366>
> >
> >"(E-Mail Removed)" wrote:
> >
> >> "ktillman" <(E-Mail Removed)> wrote:
> >>
> >> >ah...ok heres the deal and I can't figure it to save my life.
> >> >Ok the problem in its most basic form, the part my brain doesn't have
> >> >computing power to solve is this.
> >> >On a windows server 2003 platform I have shared folders in the root drive.
> >> >I can share these folers with the 'everyone' read access default. No problem.
> >> >However if a user (or even me as an admin) attempts to map this network
> >> >drive via (tools ...map network drive...etc) It gives me the following error:
> >> >"configuration information could not be read from the domain
> >> >controller,either because the machine is unavailable, or access has been
> >> >denied" The mapping is the typical \\server\share.
> >> >Now heres the kicker. I learned that I can map network drivers (after making
> >> >them avail. to be shared) by using (tools..map network drive.etc) and
> >> >specifying the option to 'map as a different user'. I've used admin and
> >> >domain user accounts and they both work as normal and I can see the contents
> >> >of the share.
> >>
> >> You may have DNS or AD issues. I'd suggest getting NETDIAG and DCDIAG
> >> (google & download) and running them. If they get any errors, try running
> >> them with /FIX; if that doesn't help, analyse the problem.
> >>
> >> Can you map the drives from the server back to itself?
> >>
> >> /kenw
> >> Ken Wallewein
> >> K&M Systems Integration
> >> Phone (403)274-7848
> >> Fax (403)275-4535
> >> (E-Mail Removed)
> >> www.kmsi.net
> >>
> Ken Wallewein
> K&M Systems Integration
> Phone (403)274-7848
> Fax (403)275-4535
> (E-Mail Removed)
> www.kmsi.net
>

"ktillman" <(E-Mail Removed)> wrote in message
news:92D14020-1E23-4217-94E6-(E-Mail Removed)...
> Ken thank you for responding. I've done as you said and got the following
> feedback returned from the command line: It refers to DNS could this be
> issue?
> ----
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'gateway366.thetillmans.local.'. [ERROR_TIMEOUT]
> The name 'gateway366.thetillmans.local.' may not be registered
> in DN
> S.
> [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> [FA
> TAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL] No
> DNS s
> ervers have the DNS records for this DC registered.
>
>
> The command completed successfully
>
> C:\Documents and Settings\Administrator.GATEWAY366>

<snip>

Are you running AD-integrated DNS on this box? Easiest to do this. Then
point *all* clients & servers at the internal DNS server's IP only - no
external IPs. Set up forwarders in your DNS server itself to handle external
queries.

Yes.. It is AD-integrated DNS on the box. I've done as you said and pointed
all client and server IPs to the DNS IP address on the box (10.34.7.9).
However I get the same issue; unable to map network drives or access network
shares local to this box via the schema \\server\share. Another thing I
noticed is I opened 'computer managment' via admin tools. In it I went to the
'sessions' folder to show open session. This is what happens. ANYTIME I
attempt to connect to a share \\server\share computer management shows a
session of USERNAME:GATEWAY366$ as a user that has this connection open. It
lasts for 10seconds and dissappears.
If I choose to open a network share via \\server\share as a different user
(any user in AD) computer managment reflects the user as :%USERNAME% <IE Phil
Hawk> and the network session he has open. AND the dam share folder opens
with no problem using \\server\share. So I know its not permissions and I
finally got that DNS issue fix as stated above.
So in its purest form I cannot open share folders locally (on the server
box) or from any client using \\server\share.Computer managment shows a user
of GATEWAY366$ (which is not listed in AD btw; but is the name of the server
box).
I can open a share if I 'run as a different user'.

And It bewilders me to no end...... Any other suggestions possibly you can
think of? I'm pretty desperate now so Ill try almost anything. (i'm thinking
about tearing down the domain itself and recreating..hate to do that but
....I'm running out of options..)

"Lanwench [MVP - Exchange]" wrote:

>
> "ktillman" <(E-Mail Removed)> wrote in message
> news:92D14020-1E23-4217-94E6-(E-Mail Removed)...
> > Ken thank you for responding. I've done as you said and got the following
> > feedback returned from the command line: It refers to DNS could this be
> > issue?
> > ----
> > DNS test . . . . . . . . . . . . . : Failed
> > [WARNING] Cannot find a primary authoritative DNS server for the
> > name
> > 'gateway366.thetillmans.local.'. [ERROR_TIMEOUT]
> > The name 'gateway366.thetillmans.local.' may not be registered
> > in DN
> > S.
> > [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> > [FA
> > TAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL] No
> > DNS s
> > ervers have the DNS records for this DC registered.
> >
> >
> > The command completed successfully
> >
> > C:\Documents and Settings\Administrator.GATEWAY366>
>
> <snip>
>
> Are you running AD-integrated DNS on this box? Easiest to do this. Then
> point *all* clients & servers at the internal DNS server's IP only - no
> external IPs. Set up forwarders in your DNS server itself to handle external
> queries.
>
>
>
>

*This thread can be closed!!* Problem resolved. What you suggested seemed to
fix the issue. I just had to do a ipconfig/flushdns after pointing all
clients to the DNS server IP and removing all other DNS IPs. Had the DNS
forward to the router IP address for external resolution. And YAHTZEE! seemed
to do it!

Much appreciation,

Kimani

"Lanwench [MVP - Exchange]" wrote:

>
> "ktillman" <(E-Mail Removed)> wrote in message
> news:92D14020-1E23-4217-94E6-(E-Mail Removed)...
> > Ken thank you for responding. I've done as you said and got the following
> > feedback returned from the command line: It refers to DNS could this be
> > issue?
> > ----
> > DNS test . . . . . . . . . . . . . : Failed
> > [WARNING] Cannot find a primary authoritative DNS server for the
> > name
> > 'gateway366.thetillmans.local.'. [ERROR_TIMEOUT]
> > The name 'gateway366.thetillmans.local.' may not be registered
> > in DN
> > S.
> > [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> > [FA
> > TAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL] No
> > DNS s
> > ervers have the DNS records for this DC registered.
> >
> >
> > The command completed successfully
> >
> > C:\Documents and Settings\Administrator.GATEWAY366>
>
> <snip>
>
> Are you running AD-integrated DNS on this box? Easiest to do this. Then
> point *all* clients & servers at the internal DNS server's IP only - no
> external IPs. Set up forwarders in your DNS server itself to handle external
> queries.
>
>
>
>

"ktillman" <(E-Mail Removed)> wrote in message
news:1B3A1138-4C3E-4A04-812D-(E-Mail Removed)...
> *This thread can be closed!!* Problem resolved. What you suggested seemed
> to
> fix the issue. I just had to do a ipconfig/flushdns after pointing all
> clients to the DNS server IP and removing all other DNS IPs. Had the DNS
> forward to the router IP address for external resolution. And YAHTZEE!
> seemed
> to do it!
>
> Much appreciation,
>
> Kimani

You're very welcome; glad you got it running.

>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>> "ktillman" <(E-Mail Removed)> wrote in message
>> news:92D14020-1E23-4217-94E6-(E-Mail Removed)...
>> > Ken thank you for responding. I've done as you said and got the
>> > following
>> > feedback returned from the command line: It refers to DNS could this be
>> > issue?
>> > ----
>> > DNS test . . . . . . . . . . . . . : Failed
>> > [WARNING] Cannot find a primary authoritative DNS server for
>> > the
>> > name
>> > 'gateway366.thetillmans.local.'. [ERROR_TIMEOUT]
>> > The name 'gateway366.thetillmans.local.' may not be
>> > registered
>> > in DN
>> > S.
>> > [FATAL] File \config\netlogon.dns contains invalid DNS entries.
>> > [FA
>> > TAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL]
>> > No
>> > DNS s
>> > ervers have the DNS records for this DC registered.
>> >
>> >
>> > The command completed successfully
>> >
>> > C:\Documents and Settings\Administrator.GATEWAY366>
>>
>> <snip>
>>
>> Are you running AD-integrated DNS on this box? Easiest to do this. Then
>> point *all* clients & servers at the internal DNS server's IP only - no
>> external IPs. Set up forwarders in your DNS server itself to handle
>> external
>> queries.
>>
>>
>>
>>