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 10.34.7.9 works ping gateway366.thetillmans.local nslookup 10.34.7.9 resolves to gateway366.thetillmans.local nslookup gateway366 resolves to 10.34.7.9 (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, K
You can do FQDN and IP address mapping but not hostname ... are your dns suffix search lists configured correctly on the clients ?
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 \\10.34.7.9\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."
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 \\server\share. 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! THANKS TECHNET. Kimani
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. Thanks, Mark
