Windows Server 2008 R2 Cross-Domain File Sharing Not Working

Odd problem with sharing across two Domains in a single Forest.

Domain controller DC1 is in Domain1. Domain controller DC2 is in Domain2. Both domains are separate trees in the same Forest. Both DC's are Windows 2008 R2.

No problem with browsing for users and groups across domains and assigning the relevant permissions to shares and folders. No evidence of replication or other AD issues.

Permissions on shares and folders are definitely correct.

We can browse to System shares across domains. Eg browse to \\dc1\sysvol or \\dc1\c$ from DC2 (or another machine on Domain2) works as expected. (Using FQDN, just shortened here for easier typing).

Browsing to \\dc1\myshare from DC2 or another machine on Domain2 brings up a "path not found" error. Actual error varies depending on OS but they are similar. Shares work as expected within Domain1.

Server1 is a member server (Windows 2008) on Domain1. No problem browshing to shares on Server1 from Domain2.

The same problem occurs in reverse - ie accessing shares on DC2 from Domain1.

We have many other domains set up in a similar way using Server 2008 DC's and have not encountered this problem. The problem seems limited to Server 2008 R2.

I have seen similar issues with SMB shares when operating across WAN with IPSec VPN, but this is across a Gb switch. Servers are on seperate subnets but there is no network security between them. FIrewall on the Windows servers has been disabled.

Any ideas?


milottAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gemartiCommented:
"path not found" seems like a address resolution issue. Can you ping DC1 server from DC2 using FQDN? If no I would start looking at DNS on DC2 and make sure it knows about DC1.

0
milottAuthor Commented:
I can ping and even browse system shares like Sysvol and C$. It's not a name resolution issue.
It seems that something in 2008 R2 security policy has changed from previous versions.
0
milottAuthor Commented:
Had to solve this ourselves. Standard shares resolved itself after a day or so - guessing it was replication issue somewhere but couldnt see any issues.
DFS was a bit trickier. By default it uses NetBIOS names resolution which wasnt working across domains. Forced it to use DNS and all good.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gemartiCommented:
..." DFS was a bit trickier. By default it uses NetBIOS names resolution which wasnt working across domains. Forced it to use DNS and all good."....

I don't really care about the points however I believe my very first comment dealt with address resolution.....

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.