Windows 2000 Domain, DFS Inaccessible shares and DCOM error

Windows 2000 (SP4) Domain running DFS.
Windows XP / 2000 workstations

All,

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
User: NT AUTHORITY\NETWORK SERVICE

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.

Thanks.
emailjwsAsked:
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.

valiconCommented:
IS this the KB you read?






SYMPTOMS

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:
EventID:10009
Source:DCOM
Type:Error
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.

CAUSE

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

RESOLUTION

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.
0
emailjwsAuthor Commented:
Yeah that's the one.
0
emailjwsAuthor Commented:
Just a bit of additional information, I am getting this problem evey day now. However if I do a ipconfig /renew it works again.
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

valiconCommented:
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?
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
emailjwsAuthor Commented:
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?
0
emailjwsAuthor Commented:
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.
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
Windows 2000

From novice to tech pro — start learning today.

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.