UNABLE TO access network share

Hi
My customer has a 2003 pdc (\\mammoth), a 2003 domain member with exchange and a dozen xp workstations. They have experienced problems recently with sql server on the pdc which have now apparently been resolved after deleting a corrupted database. Most workstations can access the SQL application. The SQL application requires access by name - \\mammoth\mamut' Two PCs cannot access the application. They can see the shares as \\192.168.0.14\mamut but not as \\mammoth\mamut. They can see other shares on the 2003 member server and on xp PCs. The server can see a share on the problem PC as well.
Since the problem started a week ago the PC was generating frequent errors 10009 for the server //mammoth. Since I have been looking at it, today, it has now stopped, but it is still not possible to access the server share. I have googled for various suggestions but made no difference

10009 - DCOM was unable to communicate with the computer mammoth using any of the configured protocols.
peter_lawrieAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

jameskeagieCommented:
Sounds like a DNS issue.  On the systems not working - try from the command line the following:

ipconfig /flushdns

Then try pinging the share name (ping \\mammoth\share$)

If it resolves to the correct IP, your DNS is working properly and you may have some other issue.  Let me know if it resolves correctly but still can't map - but if it resolves - you should then be able to map to that drive either from My Computer, or the command line.

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
peter_lawrieAuthor Commented:
Hi
Thanks for the response, I could not ping the server and flushdns did not help. While looking at this, it occurred to me to check the hosts file. It had the wrong IP address for //mammoth. The serer has two lan cards, one was not being used and I suspected it was the cause of poor dns resolution so I disabled it. The PC with the problem was pointing at the disabled IP instead of the correct one!
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
Programming Languages-Other

From novice to tech pro — start learning today.