Solved

netbios alias in windows 2008 is 'viewable' but when connecting it asks for and won't accept authentication

Posted on 2011-09-10
11
990 Views
Last Modified: 2012-05-12
We have just installed a Windows 2011 SBS to replace a seriously old Windows 2000 server.  We did not migrate anything we simply created a new domain and moved workstations into and out of the respective domains and also completely recreated the shares and copied files over via robocopy.

The problem is that they have literally hundred ofs  files with hyper links to '\\oldserver\share\file' and we called the new server a different name.

We've added the DisableStrictNameChecking reg key and added the alias with netdom computername oldname /Add:newname which has correctly created the alias which shows up in the registry under optionalnames correctly and then is also browsable on the network.  The issue is that when you actually try to connect to the share it asks for authentication and won't accept any valid credentials...

Any help greatly appreciated.
0
Comment
Question by:techeez
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
11 Comments
 
LVL 22

Expert Comment

by:chakko
ID: 36517869

I have only read about using ALIAS Netbios names, but never tried it, so I can't offer any help with that.

As An alternative, have you thought about using a DNS 'alias' instead?  create a new DNS record of OLDSERVER which resolves to the new server IP address?
0
 
LVL 1

Author Comment

by:techeez
ID: 36517873
Yep created that as well... It resolves properly and you can actually 'browse' the resources ala:
net view aliasname
and it shows the network shares properly... but you can't connect to them.  It asks for credentials and doesn't accept any  valid username/passwords from within the domain.

Thanks.
0
 
LVL 22

Expert Comment

by:chakko
ID: 36517919
Again,  I never actually tried what you are doing, but I found this.  

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


and this (at the bottom it has another step to adjust the SPN)

http://support.microsoft.com/?id=281308

0
Salesforce Has Never Been Easier

Improve and reinforce salesforce training & adoption using WalkMe's digital adoption platform. Start saving on costly employee training by creating fast intuitive Walk-Thrus for Salesforce. Claim your Free Account Now

 
LVL 1

Author Comment

by:techeez
ID: 36518592
Thanks but the first one doesn't fit this circumstance, and the second one I used and followed earlier to no avail.

Just spent 6 hours on the phone with 2 engineers from Microsoft and they were stumped... Waiting to hear back from the 'core network team' now.
0
 
LVL 12

Expert Comment

by:FarWest
ID: 36518651
What happend when you try to access the share using FQDN eg \\yourdomain.com\share\file1?
and what happend when you use the IP eg \\192.168.1.1\share\file1?
if both also do not accept credintals I think the reason can be :
either share ACL is missing, so users and thier rights are not migrated correctly OR if the server is not the DC it is not a member of the domain OR it belongs to another domain and you need to verify the name or the trust relationship
0
 
LVL 1

Author Comment

by:techeez
ID: 36519394
It turns out that it won't work because the alias that we are trying to use also happens to be the same as the netbios domain name.
0
 
LVL 22

Expert Comment

by:chakko
ID: 36520439
You could try to rename your domain.    

0
 
LVL 22

Expert Comment

by:chakko
ID: 36520515
Just did a quick search and looks like Domain Renaming is not supported in SBS
0
 
LVL 1

Accepted Solution

by:
techeez earned 0 total points
ID: 36520545
Yes... Thanks though. Once you install the OS and specify the server name and domain name neither can be changed.

We had to actually wipe the Server and reinstall :(

Thanks for all the help
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

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

I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
Suggested Courses

628 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