Windows Safari cannot access the server by NetBIOS / WINS name

Whenever I try to access an authenticated NTLM intranet site, Safari takes forever processing and then returns with "Destructive Not Available" or, if allowed by the site, loads without authentication. I can access these same sites without issue in Firefox and Internet Explorer. The sites are hosted on IIS6 and are generated using either ASP, ASP.Net 1.1 or ASP.Net 2.0.

Any insight as to why Safari is choking on these sites? Are there any problems to get NTLM to authenticate properly with Safari?


Update:

Upon further playing with it, I determined that NTLM would work (on page load fast enough) if I use the fully qualified domain name for the site (i.e. http: // mysite doesn't work, but http: //mysite.domain. prv will work). Unfortunately this won't work due to other project constraints.

Does anyone know why the FQDN will work, but the shorter name won't? Is it something that can be bypassed or is it "Sorry to be lucky"?


Update 2:

According to Wifferhark, the safari packet sniffer sends a SYN to the correct IP address. The intranet sergeant replies with a SYN, ACK, to which the safari sends an ACK. This is the end of the communication between safari and gray. When trying to access an intranet site using the FQDN, the three packages were the same, but then an HTTP GET request followed, which then loaded the page successfully.

Since Safari is connecting to the correct IP address, I find it hard to believe that Safari simply doesn't support NetBIOS / WINS names. Also, since NTLM packets are never exchanged, since safari never sends the original GET request, I'm pretty sure NTLM has nothing to do with this problem.

Does anyone know the status of Safari NetBIOS / WINS support?

0


source to share


3 answers


In a similar situation with a Java based client I was able to use http://ntlmaps.sourceforge.net/ to traverse the proxy.



0


source


Any insight as to why Safari is choking on these sites?

Because NTLM is not a web standard. You cannot expect this web browser to support it.



Until recently, only IE supported it at all. And Firefox support needs to be specially configured.

0


source


Firefox could always go through NTLM sites. I know because I am stuck with this horrible custom ASP solution and SharePoint site to use on our intranet ... Firefox is a dream come true.

Apple .. fix Safari kthank you?

0


source







All Articles