Unable to open network share drive: \\server\share anymore

Discussion in 'DNS Server' started by ktillman, Nov 16, 2005.

  1. ktillman

    ktillman Guest

    Hello Technet got a problem cannot figure it out.
    I can no longer access network shares via \\servername\share
    I can access them via \\ip address\share or even FQDN \\FQDN\share
    The error received when I attempt via \\servername\share is "configuration
    information could not be read by the domain controller . .. etc"
    The problem this is having is all roaming profiles cannot be found when
    users logon. Thinking it was DNS this is what I verified.
    ping works
    ping gateway366.thetillmans.local
    nslookup resolves to gateway366.thetillmans.local
    nslookup gateway366 resolves to (these are real stats)
    So I stopped thinking DNS was the issue. I checked the permissions and
    domain users have the normal 'read' access to all network shares. Funny thing
    is if I create a new share and attempt to access it..boom same error. Very
    frustrating..any ideas? please
    Clueless in philadelphia,

    ktillman, Nov 16, 2005
    1. Advertisements

  2. ktillman

    Mark Guest

    You can do FQDN and IP address mapping but not hostname ... are your dns
    suffix search lists configured correctly on the clients ?
    Mark, Nov 16, 2005
    1. Advertisements

  3. ktillman

    ktillman Guest

    Mark I checked the dns suffix search lists and they are configured correctly.
    They are configured with a suffix of: TheTillmans.local.

    So I'm back to square one. To recap I cannot access any network drives via
    the following schema: \\server\share
    can only access via \\server.thetillmans.local\share or \\\share
    When I attempt via \\server\share via MY Computer I get error:
    "configuration information could not be read from the domain controller,
    either because the machine is unavailable or access has been denied."
    ktillman, Nov 17, 2005
  4. ktillman

    ktillman Guest

    Ok I believe I have narrowed this issue down. I think it has to do with a one
    way trust I have on the domain. I attempted to map a network drive and use
    the 'runas' option and user a user account. The drive mapped as normal with
    So when I attempt to map the drive on the domain controller without using
    the 'runas' option it fails with the error in my previous post. So no I
    attempted to remove the trust that is setup on the DC however I get an error
    'internal error'. And the trust never is removed.
    So now my question turns to how do I remove a Trust if It can't be done via
    the MMC snap in!

    ktillman, Nov 17, 2005
  5. ktillman

    Mark Guest

    If you're trying to map a drive over a trust (domainA - > domainB), where are
    you logged in and who are you logged in as when it succeeds\fails? Whats the
    situation with the domains (same tree/forest, separate forest ?). How does
    name resolution work between the 2 domains?
    Your other question ... you can use "netdom trust" to add\remove\reset
    trusts from the commandline.

    Mark, Nov 17, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.