Can you put a sniffer on the remote network and check that way in order to confirm your suspicion?
On 7/17/06, Jeff Ayling <[EMAIL PROTECTED]> wrote:
I think that the debugger should provide an error log or onscreen message to inform the user that 'The debugger failed to connect with the target IDE (203.1.2.3:44555) for debugging. At least this way it would be possible to see where the stub is attempting to connect. I realize that I may be well off the mark here but my 'thought' is that the IDE sends the data to the stub and includes the ip address for the stub to connect back to the IDE - if the IDE computer is behind a router and has an internal ip address then it is this internal address that gets sent to the stub - then the stub attempts to connect back to the internal ip address which of course does not exist on that network so it fails. I'd love to be proved wrong by seeing the ip address which the stub is attempting to communicate with when this error occurs.
_______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
