connection problem when use .net connection in VS.net

[Former Member]

Hi, I installed .net connector 2.0 in VS.net 2003, when I try to connect a SAP R/3 server in "server explorer", I got the following error message.

-

---

from here----

---

Connect to SAP gateway failed

Connect_PM GWHOST=xx.xx.xx.xx, GWSERV=sapgw00, ASHOST=xx.xx.xx.xx, SYSNR=00

LOCATION CPIC (TCP/IP) on local host

ERROR partner not reached (host bscndev, service 3300)

TIME Thu Jan 27 12:22:18 2005

RELEASE 620

COMPONENT NI (network interface)

VERSION 36

RC -10

MODULE ninti.c

LINE 972

DETAIL NiPConnect2

SYSTEM CALL SO_ERROR

ERRNO 10061

ERRNO TEXT WSAECONNREFUSED: Connection refused

COUNTER 1

-

---

end of here----

---

The DestinationType in properties of this server is set as "SAPLOGON.INI based Logon Settings". There is no problem if I connect the R/3 server using sapgui.

I tried some other R/3 systems, both of access from VS.net and sapgui were OK.

Are there anybody have some ideas regarding to this problem? Also, I have no idea why sap logon from VS.net will connect to SAP gateway?

Thanks and best regards,

Jin Shen

[reiner_hille-doering · Accepted solution]

Might be the system is not configured as usual. RFC-based communication allways needs a so called Gateway process, that is normally automatically running on each application server. SAPGUI doesn't need it.

[Former Member · Accepted solution]

Hi, Reiner

Thanks for your prompt response.

Could you tell me where I can configure such parameters?

I tried to connect another R/3 server via VPN, both SAPGUI and .net connection work well.

But for this one, the server is located behind a F/W, so I guess maybe the F/W is blocking the packets to go throught port 3300.

Thanks and best regards!

Jin Shen

[reiner_hille-doering · Accepted solution]

> But for this one, the server is located behind a F/W,

> so I guess maybe the F/W is blocking the packets to

> go throught port 3300.

Yes, this is very likely.

You can try

"telnet <gwhost> 3300". If this fails to connect, than there seems to be indeep port 3300 be blocked.

You could ask your adminstrator to open it. Or there might be a SAPRouter installed that routes to the server. If there is one you should try to create a SAPLOGON entry containing the correct SAPROUTER string.

[Former Member · Accepted solution]

Reiner,

Thanks for your advice. After open port number 3300 on F/W, I can connect to the server now.

regards,

Jin Shen