Problem accessing / mapping of shares in a different domain.

I have a single forest with multiple domains. (root domain) (child domain) (child domain)

I have a third party DNS server where all my clients point to.
The third party DNS server is synchronized with my child domains.
My client pc’s are joint to domain and can access/map any shares via name to a file server in the domain with no problems.

My problem is when users want to access/map shares to a file server in the domain they get error.
Logon unsuccessful:
The user name you typed is the same as the user name you logged in with.
That user name has already been tried. A domain controller cannot be found to very that user name.

When I use ip address of file server it works and when I try to access/map shares in domain from a pc which is not joint to domain it will ask for password and when I type in it works.

Please advice/help why can’t my pc’s joint to domain access/map shares to the file server in domain.

I can ping successfully the FQDN of file server and it can resolve ip address to name.
I also can resolve the DC.
My trust between domains is also working as I can use username and password of user in domain to access files in domain when pc is not joining to any domain.
Who is Participating?
MaheshConnect With a Mentor ArchitectCommented:
Download Portqueryui tool and check if required ports are opened from both domain controllers vice versa ?

If you get error here, you need to clear that 1st

Also verify DNS name resolution vice versa with both domain controllers
1.On your DNS, click Start, and then click Run.
2.In the Open box, type cmd.
3.Type nslookup, and then press ENTER.
4.Type set type=all, and then press ENTER.
5.Type _ldap._tcp.dc._msdcs.Domain_Name, where Domain_Name is the name of your domain and then press ENTER...if this resolves
5.Type _ldap._tcp.dc._msdcs.Domain_Name, where Domain_Name is the name of opposite domain and then press ENTER

To do what you are trying to do, just make dns host (A) record for file servers in us domain to dns servers (under zone) in uk domain and vice versa.

This will allow you to access file servers across domains by name such as \\server1

Single lable name will work within same domain or within workgroup environment fine in normal case but it will not work as expected between cross domains residing in different subnets

ciscosuppAuthor Commented:
I tried no luck same problem.
I try mapping/accessing shared in other domain with FQDM and I can only use name as my dns suffix is added for the other domain.
I also can resolve ip to name and name to ip successfully of the fileserver
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

That is true, if you add host (A) record for other domain file server in your dns zone, its FQDN will obviously be created as
But this is only available one of the best method.
once you created host (A) records, what important is it should be able to resolve to IP address of file server in another domain.

Can you please check on client computers and domain controllers advanced TCP/IP properties \ DNS tab for below.
ensure that "Append Primary and connection specific dns suffixes" radio button is selected
Ensure that "Append parent suffixes of primary dns suffix" checkbox is selected
Ensure that "register this connection addresses in Dns" checkbox is selected
If there is any deviation in the above settings, its probably you will face name resolution and connectivity issues

ciscosuppAuthor Commented:

In uk domain I have a file server called fileuk and in usa domain I have a file server called fileusa

So basically I have to create one A record in both dns zones and zone
Fileusa (FQDN zone
Fileuk (FQDN

Please advice if this is what you mean.
yes, you are right

ciscosuppAuthor Commented:
Ok tried it no luck.
It’s not a DNS problem as it can resolve name to it and ip to name with no problem of file server.

What else can be the problem any advice
If you access shares via \\\share is it accessible ?
Do you have any firewall enabled between two domains or windows firewall on file servers that is blocking NetBIOS name resolution ?

If you ping hostname of us domain file server from uk domain, is it pings ?
If you ping FQDN of us domain file server from uk domain, is it pings ?

ciscosuppAuthor Commented:
yes I can ping both servers from both different domains.
Records for both fileserver can also resolve from ip to name and name to ip.
ciscosuppAuthor Commented:
will try it
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.