I need to debug some C# code on a remote machine running XP Embedded. I did remote debugging on several occasions on different Windows operating systems and all worked well, but I think that the XP Embedded OS is missing something.
I'm popping my brains out in the last couple of days, reading and trying stuff, but nothing seems to work. So if you have been in the same situation and found a solution, please help. Here is what I did up to now:
Successfully established a remote debugging connection to an XP Professional environment, so I know that there's nothing wrong with my remote configuration.
Started the same services on the Embedded environment that are running on the Professional environment.
Configured DCOM permissions, firewall, local users with same name and passwords on both local and remote machines. Gave local users administrator rights.
Started msvsmon.exe both as an application and as a service, under the local user account, wich also has log on as a service rights.
Triple-checked that there is no other firewall between the machines that could drop remote debugging packets.
If I use the No authentication (native only) mode on the Embedded machine, the remote debugging works and I can see the processes. Otherwise, I get an error:
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named '[NAME]'. The debugger cannot connect to the remote computer. This may
be because the remote computer does not exist or a firewall may
be preventing communication to the remote computer. Please see
Help for assistance.
Thank you for the time you took to read this and any suggestion may help. Thanks!
Can you use WireShark to capture the data going to the remote XP embedded device? If you get a TCP acknowledgement, at least you'll know it's not a firewall problem.
Did you tried to start msvsmon.exe with admistrator rights ? Maybe that is the issue, a post by John Robbins explains it : http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/06/15/vs-remote-debugging-across-workgroups-or-domains.aspx.
Related
We recently moved from a Windows 2003 server to Windows 2008 R2 server and now I see that all my psexec jobs fail.
thsi is how they are coded to run:
c:\shell\psexec.exe \NTDB2UT02 -u conseco\plat -i cmd.exe
I then get prompted for a password and as soon as I enter the password I get the error message below
PsExec v1.31 - execute processes remotely
Copyright (C) 2001-2002 Mark Russinovich
www.sysinternals.com
Password:
Could not start PsExec service on NTDB2UT02:
The system cannot find the file specified.
So I went back to the Windows 2003 server that we were using earlier and I know it worked there because I have proof that it ran, and now I get the same message from the old Windows 2003 server too.
I read on a few posts that I could use the cmdkey to add a cached credential and I even tried doing that on both servers, but it didnt help at all.
I am going to try using a newer version of psexec, but I doubt that this will change anything at all.
Any tips or if anyone has successfully figured out a solution to this (or even a workaround), sharing that will be greatly appreciated.
thanks,
Mike
I have struggled with this on 2003 server and found that when I turned off firewall everything worked, then when turning firewall back on it didn't. I found the problem under firewall exceptions "File and Printer Sharing". When you go to edit the service, there are 4 entries, and when you check the scope they are set for your network subnet only. My problem was/is that we use multiple subnets and this machine did not match to the other machines trying to access it. If you find this is also your problem, and not the admin$ share issue (you can search against that), update the network subnets in a custom list (or if you're daring to attacks, allow any computer - bad idea). You only need to update ports 139 and 445 Hope this helps someone.
So here's my setup: Visual Studio/Microsoft Test Manager (2012) running on Windows Server 2008 (running on a virtual machine), trying to connect to another VM running Windows 8 (not 8.1). The issue is that in Lab Manager, it says that my Win 8 VM is in a "Ready" status, but when I go to connect, it says "Microsoft Environment Viewer could not connect to the machine..." I have looked for this error and nothing that I can find applies to this error. I get a somewhat generic "how to" doc from MS in most of my searching, but it's not helping me here. The interesting thing about it is that I can connect via the remote desktop option...So I don't know where to go from here. If it's a firewall issue, I don't know what to look for exactly. There may be some detail I've missed, but I don't know what it could be...help?
Thank you!
Aha! I have found the answer, and it is here. Basically, you have to reduce somewhat the security of your environment to allow RDP Clients that aren't the same version as the host OS expects to run.
I have been messing with remote debugging so finally out of despair here I am. I am trying to connect to a Win 2003 remote machine where I have remote debugging installed (NO VS installed on this machine.) following this tutorial. So, I have added all the ports to exceptions in the firewall and I am trying to connect from my visual studio 2010 (run as administrator) and windows 7 Home Premium local machine using No authentication method by attaching it to a process. (For some reason I cannot use windows authentication and gives me edition not supported error!)
What happens is on the debug monitor it says that User has connected but then it just sits there waiting and finally gives an error Unable to connect to xxx.xxx.xxx.xxx. The remote machine is not responding. I tried to research a lot and also created a user with the same name as on the local machine on the remote machine. Also I used telnet as mentioned in the link and it does not show connected to the remote system message but does not show that it failed either and just sits there. I am guessing it something to do with the port not open correctly.Also after the first connection attempt when I try to connect again the remote debug monitor does not show any connected message and also the error I get is that remote debug monitor is not setup or running on the machine (almost like the debugger stops reponding). I am pretty exhausted trying out all the options can anyone give me more direction here ? Thanks !
Hey everyone, I'm having trouble configuring my remote debugging set up. I've been searching and reading for a while, but I can't figure it out. I'm running windows 7 as the pc I'm running VS on and then have windows 7 running in virtual box as the pc that is running the program I'm trying to debug. I'm trying to debug a .NET 4 project.
Both computers are not part of a domain (I'm not sure if that matters). I'm running the debug monitor on the virtual pc via a shared folder on the non-virtual pc.
When I try to connect to the remote pc in the attach to process window in VS it connects, but fails to launch, and I get an error that says
Error while trying to run project: Unable to start debugging.
The specified network name is no longer available.
Let me know if I need to say anything else about my set-up.
Thanks for the help!
I finally figured out my problem(s).
I was using the wrong PC name to connect to the host machine. I was using the Server name that you can type in the VS remote debugging monitor. I had it working when I did the server as 'Stephen#192.168...' where that was the actual ip address on my subnet
Windows didn't properly configure the firewall ports for me. I had to manually open the DCOM ports to get it connecting.
I had to clear the existing credentials for each machine once everything else was set up as is shown here http://msdn.microsoft.com/en-us/library/2dbesfyx.aspx
Thanks everyone for your help and pointers.
I've read all related remote debug entries here and couldn't find an answer to my problem. I've trying to setup remote debugging to test a console app.
Dev Machine - Vista, VS 2008
Remote Machine - Win 2008
I've followed the steps in this article to configure it and I'm stuck with the following error when I try to list processes in remote machine under 'Attach to Process'.
"The remote procedure call failed and did not execute".
But in my remote machines 'Remote Debug Monitor' I see that the dev machine connection was established.
Can anyone provide me with any clues?
Whenever I run into this problem the first thing I do is disable the firewall on both computers. Firewall problems are the most common issue I run into with remote debugging and it's best to eliminate that problem from the start.
Do take care to turn the firewall back on when you're done diagnosing the problem :).