I'm sure I posted to this group yesterday but now can't see the
posting.
I used SETSPN to create a servicePrincipalName for the account I'm
using to run a web site. When I did this, IE could access the page
but VS2005 demanded but then refused to accept credentials when I
tried to open the site.
To confirm that SETSPN was the problem, I deleted the SPN using SETSPN
and the problem went back to the original problem: IE demanded but
then refused to accept credentials, VS2005 could open the web site.
Adding the SPN back went back to IE being able to access the page and
VS2005 not being able to open the website.
So, SETSPN is definitely causing the problem.
A further bit of poking around revealed that a local account on the
IIS server, which was a member of Administrators on the server, could
access the page through IE (when the SPN was deleted) and could open
the web with VS2005 (when the SPN was added).
Something about using an SPN changes network account access to the
server.
Can anyone help, please?
Microsoft Windows (other)