Super User Asked by Andy Arismendi on January 3, 2022
Normally accessing a Windows share is accomplished using a UNC path e.g. \servershare where “server” is the real hostname of the Windows machine. \server.domain.comshare 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-aliasshare.
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?
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 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.
Answered by xstnc on January 3, 2022
1 Asked on December 9, 2021 by vlad-gogonea
0 Asked on December 9, 2021 by geek11
4 Asked on December 9, 2021
1 Asked on December 8, 2021 by gabriella
2 Asked on December 7, 2021 by dgo-a
1 Asked on December 7, 2021 by kbell
1 Asked on December 7, 2021 by esther-t
4 Asked on December 7, 2021 by tvc
0 Asked on December 7, 2021 by duncan-bayne
1 Asked on December 7, 2021 by alant
2 Asked on December 7, 2021 by etienne-miret
1 Asked on December 7, 2021
default settings microsoft powerpoint multiple monitors persistence
1 Asked on December 7, 2021 by wieerd
1 Asked on December 5, 2021
0 Asked on December 5, 2021
20 Asked on December 5, 2021
Get help from others!
Recent Answers
Recent Questions
© 2023 AnswerBun.com. All rights reserved. Sites we Love: PCI Database, MenuIva, UKBizDB, Menu Kuliner, Sharing RPP, SolveDir