Dima is right. It is as simple as to change the HTTPS farm (443 Port) by a
L4 farm or TCP farm. The issue is that the RPC verbs aren't supported by
HTTPs farm.
Regards
2013/12/29 Dima Polyakov <[email protected]>
> There you go! You have few options why it did not work in your original
> setup:
>
> - RPC uses ports (TCP or UDP) that are not forwarded (for
> example according to http://support.microsoft.com/kb/325930 you need port
> 139). I guess you can find out if you run a sniffer on your client to see
> what ports it is trying to connect to.
>
> - RPC uses UDP, and you have opened only TCP
>
> - There is also ICMP (ping) that might be used somewhere in RPC
> (doubt, but you can check it as well with a sniffer).
>
> By setting * - you just do NAT for everything that comes to that IP. By
> specifying ports – you basically adding a firewall, do you really need it
> on a load balancer? In my opinion load balancing should do only LB,
> firewall should do a dedicated firewall/router like Cisco ASA:
>
> ---internet---firewall/router---zlb---servers
>
>
>
> Dima
>
>
>
> *From:* Damien Solodow [mailto:[email protected]]
> *Sent:* Saturday, December 28, 2013 5:55 PM
>
> *To:* [email protected]
> *Subject:* Re: [Zenloadbalancer-support] Issues with Exchange 2010 CAS
>
>
>
> Setting the port on the l4txnat farm to * and the NAT type to 'NAT' works.
>
> So what does that tell us about the issue? Or is it likely that the
> answers would be in the iptables logs on the Zen box?
>
>
>
> On Fri, Dec 27, 2013 at 11:41 PM, Dima Polyakov <[email protected]>
> wrote:
>
> hm.. can you leave port empty? Let’s redirect all traffic.
>
> You might also want to look at iptables log if packets get dropped there
> (you will need to login into debian,
> http://www.thegeekstuff.com/2012/08/iptables-log-packets/).
>
>
>
> Dima
>
>
>
>
>
> *From:* Damien Solodow [mailto:[email protected]]
> *Sent:* Friday, December 27, 2013 11:13 PM
>
>
> *To:* [email protected]
> *Subject:* Re: [Zenloadbalancer-support] Issues with Exchange 2010 CAS
>
>
>
> I replaced the tcp farm for port 6001 with one using 'l4txnat' and port
> 6001.
>
> The failure was the same.
>
>
>
> The F5 setup is different from Zen; F5 has an Exchange 2010 template that
> configures the "farms" for it. The setup is pretty similar though.
>
>
>
> On Fri, Dec 27, 2013 at 10:46 PM, Dima Polyakov <[email protected]>
> wrote:
>
> Can you make L4 farm as an experiment to see if it works with RPC? (if it
> works then my initial guess is correct).
>
> Also, with what type of farm F5 load balancer is setup? Is it the same
> configuration as ZLB?
>
>
>
> And just a wild guess, RPC library can make an initial ping before making
> actual RPC. There is an utility from MS:
> http://technet.microsoft.com/en-us/library/hh875578.aspx to do rpcping.
>
>
>
> Dima
>
>
>
>
>
> *From:* Damien Solodow [mailto:[email protected]]
> *Sent:* Friday, December 27, 2013 9:36 PM
> *To:* [email protected]
> *Subject:* Re: [Zenloadbalancer-support] Issues with Exchange 2010 CAS
>
>
>
> Doubtful; I think "ping" in the results is a bit of a misnomer as it's
> likely doing a tcping instead. :)
>
> Also I have a similarly configured Exchange array at another client using
> an F5 load balancer and the "ping" from the Remote Connectivity Analyzer
> succeeds.
>
>
>
> On Fri, Dec 27, 2013 at 9:30 PM, Dima Polyakov <[email protected]>
> wrote:
>
> Could it be because ping is ICMP protocol and ZLB is configured for TCP
> (telnet runs on TCP as well, that can explain why ping fails but telnet is
> ok).
>
>
>
> Dima
>
>
>
>
>
> *From:* Damien Solodow [mailto:[email protected]]
> *Sent:* Friday, December 27, 2013 9:22 PM
> *To:* [email protected]
> *Subject:* [Zenloadbalancer-support] Issues with Exchange 2010 CAS
>
>
>
> Running Zen 3.02 on VMware; 2 Exchange 2010 CAS servers in a CAS array.
>
> Zen was configured per the documentation linked on zenloadbalancer.org,
> including setting static ports and SSL offload on Exchange.
>
> I also created farms for ports 6001, 6002, and 6004.
>
>
>
> Currently all the Exchange related farms only have one backend server
> listed.
>
>
>
> Everything seems to work except for Outlook Anywhere.
>
>
>
> The Remote Connectivity Analyzer shows:
>
> Attempting to ping RPC endpoint 6001 (Exchange Information Store) on
> server outlook.domain.com.
>
> The attempt to ping the endpoint failed.
>
>
>
> Additional Details
>
> An RPC error was thrown by the RPC Runtime process. Error 1818
> CallCancelled
>
> Elapsed Time: 33191 ms.
>
>
>
> I know the error 1818 is a timeout; running a similar test internally
> shows an error 1722 (RPC_Server_Unavailable).
>
>
>
> From an internal PC I can successfully telnet to 6001 using the Zen farm
> IP.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
--
Load balancer distribution - Open Source Project
http://www.zenloadbalancer.com
Distribution list (subscribe): [email protected]
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
