SAP Note 25941 - SAP System does not find host name of

Symptom:

Output requests receive the status "Error." The error message in the syslog is "FA6: Attempted to connect to the host ... Failed, as the gethostbyname(3) for this host was not recognized", such as:
"Name of destination host unknown".

Other terms

NILIB, gethostbyname, SAPLPD, telnet, ping, hosts, print, SAPSprint

Reason and Prerequisites

The C-library functions gethostbyname or NiHostToAdr called by R/3 fail.
Unfortunately, the same error message is returned in both cases.

Solution

Carry out the following tests:

1. Are there incorrect entries for this host in the THOST ?

2. Does ping work (under user adm)?

3. Does the command telnet 515/tcp work (user adm)?

If a connection is set up after transmission of this command, you can use 4 x 1 to test whether you can reach SAPLPD. This should then return its version number and close the connection.

4. If one of these actions fails, the corresponding measures must be taken in your network environment - there is no error in the SAP System. Usual errors are, for example, missing entries in the file /etc/hosts. or the user adm has no read rights to the entries.

5. Does an nslookup with the host name function?

If this program fails, you have to contact your network administrator.

6. To test the Nilib function NiHostToAdr, logon as user adm and run the command "niping -t -H ". If the function NiHostToAdr returns a value <> 0, try if an NI reset in the definition of the output device using transaction SPAD solves the problem.

7. Use more SUBDOMAINS ? -- for example, the editing computer is named host1.xx.yy.zz; the router on which SAPLPD is running is called host2.uu.vv.ww. Call Transaction SM55 and enter the following alias:

host2 host2.uu.vv.ww

The host computer will still be named host2 in transaction SPAD. This can solve the probelm, but if it does not, you need to examine the configuation of your domain name server.

Have you made changes to the host files or were PC addresses allocated dynamically? If so, reboot the application server running the spool work process in question.