on ‎2020 May 27 11:08 AM
Request clarification before answering.
Hello Prashant,
Can you clarify the landscape here?
Are you running the SAP GUI outside of your corporate network (e.g., at home), and want to connect to the SAP systems at the corporate network by exposing the saprouter on the internet?
If that is the case, I would advise not doing it. Be aware that anyone on the internet would be able to at least reach your system's logon screen. This is already too dangerous.
You should consider using a VPN software to create a secure channel to your company's network. This way, only authorized users would be able to connect.
If you wish to proceed nonetheless, at least configure SAP GUI encryption (SNC) to protect the traffic and prevent your data from being stolen.
Proceed at your own risk!
That being said, the error on the SAP GUI suggests that it might not be reaching your saprouter.
You can use the "niping" tool on the SAP GUI folder ("C:\Program Files (x86)\SAP\FrontEnd\SAPgui") to do some tests and see where the connection breaks:
(the last character on the command lines is the uppercase letter 'o', not the number zero)
If the command outputs "connect to server o.k." then the connection was successful, even if an error occurs afterwards.
Regards,
IsaÃas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Prashant,
As sumitjais mentioned, the connection from your machine to the saprouter is fine.
The issue is from the saprouter onwards.
Besides the telnet test from the saprouter to your SAP system (on port 3201) suggested by Sumit, you can also analyze the saprouter trace (dev_rout) and saprouter log (if activated; the log is optional and defined by the "-G <file>" argument on the saprouter command line) to see whether any issues are logged.
Also as Sumit suggested, confirm that the saprouttab allows the connection:
P <IP from the client1> 10.91.11.119 3201
P <IP from the client2> 10.91.11.119 3201-> "IP from the clients" would be the public (internet) IP, not the IP from the computer itself; or you can add an asterisk ("*") which will mean "all IPs", and the danger and risk are increased exponentially 🙂
Best regards,
IsaÃas
Dear Isaias Freitas
Did all the things as suggested by you but from internet issue remains the same. Also one more point that i noticed is i can connect to the sap system internally using sap router string.But issue remains the same when i try to connect the same system from the internet.
Dear Prashant,
Part of me is glad that it is still not working from the internet, as it seems that you going forward with this despite of all our warnings.
This is really dangerous. You should not expose your SAP system on the internet like that.
I would say that we need a level 2 trace from your saprouter to see what is happening.
Regards,
IsaÃas
Dear tek_20
Do you have access to the saprouter running on "cloud.ucc.ovgu.de" ?
You could verify whether any issues are logged at its log / trace files.
Since it works on a different WiFi, maybe the saprouter is not allowing your address in?
Perhaps discuss this with the university team responsible for this system.
Regards,
IsaÃas
PS: sorry for the delay in replying 🙂
| User | Count |
|---|---|
| 6 | |
| 6 | |
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.