If your PC is acting as a router by forwarding traffic, then your 400 is accessible from the internet.
In my case, it wasn't the PC but a dedicated firewall/router performing NAT. I'd give iPTF the IP address of the router, and the router would then do the address translation to the 400's internal IP.
Everything worked fine on the initial connection from iPTF to the 400, but then came to a screeching halt because the 400 randomly assigns port numbers for use by iPTF. Since they're randomly assigned, it was almost certain that the 400 would pick a port number that was blocked by default on the firewall. Of course, opening up all ports on the firewall resolved the issue, but for obvious reasons, that wasn't practical.
In the end, the iPTF support person who was helping me determined that there was no way of doing this through the firewall, and part of his explanation revolved around this issue of the 400 needing to be accessible from the internet.
> -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Justin C. Haase > Sent: Monday, June 09, 2003 2:48 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE: internet PTF service > > > Not meaning to be picky or start a war here, but if your 400 > has an internal (reserved/non-routable - eg 10.x.x.x or > 192.168.x.x) address, how does that get routed over the > internet? It doesn't. It goes through your PC as an intermediary. > > No 400 I've ever used iPTF on has had access to the internet. > My PC did. The 400 did not. > > jch >
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact