Visual Studio 2005 - 远程调试连接问题？
我试图在用于 ASP.Net 2.0 开发的 Windows 2003 服务器上再次进行远程调试。我把一切都准备好并运行了几个月，然后有一天，我们的 AD 策略迫使我更改密码，从那以后远程调试就不起作用了。
我有一台虚拟运行的 Windows 2003 服务器 (MS Virtual PC 2007)，该服务器与我运行 Visual Studio 2005 IDE (Windows XP Pro) 的系统相同。两个系统都是同一域的成员，我的域帐户位于两个系统的管理员组中。我使用此域帐户登录到运行 Visual Studio 的 XP 计算机和运行调试控制台的 Windows 服务器。
当我尝试从 VS 内连接到远程调试器时，大约 1 分钟后出现错误...“无法连接到 Microsoft Visual Studio 远程调试监视器和‘myServer’。由于超时时间已过，该操作返回。”
从 VS 附加时，我仅使用了服务器名称以及控制台中列出的完整调试服务器实例名称 (Domain\user@myServer)，但我得到了相同的结果。我还尝试使用我的域帐户将控制台作为服务运行（这是我设置它的原始方式），并从运行 VS 的 XP PC 上共享......再次得到相同的结果。我还检查了调试控制台上的权限，管理组和我的域帐户均已列出，并且调试设置为“允许”。
当我尝试从 VS 内连接到调试器时，我可以在服务器的远程调试控制台上看到连接弹出窗口，它表示已连接，但我注意到它正在尝试以与我登录的用户不同的用户身份进行连接机作为。调试控制台显示连接属于本地帐户 (myServer\user1)…我希望看到域\用户。调试控制台中显示的本地帐户确实存在于两个系统上，并且位于每个系统上的本地管理组中，但我不知道为什么它会突然尝试使用该帐户而不是我正在使用的域帐户在两个系统上均已登录。
正如我所提到的，一切都工作了几个月，直到 AD 帐户密码更改后才似乎停止工作。
有谁对可能导致此问题的原因有任何想法吗？
任何帮助将不胜感激。
谢谢！
I’m trying to get remote debugging working again on a Windows 2003 server that I use for ASP.Net 2.0 development. I had everything up and running for months then one day, I was forced by our AD policy to change my password and the remote debugging has not worked since.
I have a Windows 2003 server running virtually (MS Virtual PC 2007) on the same system that I run my Visual Studio 2005 IDE from (Windows XP Pro). Both systems are members of the same domain and my domain account is in the admin group of both systems. I’m logged into the XP machine running Visual Studio and the Windows server running the Debug Console using this domain account.
When I try to attach to the remote debugger from within VS I get an error after about 1 minute… “Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor and ‘myServer’. This operation returned because the timeout period expired.”
When attaching from VS, I have used just the server name as well as the full debug server instance name (Domain\user@myServer) that is listed in the console but I get the same results. I have also tried running the console as a service using my domain account (this is the original way I had it setup) and from a share on the XP PC running VS….again same results. I also checked the permissions on the Debug Console and both the admin group as well as my domain account are listed and Debug is set to “Allow” for both.
When I try to attach to the debugger from within VS I can see the connection popup on the Remote Debug Console of the server and it says it’s connected but I noticed that it’s trying to connect as a different user than what I’m logged into either machine as. The debug console shows the connection belongs to a local account (myServer\user1)… I would expect to see Domain\User. The local account that shows in the debug console does exist locally on both systems and is in the local admin group on each system but I have no idea why it would all of a sudden try to use that account rather than the domain account I’m logged in as on both systems.
As I mentioned, everything was working for months and only seem to stop functioning after the AD account password was changed.
Does anyone have any ideas on what could be causing this issue?
Any help would be greatly appreciated.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我想我会更新这个问题，以防其他人遇到类似的问题。
在我为这个问题绞尽脑汁几天后，我决定尝试在新工作站上安装 VS 2005。我能够毫无问题地连接到我的开发服务器的远程调试进程。
我仍然不能 100% 确定问题的实际原因是什么，但我认为它与 2 个不同的问题有关。一旦我能够从新工作站进行远程调试，我决定在遇到问题的工作站上重置 VS 环境设置。我不知道为什么我没有早点尝试这个……但这似乎已经解决了问题，并且远程调试现在可以在我遇到问题的系统上进行。
错误用户的问题是由于缓存的登录帐户被使用而不是当前登录的域用户的帐户所致。我在运行 VS 的工作站上运行“%windir%\system32\rundll32.exe keymgr.dll, KRShowKeyMgr”，找到有问题的本地帐户，将其从“存储的用户名和密码”框中删除，然后在远程调试器上使用我的域帐户应该如此。
I thought I would put an update to this question in case someone else runs into a similar issue.
Well after pulling my hair out on this issue for a couple days now, I decided to try installing VS 2005 on a new workstation. I was able to connect to the remote debug process of my dev server without any problems.
I’m still not 100% sure what the actually cause of the problem was but I thnk it was related to 2 different issues. Once I was able to get the remote debugging working from the new workstation I decided to reset the VS Environmental settings on the one I was having issue with. I’m not sure why I did not try this sooner …but this seems to have taken care of the problem and remote debugging now works from the system I was having problems with.
The issue of the wrong user was due to a cached login account being used over that of the currently logged in domain user. I ran "%windir%\system32\rundll32.exe keymgr.dll, KRShowKeyMgr" on the workstation running VS, found the local account in question, deleted it from the Stored User Names and Passwords box and from that point on the remote debugger used my domain account as it should.