[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Windows 2000 Domain, DFS Inaccessible shares and DCOM error

Posted on 2004-11-20
Medium Priority
Last Modified: 2011-04-14
Windows 2000 (SP4) Domain running DFS.
Windows XP / 2000 workstations


Over the last two weeks a few windows XP clients have been experiencing problems accessing our DFS shares. Sparadocially when they try to access a share they may get the error "Z:\ is not accessable. The network path was not found." If I access the shares via a UNC to a server holding a replica of the share it works fine. If I reboot the workstation it then works fine for a while.

My workstation eventlog is filling up with the following DCOM error, but nothing is showing in any of the server error logs.

Source: DCOM
Event ID: 10009

DCOM was unable to communicate with the computer computername.domainname(pdc) using any of the configured protocols.

I have checked the component services / default protocol setting as per the MS article but this doesn't apply to me. If you have any ideas I would love to hear them.

Question by:emailjws
  • 4
  • 2
LVL 12

Expert Comment

ID: 12641348
IS this the KB you read?


Distributed Component Object Model (DCOM) applications that connect to a Microsoft Windows 2000- and Microsoft Windows XP-based computer and are configured to use only datagram protocols receive the following error message:

Not enough storage is available to complete this operation(0x8007000e)
DCOM clients that are configured to use only datagram protocols that connect a Windows 2000 and Windows XP DCOM server receive the following error message:

The RPC Server is unavailable (Ox800706ba)
In addition, a message similar to the following appears in the Event Viewer:
Description:DCOM was unable to communicate with the computer <WWTOKEN>Remote Server Name</WWTOKEN> using any of the configured protocols
To connect to a DCOM server on Windows 2000 and Windows XP, there must be at least one common connection-oriented protocol between the client and DCOM server.


Component Services Administrative tool or DCOMCNFG incorrectly allows you to add Datagram User Datagram Protocol/Internet Protocol (UDP/IP) and Datagram Internet packet exchange (IPX) protocols to the Default Protocols tab. Windows 2000 and Windows XP do not support any datagram protocols.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
242022 INFO: DCOM on Microsoft Windows 2000 Does Not Support Any Datagram (UDP) Protocols


Make sure that connection-oriented protocols are in the DCOM protocols tab. Remove any of the Datagram protocols from DCOM protocols tab.
Bring up the Component Services Administrative tool. On the Start menu, point to Programs, Administrative Tools, and then click Component Services.
In the console tree of the Component Services Administrative tool, right-click the computer on which you want to configure the protocol, to bring up the context menu.
Click the Properties menu to bring up Computer Properties dialog box.
Click the Default Protocols tab.
If you have any of the Datagram protocols (UDP/IP or IPX) protocols listed here, click to select, and then click Remove.
If you do not have any of the connection-oriented protocols in the list, click Add to bring up Select DCOM protocol and endpoint dialog box.
Choose Connection-oriented TCP/IP Protocol as the protocol sequence, and then click OK.
Add any or all of the connection-oriented protocols to the default protocols this way.
Move Connection-oriented TCP/IP Protocol to the top of the list.
Restart the computer for the changes to take effect.

Author Comment

ID: 12641920
Yeah that's the one.

Author Comment

ID: 12644771
Just a bit of additional information, I am getting this problem evey day now. However if I do a ipconfig /renew it works again.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

LVL 12

Accepted Solution

valicon earned 1500 total points
ID: 12661883
Are the same clients having this issue or is it different clients?  What are TCP/IP and DNS settings for the clients?  Has this ever worked correctly since it was setup or is this a new problem?

Author Comment

ID: 12662661
The are a few client having this problem, but it seems to be limited mainly to XP clients.
All clients are getting their TCP/IP address and DNS settings from the DHCP server configured on one of the DCs. This was working fine until about two weeks ago which is when I first started noticing this problem.

The connection to our remote site is flakey and goes down at least once a day for varied amounts of time. I originally thought as files got back logged for replication and the NTDS consistency checker started complaining that maybe the DFS is going into a state where it errors and becoming unavailable. But as I said before simply renewing my IP address resolves the prtoblem from the client so it can't be anything to do with that.

I do have RRAS running on another server providing internet conenction sharing, maybe it is this that is causing the problem?

Author Comment

ID: 12771644
Problem was caused by an incorrect DNS setup. External ISP DNS servers where included in the scope options of the DNS server, once removed and added a forwards everything worked again.

Thanks valicon for your input.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Applications for our next round of the Experts Exchange Scholarship Contest are starting to roll in. It made us wonder what our past winners are up to these days. Here's a look at what four winners experienced with the contest and what they're doing…
Integration Management Part 2
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?
Suggested Courses
Course of the Month19 days, 6 hours left to enroll

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question