On Aug 08, 2006, at 9:02 AM, Peter Truskier wrote:
Stephen,
Does that mean that you ARE able to do it over the internet through
a router?
Since my last message, I wrote a little app that can listen on a
port, or try and connect on a given port with a TCPSocket. I have
confirmed that I am able to connect from the remote machine through
my NAT router on both ports 13897 and 13987. So, I'm confused as to
what the problem is.
(I also noticed an inconsistency in a couple of the READ MEs about
the ports. One said 13897, and another said 13987, so I opened them
both. Where did you get the 1081? I tried opening that as well, and
it's still no go.)
So it seems that I am properly getting through on 44555 since the
executable is being transferred and launched, and I have proven to
myself that I can get through to my IDE machine via TCP on ports
13897 and 13987. As I mentioned yesterday, taking my router/NAT out
of the configuration on the IDE end still doesn't seem to get it to
work.
I have used a port sniffer on the IDE end, and it gets no packets
on 13897 or 13987 when the remote stub launches the debug app, and
then errors out.
I'm about to give up and install RB on the remote end and use ARD
to control it. Any other suggestions? Aaron?
Thanks one and all,
Peter
The problem is likely that the application that has been sent to the
remote machine has an IP address in it to connect back to that is not
reachable.
That was sort of the problem in my case.
_______________________________________________
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>
