Can you tell us whats there in IIS logs for this whole thing. Or just copy paste the whole communication frm the iis logs..
Main Topics
Browse All TopicsI have a SonicWall SSL-VPN 2000 hardware VPN box that users use to connect to a 2003 Server. The server hosts e-mail, files, and Sharepoint. You can create links to internal web services and it passes the credentials to the resource. When I follow a link to the sharepoint intranet site, I get the following error:
TTP/1.1 401 Unauthorized Content-Length: 1656 Content-Type: text/html Server: Microsoft-IIS/6.0 WWW-Authenticate: Negotiate WWW-Authenticate: NTLM WWW-Authenticate: Basic realm="server.nwi.local" X-Powered-By: ASP.NET MicrosoftSharePointTeamSer
You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.
I assume it's something to do with how the device is passing the credentials to the web server. What settings would I need to change on the IIS site to allow it to accept WWW-Authenticate headers?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
This is over https. Authentication works perfectly when accessing it directly or over VPN. This issue only surfaces when the VPN hardware device tries to authenticate on behalf of the client. It may be an issue with trusted delegation. Basic authentication and integrated windows authentication is enabled. I'll post the IIS logs shortly.
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2006-06-18 17:58:36
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2006-06-18 17:58:36 192.168.1.2 GET /_vti_bin/owssvr.dll - 443 - 192.168.1.4 Mozilla/4.0+(compatible;+M
2006-06-18 18:04:08 192.168.1.2 GET /_vti_bin/owssvr.dll - 443 - 192.168.1.4 Mozilla/4.0+(compatible;+M
Here are two separate attempts to connect via the VPN box.
>This is over https. Authentication works perfectly when accessing it directly or over VPN. This issue only surfaces when >the VPN hardware device tries to authenticate on behalf of the client
I think that you need to be looking at the configuration of the VPN Hardware rather than the client/server? VPN hardware is supposed to be (as neart as dammit!) transparent!
Business Accounts
Answer for Membership
by: pjedmondPosted on 2006-06-15 at 13:38:53ID: 16915481
http://www.microsoft.com/w indows2000 /en/server /iis/htm/c ore/ iiauth s.htm#enab lebasic
ns/jlima/j oelima2.ht ml
Bear in mind that basic authentication *IS NOT* considered to be secure unless done over https. It is the simplest method of authentication, and as such virtually every browser supports it.
If you want to understand more about how it all works, then:
http://old.owasp.org/colum
will give you a good overview.
HTH:)