I am having some peculiar issues with some head office users. A lot of users there connnect to mailbox via OWA since they access from kiosks. OWA URL is https://webmail.contoso.com These requested a load balanced by a Cisco load balancer and sent to one of several Exchange 2007 SP2 CAS servers (CAS1.contoso.com, CAS2.contoso.com etc) running on Windows 2008 servers. Then onto the user's Exchange 2007 SP2 Mailbox server (Mail1.contoso.com, Mail2.contoso.com etc). Some of these users are getting time outs etc. I think the problem maybe a CAS server. But, if User1 calls in and says there are experiencing this, I don't know how to work out which CAS server they are going through. Is there any way to find this out? Obviously, they connect ultimately to their own mailbox server, but what logs can I look at/tools I can run, to find out which CAS their OWA connection is going through?

On Wed, 2 Feb 2011 17:51:11 +0000, PaulDaniels2011 wrote: >I am having some peculiar issues with some head office users. A lot of users there connnect to mailbox via OWA since they access from kiosks. OWA URL is https://webmail.contoso.com These requested a load balanced by a Cisco load balancer and sent to one of several Exchange 2007 SP2 CAS servers (CAS1.contoso.com, CAS2.contoso.com etc) running on Windows 2008 servers. Then onto the user's Exchange 2007 SP2 Mailbox server (Mail1.contoso.com, Mail2.contoso.com etc). Some of these users are getting time outs etc. I think the problem maybe a CAS server. But, if User1 calls in and says there are experiencing this, I don't know how to work out which CAS server they are going through. Is there any way to find this out? Obviously, they connect ultimately to their own mailbox server, but what logs can I look at/tools I can run, to find out which CAS their OWA connection is going through? Shouldn't your load balancer be able to tell you where it's sending the connections? The IIS logs on the CAS servers will have lots of information. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich Getting access to the load balancers would take a decade, they are managed by an outsourced team. Is there nothing on the mailbox server I can run to find out which CAS the connection came from for a specific user? We have loads of CAS servers, so not possible to check the IIS logs on each one.

On Mon, 7 Feb 2011 20:23:32 +0000, PaulDaniels2011 wrote: >Getting access to the load balancers would take a decade, they are managed by an outsourced team. > >Is there nothing on the mailbox server I can run to find out which CAS the connection came from for a specific user? We have loads of CAS servers, so not possible to check the IIS logs on each one. Can you see where Outlook users are connected? I was going to suggest get-logonstatistics, but I think the only way to know is to use ExMon. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

> "Can you see where Outlook users are connected" Not sure what you mean by this? I guess Exmon will help, but not sure if it will show the CAS or the source client?

On Tue, 8 Feb 2011 21:22:37 +0000, PaulDaniels2011 wrote: > > >> "Can you see where Outlook users are connected" > >Not sure what you mean by this? I meant that you probably can't see the IP address of a client that's connected using RPC. Since the CAS uses RPC to connect to the mailbox server you wouldn't be able to see what you're after, >I guess Exmon will help, but not sure if it will show the CAS or the source client? Neither am I. But the IIS log files would -- if the load balancer uses the originator's IP address when it connects to your CAS. But if it does, then your default route would have to be set to the load balancer and most of them aren't designed to handle such large volumes of traffic. I'd guess that they're using a NAT and you'll see the NAT address, not the client's in the IIS logs. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP