Target name resolution error

I have a two node Windows Server running Exchange target name resolution error which went through a name change on the primary cluster resource. The DNS and computer entries came online with the updated name after the update, and no other significant errors are being logged. The server manager console shows an error on the All Servers section for "kerberos target resolution error" for the cluster name.

I have a problem stopping me from progressing in my learning, my test bench in hyperv gives me this error when I add the 2nd domain controller. Check these to make sure they are correct. Could you ping NU-DC2 by name? This topic has been locked by an administrator and is no longer open for commenting. To continue this discussion, please ask a new question. Last year, we announced our plans to migrate the Spiceworks Community to a new platform.

Target name resolution error

Log in. Sign up. JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. Status Not open for further replies. We had one server running sbs which was running our exchange and active directory. We installed a new server with server enterprise and exchange and installed server standard on our server that was running sbs The server running standard is now our active directory server and is our domain controller. Most of the users had no problem reconnecting their outlook to the new server but there are a few users who didn't connect so easily. I had to manually go in and change their accounts to look at the new server.

Then, the user loses access to the share on the server. Here is a screen shot.

Connect and share knowledge within a single location that is structured and easy to search. I have just set up a new Hyper-V Server and connected it to the domain. I attempted to follow the Microsoft documentation to allow remote management via server manager. I enabled remote management in the server configuration command menu. I also allowed the server to respond to ping requests.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. This article describes methods that you can use to configure DNS if queries that are directed to the Internet are not resolved correctly, but local intranet name resolution functions correctly. The Cache. You can manually add root hints by using the DNS snap-in, replace the Cache. To manually add root hints on a Windows Server DNS server that is not configured as a domain controller:. To rename and replace the Cache. Stop the DNS service.

Target name resolution error

Connect and share knowledge within a single location that is structured and easy to search. I'm setting up a Windows lab environment. It has a WinR2 domain controller srv and I'd like to add another WinR2 server to the domain srv Actually, all goes well. I gave the new server a static IP address in the same subnet as the DC, pointed it to the right DNS server and added the server to the domain. I has quite a long error message that I'll post below.

Leaky librarian

It appears that it only works 'cleanly' on the node that owns the cluster name. Thanks in advance! I recently had a crash of this server. Improve this answer. Add a comment. Asked 10 years, 6 months ago. What I am not certain of is whether the object is still in the same Organizational Unit as it was originally. Changing how community leadership works on Stack Exchange: a proposal and I know I can set Preferred Owners, but wasn't sure whether that was best practice after reading a blog about"potential" issues last year. Deals Forum. Dealing with a situation where the home builders stripped the existing Cat5e cables back to the wall and evidently stapled the cables into place before the drywall was installed so I can't pull any slack. I found the problem in my setup. Skip to main content.

Connect and share knowledge within a single location that is structured and easy to search. I have just set up a new Hyper-V Server and connected it to the domain. I attempted to follow the Microsoft documentation to allow remote management via server manager.

Only after adding the server to server manager do I get the target name resolution error. I tried adding the server name to my deskops hosts file in which case I can now ping the server by name but I still get the same error in server manager. Hot Network Questions. On the account properties, "User cannot change password" and "Password never expires" are both checked. Stack Overflow for Teams — Start collaborating and sharing organizational knowledge. The documentation simply states that I should have to enable remote management on the server, add any user accounts that should be allowed remote access to the local administrator group, and then connect to it from server manager. The DNS and computer entries came online with the updated name after the update, and no other significant errors are being logged. Any ideas why I'm getting this error? Both the server and my desktop are connected to the domain. Guntars Svilpe. Related 3. Claim or contact us about this channel. Is this expected behavior? On last one we are getting following error:.