Link to home
Create AccountLog in
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Avatar of BRI-Consulting
BRI-Consulting

DFS issues
Hello,

I am having some DFS issues and have narrowed it down to a windows firewall issue.  When the firewall is on I cannot connect to the share and FRS does not work between two different shares.  When the firewall is off, I can connect to the share and FRS works.

My question is, what needs to be added to windows firewall in order for DFS and FRS to work properly.

I have added the following:
TCP - 137, 139, 389, 135, 445
UDP - 137, 138, 389, 445
File and Printer Sharing

But still no success.  What else needs to be done?

Thanks in advance.

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of Robin HumanRobin Human🇿🇦

Take a look at the following article re: dfsrdiag (this would suggest that you need to allow this .exe through the firewall as well)
https://www.experts-exchange.com/questions/22746536/What-SPECIFIC-ports-does-DFS-under-Windows-2003-R2-require.html
Avatar of BRI-ConsultingBRI-Consulting

ASKER

I allowed the dfsrdiag.exe and still no luck.

I also did:
dfsrdiag StaticRPC /port:nnnnn /Member:Branch01.sales.contoso.com

and the operation failed.  Any other suggestions?
Avatar of Robin HumanRobin Human🇿🇦

when you ran dfsrdiag, did you set it to a particular static port and open that port on the firewall?
the command should look something like this: dfsrdiag staticRPC /port:{port number} /Member:{your server's fqdn - ie. server1.joebloggs.com}
see this article:
http://rockstarguys.com/blogs/colin/archive/2008/01/25/locking-down-dfs-for-windows-firewall.aspx
Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Avatar of BRI-ConsultingBRI-Consulting

ASKER

I get this:

C:\WINDOWS\ServicePackFiles\i386>dfsrdiag StaticRPC /port:135 /Member:<computer>

[ERROR] Failed to connect to WMI services on computer: <computer>

Operation Failed
Avatar of Robin HumanRobin Human🇿🇦

You need to start the Windows Management Instrumentation services on the server;
 
Avatar of BRI-ConsultingBRI-Consulting

ASKER

That service is started.
Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of BRI-ConsultingBRI-Consulting

ASKER

DFS shows both targets as 'online'.  However, files and folders still won't sync.
ASKER CERTIFIED SOLUTION
Avatar of BRI-ConsultingBRI-Consulting

ASKER

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).