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

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

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
techeez
Asked:
techeez
  • 4
  • 4
1 Solution
 
chakkoCommented:

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
 
techeezAuthor Commented:
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
 
chakkoCommented:
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
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

 
techeezAuthor Commented:
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
 
FarWestCommented:
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
 
techeezAuthor Commented:
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
 
chakkoCommented:
You could try to rename your domain.    

0
 
chakkoCommented:
Just did a quick search and looks like Domain Renaming is not supported in SBS
0
 
techeezAuthor Commented:
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
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.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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