CODEWITHSUNDEEP
.netremote-debugging
Matt Dawdy
Matt Dawdy

Reputation: 19717

VS Remote Debugging

I'm very unfamiliar with traditional debugging, but we are having an issue on a production server and it would come in very handy right now, but I can't even get VS to connect to the remote machine and show any processes.

I've installed the remote debugging tools from MS. The remote computer is one that I have VPN connection to (I can browse to \172.25.250.66\c$ from windows explorer -- I am not sure, but I thought this meant that I was on the same network as the remote machine, but maybe I'm wrong).

Debug -> Attach Process, even if I choose Remote (no authentication) I can't see any other computers besides my own.

Upvotes: 0

Views: 287

Answers (1)

tehlexx
tehlexx

Reputation: 2859

Remote (no authentication) won't work for managed debugging.

You'll need to use Default transport. For that you will need the same users (and I believe also the same passwords) on both your computer where you are debugging and on the remote machine. On your computer, the Visual Studio process must run as that user, and of course on the remote machine the remote debugging process as well.

Upvotes: 1

Related Questions