Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Normally accessing a Windows share is accomplished using a UNC path e.g. \\server\share where "server" is the real hostname of the Windows machine. \\server.domain.com\share also works.

However access does not appear to work using host alias'. For example if you put this in the hostile:

192.168.1.5   server   server-alias

Both will be pingable, however share access fails using \\server-alias\share.

I'm aware SMB access uses NTLM authentication, I suppose kerberos in a domain environment. So I suspect NTLM might not support alias' like this. Is this the case?

share|improve this question
add comment

1 Answer 1

As far as I know, NTLM got a set list of host-names it will authenticate with. When just creating an alias like that, without updating it on the "server side" the auth will fail.

I found two relating articles regarding a few windows flavors :-)

Link 1 - Regarding IIS

Link 2 - Regarding access on 2003 server

As it seems both need the server-side to be updated to work, I believe you're correct in assuming this is due to the nature of NTLM.

share|improve this answer
    
The first link didn't work. I added the alias to the server host file but that didn't work. I guess host alias' are not supported by NTLM. –  Andy Arismendi Aug 6 '13 at 20:13
    
Looks like aliases are a bit unreliable when it comes to NTLM yes. The above was just a few examples, and not necessarily the -solution- you're looking for. –  xstnc Aug 8 '13 at 6:27
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.