Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem with TCP/IP servers visibility in iSeries Navigator

66 views
Skip to first unread message

Jonathan Ball

unread,
Jul 26, 2009, 4:15:04 PM7/26/09
to
I have the SNTP (time mgmt) server running on some partitions on a
remote iSeries. We just moved the server to a different data center,
and now I can't manage the SNTP server configuration on any partition on
that machine using iSeries Navigator. When I click on that server in
the servers pane, i.N. locks up for a couple of minutes; doesn't matter
if it's a left click or a right click. I can click on most of the other
TCP/IP servers, and don't have that problem. I didn't have the problem
with the server was in the previous data center, and I don't have the
problem with a different multi-partitioned iSeries in another data
center. All the iSeries partitions on both servers are on the same OS
ver/rel with the same PTFs.

It sounds like a firewall issue to me, but I don't know enough about
firewalls to know what questions to ask. More indication of firewall
issues is that the iSeries partitions on the affected server can no
longer get to the IBM PTF site; when the server as in former data
center, they could.

Thanks in advance for any suggestions.

jb

unread,
Jul 27, 2009, 6:20:36 AM7/27/09
to
"Jonathan Ball" <jon...@whitehouse.not> wrote in message
news:Ic-dncvVf9bUJPHX...@earthlink.com...

The only suggestion I can make is to look at the network connections via
netstat option 3. Figure out what the 400 thinks your ip address is. Mine
thinks I am a 172.16.xx since it goes through a firewall. I call QDCRDEVD
to figure it out from a greenscreen but you might get a different address
from
Navigator. You might also share it with everyone else at your site. Now you
can posiion to this in netstat & look for connections which have not got all
the way, say SYN-SENT. Then you can get the port number. There may well
be ip logging somewhere too but I dont know of any.

--
Jonathan


iseriesflorida

unread,
Jul 27, 2009, 8:15:16 AM7/27/09
to
On Jul 27, 6:20 am, "jb" <jonathan.bai...@tesco.net> wrote:
> "Jonathan Ball" <jonb...@whitehouse.not> wrote in message
> Jonathan- Hide quoted text -
>
> - Show quoted text -

Can you ping the remote server from your new server based on the IP
address or DNS name. If you can't it could be that is the issue.

Brad

unread,
Jul 27, 2009, 6:41:02 PM7/27/09
to
Have you tried a trace route to the time server's name or IP?

call qcmd
tracreroute [timeservername]

The results will be displayed in the command shell history, if you are
happy to share, then post the results back into the thread.

Good Luck, Brad

Jonathan Ball

unread,
Jul 27, 2009, 10:25:32 PM7/27/09
to

It isn't the time server itself - it's the iSeries "server" that's
talking to it. When I expand Network in iSeries Navigator to show
Servers + TCP/IP, I see a whole slew of servers displayed: BootP, DDM,
DHCP, iSeries NetServer, etc. On most of them, if I right-click on the
server, I get a menu to start/stop the server, show the server jobs, or
display/work with the properties. When I try it on the SNTP server
entry, the display locks up. The same thing happens on QoS, ASFTomcat,
Triggered Cache Manager, HTTP Administration and IBM Directory Server.
All the rest work. It doesn't seem to matter if the server is started
or stopped.

This only started happening on this machine after it was moved from one
data center to another. On a different iSeries in a different data
center, I don't have any problem - I can right-click on every TCP/IP
server in iSeries Navigator and get the menu.

iseriesflorida

unread,
Jul 28, 2009, 8:18:33 AM7/28/09
to

Maybe a port restriction issue or nat problem.

Jonathan Ball

unread,
Aug 3, 2009, 5:17:13 PM8/3/09
to

I figured this out. For the affected partition, I had an entry in my
HOSTS table in Windows with the old address. For some reason, for the
iSeries SNTP server info in iSeries Navigator, it was using the address
from there; for other TCP/IP servers, it was using the address from the
iSeries Navigator server connection. I deleted the entry from the hosts
table, and now it works.

Thanks to everyone who responded.

0 new messages