Cannot Access Remote System from iSeries Using System Name

 

Problem

You cannot access a remote system from the iSeries by using the remote system's host name.

Solution

For information on IP addresses, system host names, and DNS servers, see:

• Understanding DNS Servers, IP Addresses and Host Names.
• IBM InfoCenter's section on TCP/IP troubleshooting.

Do the following in order to determine what is causing the issue and resolve it:

1. From the iSeries, ping the system's host name, where SYSTEM_NAME is the host name:

   PING RMTSYS('SYSTEM_NAME')

   If you can ping the host name, try your original program again.

2. If step 1 doesn't resolve the issue, ping the IP address directly:

   1. Find the IP address of the remote system you are trying to access.

   2. On the iSeries, run the following, where 1.1.1.1 is the IP address:

      PING RMTSYS('1.1.1.1')

      • If you cannot ping the IP address, there is a problem with the remote system. Make sure that the system is running, is on the network, and can see the iSeries. If not, you will need to resolve the networking issues on that PC first.

      • If you can ping the IP address, continue to step 3.

3. Check for changes to the DNS server. If the IP address changed for the DNS server or the network was reconfigured to add additional DNS servers, you need to change the settings on the iSeries manually:

   1. On the iSeries, type CHGTCPDMN and press F4.

   2. In Change TCP/IP Domain, in Domain name server and Internet address, make sure that the IP addresses for your DNS servers are listed in the order that you want them checked. The topmost listing is checked first.

      For example:

      Domain name server:
      Internet address . . . . '1.1.1.1'
          '1.1.1.2'

   3. Set Host name search priority to *REMOTE.

      The iSeries now checks network DNS servers before the internal DNS listings in Host Table Entries. If you choose *LOCAL, it may still work but can take much longer.

   4. Try your original program again.

4. If the issue still isn't resolved, bypass the DNS servers by setting up an entry for the remote system in Host Table Entries:

   Note: Even if you don't need this option to resolve the issue, you may still want to set up one or more aliases for a remote system if that system causes more connectivity issues than others.

   1. On the iSeries, run the following:

      CFGTCP

   2. In Configure TCP/IP, choose 10. Work with TCP/IP host table entries.

      Work with TCP/IP Host Table Entries displays.

   3. If an entry for your remote system already exists, make sure that the information is correct:

      1. If the host name is incorrect, edit it.

      2. If the IP address is incorrect, you need to create a new entry.

   4. To create a new entry:

      1. In Work with TCP/IP Host Table Entries, in the blank entry at the top of the page, in Opt, type 1 and, in Internet Address, type the IP address of the remote system.

      2. Press Enter.

      3. Enter one or more Host Names, depending upon how you wish to use this entry.

         Note: Only one host name is required. RJS Software recommends that at least one matches the host name on the remote system.

   5. On the iSeries, type CHGTCPDMN and press F4.

   6. Set Host name search priority to *LOCAL.

      The iSeries now checks Host Table Entries before network DNS servers. If you choose *NETWORK, it may still work but can take much longer.