Debuggin an application on a separate computer with Labview 8

[RGreg]

I have an application that I am trying to debug on a different computer on the network.  I have verified that the app IS debuggable on my computer.  However, when it is on another computer the error I get is "No debuggable applications or runtime libraries found".  I have tried typing in the machine name and the IP address, but whenever I click on "Refresh" the error is the same. 

Both computers run WinXP, so I have also verified that a) LV8 is not blocked by the WinXP firewall on my PC and b) my app is not blocked by the WinXP firewall on the remote PC.

Any ideas on what I am missing here? 

[JeffBoettcher]

Just a couple of ideas...

You said you got "remote" debugging working on the same machine where the development system was.  When you moved over to real remote debugging, did you move your built EXE, or just try to connect to the same EXE from a different development machine?

The reason I ask is that if you moved the EXE to the other machine, make sure you move the INI with it.  The INI file contains a special line when built with remote debugging on that enables the remote debugging server.  Aside from that, you could verify the service locator is running by going to the machine running the EXE while remote debugging is problematic, launching a web browser, and going to the following URL: http://localhost:3580/dumpinfo?

If that comes back with a table of information (or at least a blank page) then that's a start.  If it gives the typical "page not found" error, that could be the cause of the problem.  You may need to re-install the run-time engine in that case.

[RGreg]

---

@Jeff B wrote:

The reason I ask is that if you moved the EXE to the other machine, make sure you move the INI with it.  The INI file contains a special line when built with remote debugging on that enables the remote debugging server.  Aside from that, you could verify the service locator is running by going to the machine running the EXE while remote debugging is problematic, launching a web browser, and going to the following URL: http://localhost:3580/dumpinfo?

================
Yes, the original INI file is there. And I tried the "localhost:3580" suggestion and did get a table of information for my application. But thanks for the ideas anyway, because neither one was something I had thought to check.

[RGreg]

As a postscript, I did get this to work finally.  Adding the executable to the exceptions list for WinXP's firewall did not cut it, but adding the PORT (number 3580) as an exception did the trick.

[JeffBoettcher]

Glad to hear it, thanks for the update.  I was a bit baffled and was hoping someone else might chime in.  I guess your comment about already thinking of firewall issues in the original post set my mind clear of asking anything about that.  Good work!