域账号更改密码之后代理需要重新配置

在使用域账号的时候，如果需要配置账户和密码，那么最好记录下来，否则将来找不到就很尴尬了。

我遇到的问题是，因为在另外一台电脑配置了域账号，用来联网，提供网络给visual studio

1.Firefox

这个代理的账号需要附加域名

2.Chrome

3.NuGet代理

C:\Users\clu\AppData\Roaming\NuGet\NuGet.Config 这个地方配置的代理不需要指定账号和密码

4.npm代理

【应该是无需配置代理，会自动使用ie的代理。某一个ip连不上的时候，会自动切换到其他的ip】

C:\Users\clu\.npmrc 这个地方配置的代理似乎需要指定账号和密码

PS C:\Users\clu\Desktop> npm install --save-dev jasmine
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/jasmine failed, reason: connect ETIMEDOUT 104.18.96.96:443
npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
npm WARN Desktop No description
npm WARN Desktop No repository field.
npm WARN Desktop No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

+ jasmine@3.1.0
updated 1 package in 273.624s

5.git代理

在windows credential manager中修改

6.可以检查用户目录下的所有配置文件

.git-credentials

7.windows service中使用了代理，最后一列logon as

8.清空credential manager中所有相关的账户和密码

9.TortoiseSvn可能有配置

svn代理设置无效?

可以直接去后台修改C:\Users\clu\.subversion文件夹下的servers文件，这个是全局的配置

但是TortoiseSvn中的设置是关联到C:\Users\clu\AppData\Roaming\Subversion下的servers文件

The Security System detected an authentication error for the server LDAP/SASYGSHADC01.asnet.xxx.net/asnet.xxx.net@ASNET.xxx.NET. The failure code from authentication protocol Kerberos was "The user account has been automatically locked because too many invalid logon attempts or password change attempts have been requested.
(0xc0000234)".

eventlog对应的source是LSA(LSASrv)

https://social.technet.microsoft.com/Forums/ie/en-US/cf9ca750-d624-468a-8e0b-239fb561a0bd/event-source-is-lsasrc-and-event-id-is-x-40960?forum=winserverDS

Use the Account Lockout tools (http://www.microsoft.com/en-us/download/details.aspx?id=18465) to identify the source of the lockouts.

Once you have found the machines, disconnect them from the network and monitor if account lockouts still occur.

More information:

Account Lockout Tools
http://technet.microsoft.com/en-us/library/cc738772(WS.10).aspx