Misunderstanding MS KB article on Loopback Check security feature


the question [1] tells: 

  •  "in windows 2008, find tcp connections public ip e.g. 1.2.3.4 127.0.0.1:8334 fail" 

ms kb article [2] (on loopback check security feature in windows-es) explains as: 

  • "authentication fails if fqdn or the custom host header use does not match local computer  name"

 

questions (reformulating [4]):   

1)

aren't fqdns of of both 127.0.0.1 , 1.2.3.4 (of same machine) question [1] same? 


2)

don't fqdn of 1.2.3.4 match local computer name (in case of tcp connection 1.2.3.4 127.0.0.1) in question [1]?

 

3)
i'd grateful if answer questions [3] related these questions 


cited: 

  [1]

the question "windows server 2008 - connecting 127.0.0.1"  http://serverfault.com/questions/170476/windows-server-2008-connecting-to-127-0-0-1/  

 

 [2]
receive error 401.1 when browse web site uses integrated authentication , hosted on iis 5.1 or later version 

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

 

 [3]
question "on disabling loopback check security feature in windows xp pro sp3"

http://superuser.com/questions/178187/on-disabling-loopback-check-security-feature-in-windows-xp-pro-sp3

 
[4]
fqdn of localhost, 127.0.0.1, apipa , dhcp attributed ip?
http://social.technet.microsoft.com/forums/en-us/winserversecurity/thread/a03ab9b9-e550-463c-b060-5776078d4064



Windows Server  >  Security



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL