SAPRouter issue telent end withs timeout error

Question

Hi Friends,
We have changed Public and Private IP of our SAP Router same has been updated to SAP and SAP replied and they have also updated there records.
When I am doing telent saprouter 3299 i am getting timeout error as below.
┘NI_RTERR& ┴*ERR*1connection timed out-5NI (network interface)70038nirout.cpp544
1RTPENDLIST::timeoutPend: CONNECTED timeoutMon Mar 03 13:49:22 201419SAProuter 3
8.10 on 'saprouter'*ERR*
Connection to host lost.
Even when i am doing telnet from SAPRouter machine same error is coming.
Note: SAPRouter service is started and no errors in dev_rout
Our network team is saying port 3299 is already open on firewall, They also done nating.
Kindly help us to solve this issue, why this timeout error is coming when we are doing telent to port 3299
telnet is going but within 5 seconds timeout error is coming and connection is lost.
We have also maintained new IP in OSS1 and generated SAPOSS rfc but rfc is getting fail with Error
Error Details    ERROR: The connection to the specified message server (/H/192.168.60.11/S/329
Thanks
Basis

Answer 1

Hi Basis,
This is fine.I request you to please read below very carefully,hopefully you'll get solution from this
timeoutPend: no route received within 5s (CONNECTED)
You are connected but not does not send route quickly.Here your TCP/IP connection setup was successful.
Route sent too late
The connection setup (connect) was successful but the client sends the route to the SAProuter too late, or the client assumes that it is already connected to the server and is waiting for data, or the timeout -W is exceeded.
The log file contains the following entries:
Thu Jun 14 12:27:27 2007 CONNECT FROM C11/- host 10.66.66.90/35087 (host1.company.corp)
Thu Jun 14 12:27:32 2007 CONNECT ERR C11/- no route received within 5s
Thu Jun 14 12:27:32 2007 DISCONNECT C11/- host 10.66.66.90/35087 (host1.company.corp)
The client issues the error message below.
Syntax
SAProuter Error Message
*********************************************************************** * LOCATION SAProuter 39.1 (SP3) on 'host1' * ERROR connection timed out * * TIME Thu Jun 14 12:27:32 2007 * RELEASE 710 * COMPONENT NI (network interface) * VERSION 39 * RC -5 * MODULE nirout.cpp * LINE 6519 * DETAIL RTPENDLIST::timeoutPend: no route received within 5s * (CONNECTED) * COUNTER 5 ***********************************************************************
Background and Further Analysis
This error can occur if the client does not send the route quickly enough after the TCP/IP connect to the SAProuter. This might be caused by the client hanging temporarily.
Please follow Other Errors - SAProuter - SAP Library
TCP/IP connect takes too long (longer than the timeout -W value)
The log file contains the following entries:
Thu Jun 14 13:22:01 2007 CONNECT FROM C10/- host 10.66.66.90/41060 (host2.company.corp)
Thu Jun 14 13:22:01 2007 CONNECT TO S10/18 host 1.1.1.1/3299 (1.1.1.1)
Thu Jun 14 13:22:06 2007 CONNECT ERR S10/18 could not establish connection within 5s
Thu Jun 14 13:22:06 2007 DISCONNECT S10/18 host 1.1.1.1/3299 (1.1.1.1)
The client issues the error message below.
Syntax
SAProuter Error Message
*********************************************************************** * LOCATION SAProuter 39.1 (SP3) on 'ld8060' * ERROR connection to 1.1.1.1:3299 timed out * * TIME Thu Jun 14 13:22:06 2007 * RELEASE 710 * COMPONENT NI (network interface) * VERSION 39 * RC -5 * MODULE nirout.cpp * LINE 6548 * DETAIL RTPENDLIST::timeoutPend: could not establish connection within * 5s (ROUTED) * COUNTER 6 ***********************************************************************
Background and Further Analysis
In this example, the TCP/IP connection from the SAProuter to the next node (the next SAProuter, a system, or another network component) could not be established within a specified timeout period. This error can occur if the server host is down or the IP address of the host cannot be reached.
It can also be due to the network failing to establish the TCP/IP connection within 5 seconds (the timeout value defined in option -W). You might be able to solve this problem by using a greater value for option -W.
For more information, see: Expert Options in SAProuter Options.
Thanks,
Gaurav