Definitely do not need to restart tcp or services
Part 2 - I can only say that every time I want internal users to be able to
get to a public ip within the local network, the "network" people have to do
additional entries in the router/firewall
Jim Franz
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Aaron
Bartell
Sent: Tuesday, January 19, 2016 9:03 PM
To: Midrange Systems Technical Discussion
Subject: Full loop to public IP and back
I have a machine named KT1. While on KT1 I am trying to call a web service
using its public IP - essentially calling myself by first going out to the
internet and back again. The issue is it times out. I can access the
public IP (and web service) from many other computers but not from within
the same machine (KT1). From KT1 I can access other public IPs, just not
its own public IP. I've configured the firewall to be wide open so I don't
think it's that.
I've tried adding the public IP to CFGTCP opt 1 and opt 10 (with applicable
domain) but nothing I do seems to be working.
*Questions:*
1 - Do I need to restart TCP/IP services on IBM i after making CFGTCP
changes?
2 - Is there something obvious I am missing?
Aaron Bartell
litmis.com - Services for open source on IBM i
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
