After great hassles, I am now able to remote debug with other macs
around the world by logging off the net and completely bypassing my
router and plugging my Mac directly into my cable modem. Then I log
back onto the net directly.
My Mac Firewall is off and my client opens the correct ports on their
router.
This has worked every time I have tried.
If I attempt this without bypassing my Router remote debugging has
never worked - Even with port forwarding etc.
Cheers
Jeff
On 08/08/2006, at 12:53 PM, Peter Truskier wrote:
Replying to my own post...
I've done a bit more experimentation. After reading an archived
posting by Norman Palardy which indicated that there is a known
issue with the IDE and remote debugging on machines with multiple
NICs, I disabled all but my primary ethernet interface, and was
then able to work with the Remote Debugger Stub on my internal
network.
But, I continued to run into the same problem I described when I
tried it over the internet. Still thinking that it must be a
firewall issue, I connected my IDE machine (with internal firewall
turned off) directly to the internet, and turned off the firewall
on the remote machine (already connected directly to the net).
With no firewall on either end, the problem persists. The
connections on port 44455 seem to work fine. The IDE senses the
stubs presence, builds the executable, and transfers it. The stub
launches the debug build, which then raises the runtime error 7
because it cannot connect back to the IDE.
So my question now is a bit narrower - has ANYBODY successfully
used remote debugging from Mac to Mac over the internet?
Thanks,
Peter
On Aug 7, 2006, at 2:28 PM, Peter Truskier wrote:
I am trying to do some remote debugging over the internet. I am
using RB2006r3. Both IDE and stub side are Mac OS X - 10.4.7 on
the IDE, and Server 10.4.6 for the stub.
After configuring both firewalls/routers, I quickly got it to
connect, and transfer the compiled app to the target machine, but
as the stub attempts to launch the app, it gives a runtime error 7
- and reports that it was unable to connect back to the debugger.
I figured that this was a firewall configuration issue, and we
beat our heads against the wall for a bit, but to no avail. I then
decided to try it out locally between two machines on the same
network - no firewalls involved - and I get exactly the same result!
The remote debugger stub was downloaded today from the RS site, so
it is presumably not out of date. I notice, however, that its
creation date is 9/26/05, which seems a bit old, though perhaps not.
Is anyone successfully remote debugging from Mac to Mac with r3?
If so, what is the modification date of your stub. Mine is
1,785,161 bytes in size.
Any other suggestions or ideas?
Thanks,
--Peter
_______________________________________________
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>
