I can connect through the http://<servername>:<port>/VaultService only after I am prompted for a windows login for the server I am on. Once logged in, I can view everything the troubleshooting site says I should. The problem is that the client and the admin do not prompt for the windows login, leading me to believe that I missed a configuration somewhere.
I installed Vault to use the Network Service and have confirmed that the related directory permissions have been modified by the install script. I have stepped through the information from your support site without success. More than likely, I am missing a permission setting somewhere.
I have windows server 2003 with asp 2.x.
Vault installed but no connection through client
Moderator: SourceGear
Vault installed but no connection through client
lost...but making good time.
I received your email yesterday as well. Did you receive mine asking for more details? Also, are you saying you can't connect via the GUI or that you are concerned about not having to login into the server? If you didn't receive the email, just let me know.
Can you go ahead and send me a Vault Server Log and a Client Side Log.
Can you go ahead and send me a Vault Server Log and a Client Side Log.
This is a follow-up to troubleshooting that was done off-line. I am just including text from our last two emails here for documentation.
I suggested:
In the IIS Admin tool, is anonymous access enabled for the Vault
website?
I spoke with a co-worker who had a similar thing going on with several
previous users, and in their case the IUSR account had issues. Things
that you could check with that is:
--- IUSR has anonymous security rights in IIS - Vault Service
---IUSR has as account that can log into that server
---IUSR passwords between where it is configured in IIS and for the
server machine match
---IUSR password has not expired.
User responded:
To sum up what was wrong:
The IUSR account did not have a password associated with it. It had been
removed while testing connections because I did not know what the
existing password was.
However, accounts with blank passwords can not navigate our network due
to a restriction. I entered a new password and matched the one in IIS to
it, et voila: I have access. One way to test this is to attempt to log
in using the IUSR account. If it fails, the error message may very well
indicate the problem (it did for me: Cannot log in account due to
restriction).
Lastly, perhaps you could include some note in the support forums that
indicates that, even if you must use a different port (SharePoint or
whatever), it is not necessary to change the proxy settings. At least,
that's how I read them.
I suggested:
In the IIS Admin tool, is anonymous access enabled for the Vault
website?
I spoke with a co-worker who had a similar thing going on with several
previous users, and in their case the IUSR account had issues. Things
that you could check with that is:
--- IUSR has anonymous security rights in IIS - Vault Service
---IUSR has as account that can log into that server
---IUSR passwords between where it is configured in IIS and for the
server machine match
---IUSR password has not expired.
User responded:
To sum up what was wrong:
The IUSR account did not have a password associated with it. It had been
removed while testing connections because I did not know what the
existing password was.
However, accounts with blank passwords can not navigate our network due
to a restriction. I entered a new password and matched the one in IIS to
it, et voila: I have access. One way to test this is to attempt to log
in using the IUSR account. If it fails, the error message may very well
indicate the problem (it did for me: Cannot log in account due to
restriction).
Lastly, perhaps you could include some note in the support forums that
indicates that, even if you must use a different port (SharePoint or
whatever), it is not necessary to change the proxy settings. At least,
that's how I read them.