Unable to open port

Santosh Kumar 20 Reputation points
2026-07-07T03:40:12.99+00:00

Hi

I am running into a connection time between the systems, though the NSG inbound rules & outbound rules are in place for the port 3299, where external SAP backbone systems connect to SAP router hosted on Azure.

[Thr 88780] Tue Jul 07 05:36:50 2026 [Thr 88780] *** ERROR => mainU: NiBufConnect (rc=-5) [saprcchk.cpp 1236] [Thr 88780] [Thr 88780] ***************************************************************************** [Thr 88780] * [Thr 88780] * ERROR timeout occured [Thr 88780] * [Thr 88780] * TIME Tue Jul 07 05:36:50 2026 [Thr 88780] * RELEASE 753 [Thr 88780] * COMPONENT NI (network interface) [Thr 88780] * VERSION 40 [Thr 88780] * RC -5 [Thr 88780] * MODULE D:/depot/bas/753_REL/src/base/ni/nibuf.cpp [Thr 88780] * LINE 4730 [Thr 88780] * DETAIL NiBufIConnect: route connect

Please advise

Azure Firewall
Azure Firewall

An Azure network security service that is used to protect Azure Virtual Network resources.


1 answer

Sort by: Oldest
  1. Alex Burlachenko 25,120 Reputation points MVP Volunteer Moderator
    2026-07-07T08:39:14.5366667+00:00

    Hi Santosh Kumar & thx for join me here at Q&A portal,

    port 3299 is only one part of it. A timeout means the traffic is being dropped somewhere, not refused by SAProuter.

    Check the full path NSG allows inbound to the SAProuter VM NIC/subnet, Azure Firewall allows inbound DNAT / network rule if traffic passes through it, VM OS firewall allows TCP 3299, SAProuter is actually listening on 0.0.0.0:3299 or the right private IP, UDR/routing sends return traffic back the same way, No NVA/firewall is blocking outbound return traffic. From the SAProuter VM, run

    netstat -ano | findstr 3299

    From another machine, test

    Test-NetConnection <saprouter-public-ip-or-dns> -Port 3299

    If Azure Firewall is in the path, check Firewall logs. That will tell u if the traffic is denied or not even reaching it.

    If NSG rules are correct but the timeout stays, my bet would be routing, Azure Firewall DNAT/rules, or the service not listening. NSG gets blamed a lot, but it’s not always the villain.

    rgds,

    Alex &

    pls if my answer was helpfull mark it as an answer & follow me here and at my blog https://ctrlaltdel.blog/

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.