Skip to Content
author's profile photo
Former Member

Ping fails for REST-Receiver Channel

We are trying to use a XS-Service provided by a HANA-System via the REST-Adapter.

Our Landscape has 4 stages DEV – QA1 – QA2 – PROD

This works flawlessly in DEV, QA1 and QA2. The development has now been transported into the production system, waiting to be used.

In Production, we encounter a ping-fail in the Communication-Channel-Monitoring of the Production-PO. All tests we have done so far, indicate, this is a false positive.

Our network setup is:

Every HANA-host has a name/ip-address in the company-wide network, like this:

DEV and QA1:, Port 8070

QA2:, Port 8090

PROD:, Port 8070

Yes, DEV, QA1 and QA2 are sharing the same host and yes DEV and QA1 are using the same HANA instance on that host.

All hosts are also connected, on a private network (IP-Address range 192.168..) for faster internal communications.

The servers have different names there

DEV and QA1: saphfe1d.private.domain, Port 8070

QA2: saphfi1d.private.domain, Port 8090

PROD: saphfp1d.private.domain, Port 8070

Name resolution is done via DNS-Entries in the companies DNS-Servers and known to work.

Pinging the rest-channel in the PO, gives us an error 500 for HTTP HEAD and HTTP OPTIONS.

The URL in the channel is triple-checked and valid.

Accessing the rest-Service-url via a Webbrowser (and Company-domain-Servername) does work.

Accessing the rest-Service-url for HTTP HEAD and HTTP OPTIONS via telnet from the servers within the private-domain does also work. Unfortunately we don't have a Webbrowser on any of the servers in that private.domain.

How can I dtermine what is wrong with the ping.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

0 Answers