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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!