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.
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
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.
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
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.
Maybe a port restriction issue or nat problem.
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.