Clients can't connect by name

I have an ailing Windows s2008 R2 server.  This server has several file shares.  Users are able to connect to these shares using the IP in the UNC - \\10.12.50.192\data, but can't connect using the name - \\Win2008\data.  I get a message box saying "\\win2008 is not accessible.  You might not have permission to use this network resource.  Logon Failure: The target account name is incorrect"  

Net View give me a little more information.  When I do net view \\10.12.50.192\  I see all the shares on that machine.  When I do net view \\win2008 I get an error 5 - permission.

This server is also a DC.  I believe I could fix this problem by demoting it and repromoting it but it also has several of the FSMO roles on it.  When I try to move these roles to another server I get the message "Win32 error returned is 0x20af (The requested FSMO operation failed.  The current FSMO holder could not be contacted."  I am reluctant to seize the roles from that machine as that has always resulted in problems in the past.

I have tried rebooting the machine.

The recent history of this machine includes a half day of downtime and a transition from a single NIC in a 192.168.0.x/24 network to having two NICS with one in the 192.168.0.x/24 network and another in the 10.12.50.x/24 network to a single NIC in the 10.12.50.x/24 network.  The proper IP, 10.12.50.192 is registered in the DNS.  I don't have any name resolution problems I'm aware of.

Thanks for any help.

Bill
LVL 1
labdunnAsked:
Who is Participating?
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.

Wayne88Commented:
sounds like there is a problem with the name resolution, is netbios over tcp/ip enabled in services.msc?
0
unrealized92Commented:
Are you sure this machine is in the same workgroup?

Also, are you able to access your fileshares on the server directly by going to \\Win2008\ ?
0
Wayne88Commented:
Go to control panel > administrative tools > services

Can you verify the TCP/IP NetBIOS Helper service in services.msc is started?  If not then start the service and try again.  Make sure this is running on both the workstation and server too to be safe.

What happens when you ping the server by name?  Do you get host not found?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Hypercat (Deb)Commented:
What IPs are specified for the DNS server(s) on the 2008 server itself?  It should be pointing to itself, and I'm wondering if in the process of changing the IPs, the DNS setting wasn't changed or was set to the loopback address instead of the specific IP address of the server.
0
Wayne88Commented:
You also can try entering the server's ip address and name directly on the host file of the client machine.

10.12.50.192  Win2008

If it does work then the problem is with host name resolution.  You can follow this link for troubleshooting:

Microsoft TCP/IP Host Name Resolution Order: https://support.microsoft.com/en-us/kb/172218
0
Hypercat (Deb)Commented:
Also, make sure that the workstations have been restarted since the changes in the server IP address.  Some workstations could have cached the old IP address for that server in their local arp or DNS cache.
0
labdunnAuthor Commented:
Neither the clients (Windows 7)  or the server (Windows 2008 R2) have the NetBIOS over TCP service.

The client machines are all in a domain.  All client machines are having problems connecting to this server only.  They are able to access shares on other servers without resorting to the IP address.
0
Wayne88Commented:
Do you get a reply when you ping this server using the hostname?
0
labdunnAuthor Commented:
Yes I get a reply from the proper machine when pinging by hostname and FQDN.  

We have done ipconfig/flushdns on the client we were testing from after all the readdressing was completed.

All the problem server and the client we've been testing from are both using 10.12.51.2 as their DNS server.  We have verified that the DNS on 10.12.51.2 has the address 10.12.50.192  for the Windows2008 server

The NetBIOS over TCP service is started on Windows2008.
0
discgmanCommented:
You might need to copy and paste the error logs on the 2008 dns server and post here. Then we can analyze it better and look up some solutions.
0
Wayne88Commented:
If hostname resolution is fine when pinging and mapping to other servers using hostname are also fine then the only thing left that comes to mind is this:

https://windowsforum.com/threads/problem-connecting-to-network-drive-by-server-name-but-by-ip-address-works.68641/

This is similar to a problem I've run into myself, where targets could be pinged either way (by name or IP) but could be connected to only through their IPs (e.g. \\123.456.789.123 instead of \\servername), all this happening only from a Windows 7 machine. The targets could also be reached using "net use \\servername\resource", oddly. The error was something like "unknown user". Turns out stale credentials was being used from the Windows 7 machine. Have your users go to Control Panel: User Accounts: Manage My Account: Manage My Credentials. Most likely there will be saved credentials entries for the targets they're having trouble with. Have them delete the saved credentials entries and then try reconnecting normally.
0
labdunnAuthor Commented:
I had to call Microsoft for help on this one.  The problem was Secure channel was broken for Win2008.  MS used netdom resetpwd /s:Win2008 /ud:administrator /pd:* on the afflicted machine to remedy the problem.

Thank you to all for your help and suggestions.
0

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
labdunnAuthor Commented:
Solution provided by Microsoft.
0
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
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.