<div>
Ultimately, the clients are sending traffic to an IP address. &nbsp;If that IP address is not mapped to your load balancer, your load balancer won't see the traffic. &nbsp;You need to see what IP the clients are sending data to, and work backward from that. &nbsp;This may be a DNS issue.
</div>


Ultimately, the clients are sending traffic to an IP address.  If that IP address is not mapped to your load balancer, your load balancer won't see the traffic.  You need to see what IP the clients are sending data to, and work backward from that.  This may be a DNS issue.

<div>
I think what has happened is i forgot to put the exchange server in maintenance mode
</div>


I think what has happened is i forgot to put the exchange server in maintenance mode

<div>
hi,<br />
Assume both the servers are in cluster mode.<br />
Exchange is in LAN ( not able to view .vsdx)<br />
&nbsp;Barrcuda is for WAN-LB. Means load balncing with 2 iSP line.<br />
<br />
Is this.. all the exchange is before barracuda then wan isp/ wan router.<br />
&nbsp;If possible take a &nbsp; &nbsp;. jpg and attach.
</div>


hi,
Assume both the servers are in cluster mode.
Exchange is in LAN ( not able to view .vsdx)
 Barrcuda is for WAN-LB. Means load balncing with 2 iSP line.

Is this.. all the exchange is before barracuda then wan isp/ wan router.
 If possible take a    . jpg and attach.

<div>
<div class="content wysiwyg-content">
I have two Exchange 2016 servers sitting behind a barracuda load balancer. When I place disable the services on one of the the servers, from the LB. I still see connections going back to the disabled server. Running a tcp dump from the Barracuda shows no connections going to the LB. It appears that the Outlook clients are trying to connect directly to the backend server. If a client work station is rebooted eventually it will connect to the enabled server, it appears that the Outlook client is bypassing the LB. Any ideas?<br />
<a href="https://filedb.experts-exchange.com/incoming/2019/01_w03/1409602/Email-LB.vsdx" target="_blank" class="file-inline" title="Exchange load balancer issue (49 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Email-LB.vsdx</a>
</div>
</div>


Email-LB.vsdx

I have two Exchange 2016 servers sitting behind a barracuda load balancer. When I place disable the services on one of the the servers, from the LB. I still see connections going back to the disabled server. Running a tcp dump from the Barracuda shows no connections going to the LB. It appears that the Outlook clients are trying to connect directly to the backend server. If a client work station is rebooted eventually it will connect to the enabled server, it appears that the Outlook client is bypassing the LB. Any ideas?

Outlook client bypasses the Load balancer

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.