• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 308
  • Last Modified:

Windows Server 2003 R2 SP2

Please help! I get the following error on my Windows Server 2003 R2 SP2 every hour, I have done some research but everything I see points to NOT having the authenticated users as a member of the users group under the builtin folder. I do have authenticated users as part of the members in the users group under builtin. Have not found anything relating to the domain does not exist or can not be contacted.  The error specific details info there is about a 100 of them in the event log

File Server Resource Manger failed to enumerate share paths or DFS paths. Mappings from local file paths to share and DFS paths may be incomlete or temporaily unavailable. FSRM will retry the Operation at a later time.

Error-specific details:
       Error: (0x8007054b) The specified domain either does not exist or could not be contacted.
SRMSVC-Error.jpg
0
conlin
Asked:
conlin
  • 4
  • 3
1 Solution
 
ajbarronCommented:
Can you please provide more information on your current setup? Is the server a primary DC or a or a second DC in the domain? Or maybe a member server? Also you may want to check that DNS has been configured for the domain correctly and all records point to the correct locations.

-Anthony
0
 
conlinAuthor Commented:
This is one server in the domain as the DC, DHCP and DNS roles
0
 
conlinAuthor Commented:
The boss actually did windows updates this past weekend and after the reboot is when we started seeing this error.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
ajbarronCommented:
Is this error appearing on the dc itself? It sounds like Check to see if the server has a computer account in the domain. Have you tired rolling back the updates to see if it was one of the updates that caused the issue?
0
 
conlinAuthor Commented:
Yes it is appearing on the DC itself.  I will try rolling back some updates.  Thanks
0
 
conlinAuthor Commented:
Cant Roll back any of the .net crap, but i can roll back some of the security updates.
0
 
ajbarronCommented:
Here is an article i found that may be of use to you...

http://support.microsoft.com/kb/310461

Have you checked your DNS records on the server? It sounds like (if its not the updates) that DNS is not pointing to your domain. When you try to access a domain, DNS is queried in order to resolve the domain to an IP address. This error can occur if that ip address is not pointing to your DC. Also check that the DNS settings on the network port point to the IP address of your local dns server.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now