Solved

Changed Server name and can no longer UNC to computer name

Posted on 2015-01-05
10
109 Views
Last Modified: 2015-01-11
I changed a server to a new name, and I am able to access the shares via Ip address \\123.123.123.123\shares or from the system via \\localhost\shares but I am unable to access it via its name \\servername\shares.   I am able to ping it by name, RDP to it by name, just unable to access the UNC shares by name.  I ran into this on a server 2003 box 10 years or so ago and had to update something in the registry, but I can't find where that was.  This is a 2008 R2 box.  Any idea how I can fix this?
0
Comment
Question by:digital0g1c
  • 5
  • 4
10 Comments
 
LVL 43

Expert Comment

by:Steve Knight
ID: 40533073
Does it still respond on the "old" name, and it shows correctly in AD with the new name?  

Does it work with \\server.yourdomain.local\shares ?

You get the 'problem' of having to turn off "Strict Name Checking" still in 2008 R2, i.e. when you add a CNAME to DNS or via hosts table entries etc.  That just needs a registry entry "DisableStrictNameChecking" - a DWORD, value 1 at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters - very useful for adding extra aliases to incoporate old server names when amalgamating etc.

Also what does the output of this command show:

netdom computername servername /enumerate

Steve
0
 
LVL 1

Author Comment

by:digital0g1c
ID: 40533874
On that command, I get the network path was not found twice.  
I didn't add a CNAME, just changed the actual name.  It does show correctly in DNS and in AD.
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 40533894
Sure.  You replaced "servername" with the server's name?  It should show the names it responds on.

And does it respond to \\server.domain.local if it doesn't to \\server ?
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 17

Expert Comment

by:Tony Massa
ID: 40533972
http://technet.microsoft.com/en-us/library/ff660057(v=ws.10).asp

You're thinking of "Disable Strict Name Checking".  This is generally used when using an ALIAS to a server, but generally isn't necessary if you've renamed the computer.  The IP works because of NTLM authentication, but kerberos is a mutual-authentication scheme.  Your [edit] server may be having issues authenticating with domain controllers (getting a kerberos ticket).  You can use KLIST to check the tickets and maybe you just need to purge the tickets.

http://blogs.technet.com/b/tspring/archive/2014/06/23/viewing-and-purging-cached-kerberos-tickets.aspx

Rebooting does this normally.  You should also be able to view the failed kerberos authentication on the DCs, the server, or the desktop assuming you've enable security logging.
0
 
LVL 1

Author Comment

by:digital0g1c
ID: 40534071
So I was in a bit of hurry and rand the command without changing the name...  when changing the name I get "Access Denied"

I can try rebooting tonight.
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 40534098
Needs run-as-admin on a command prompt by the sounds of it.  As tmassa99 suggests though there should be event log entries by the bucket load on the client, server and/or dc a the time of the connection.  I just wanted to see what the server thought it was listening on name wise with that command.

Steve
0
 
LVL 1

Author Comment

by:digital0g1c
ID: 40534101
I did the run as administrator.  I first didn't but figured it would need that and did it again.    I will check event logs.
0
 
LVL 1

Accepted Solution

by:
digital0g1c earned 0 total points
ID: 40534299
Thanks for the input.  The issue was regarding adding the registry key mentioned here http://support.microsoft.com/kb/926642
I added the BackConnectionHostNames Registry entry with the local and FQDN to that key and it worked without a reboot.

I had found this article but skipped it because it references this problem after applying Server 2003 SP1.   But it worked for 2008 R2.
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 40534409
Bizarre!
0
 
LVL 1

Author Closing Comment

by:digital0g1c
ID: 40542946
The answer was the registry key update
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scenario:  You do full backups to a internal hard drive in either product (SBS or Server 2008).  All goes well for a very long time.  One day, backups begin to fail with a message that the disk is full.  Your disk contains many, many more backups th…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question