Hi Adam,
Thanks for the thought but yes we certainly have both Routers
configured to port forward to the appropriate internal IP.
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.
Any other thoughts or comments?
Thanks
Jeff
On 18/07/2006, at 1:19 AM, Adam Ernst wrote:
Do you have port forwarding enabled on *your* router? You must have
all the appropriate ports (44555 UDP/TCP, 13987 TCP) set to
redirect to the computer within your LAN that is running the
REALbasic IDE.
Adam
On Jul 17, 2006, at 10:09 AM, Jeff Ayling wrote:
I often attempt to use the Remote Debugger Stub when a remote
client is experiencing an issue but I continue to run into issues.
I now have a very important client who I would love to assist by
remote debugging but again I receive the following error.
Cannot Connect to Debugger
Location: DebuggerSupport.cpp
Failure Condition: Could not connect to the target IDE for debugging.
Failure Message: Since we could not locate the target IDE to start
a debug session, this application will now exit.
We have both configures our routers according to the ReadMe. I run
the app via the IDE - the Debugger Stub receives my request and
the file transfers to the client successfully then when the IDE
says that it is launching the app the error above occurs.
My client is behind a router and is unable to connect 'wired'
without the Router. I would really love to be able to troubleshoot
with the Stub and any suggestions would be greatly appreciated.
_______________________________________________
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>
_______________________________________________
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>
