HI all,
I have NAV2009R2 Commerce Gateway service adapter installed within BizTalk 2006R2 host.
It run perfectly with NAS and CG broker installed on the same machine, meanwhile SQL server are on separate machine. The Navision client able to connect to CGRS within the same machine but not from other machine
I try to telnet client from another machine but connection is failed (Unable to open the port).
After I uninstalled the CGRS and installed the downgraded version of CGRS NAV4.0 sp3 and NAV 4.0 sp3 client it works perfectly fine. From localhost and remote host I can telnet client to CGRS service.
The question is: Does CGRS NAV2009R2 service has additional dependency/config so the service is accessible in the domain/sub domain network?
Note: firewall is not the factors due off the service and/or firewall exception already created for CGRS.
CGRS config set allow all source IP to connect.
Please anybody help.. thanks
0
Comments
Finally I am able to pin down the main issue.
Navision 2009R2 Service listerner type such as Commerce Gateway Service, CG Broker and NAS TCP listener, they are now bind to IPv6 format instead of IPv4.
If you can't have have IPv6 in your domain network but IPv4, then forget it to have multiple host installation for commerce gateway integration with BizTalk Server. CGRS and CG Broker allow you to enforce bind to IPv4 but NAS TCP listener unable to. Tough CG broker and TCP NAS listener may reside in the same host, CG broker unable to communicate with TCP NAS listener. Looking to this situation, TPv6 is a must have or else don't take Commerce Gateway solution at all..... :thumbsdown:
Tino Ruijs
Microsoft Dynamics NAV specialist