Re: Wierd 301 Moved Loop in OWA

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Nov 5, 1:44 pm, "Lee Derbyshire [MVP]" <email a@t leederbyshire d.
0.t c.0.m> wrote:
"Aaron" <Aaron.Sm...@xxxxxxxx> wrote in message

news:1dde5a90-77d5-4543-94d7-fb46c334d6eb@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



So I pulled up TCPView on our exchange server to take a look at it for
an unrelated issue and noticed a ton of TCP connections in TIME_WAIT
mode all from a single IP (A users workstation on the network).
Curious, I captured some network traffic from that IP and saw what
appears to be some sort of endless redirect loop.  It's trying to do
an HTTP connection (via OWA/WEBDav I assume) for one certain item in
the user's Contact's folder.  The server responds with a 301
Permanently Moved and the new address.  Then the client immediately
requests the same, original path again, gets another redirect, asks
again, redirected again, etc. etc. etc.  pretty much continuously.
This user uses Macintosh OSX and is apparently using something called
Mailapp.  Our OWA setup is a little odd in that it's set to listen on
a non standard port for regular HTTP and then the usual 443 port for
SSL.  We then have a seperate web "site" that listens on port 80 and
redirects all requests to HTTPS.  Has anyone run in to this or might
have an idea of what's going on?  It doesn't really seem to be
affecting the server adversely from what I can see, but I'd still like
to track down the issue and eliminate it.

Can you show us the IIS log entries generated by these requests?  If there
are several sites on the server, you will need to check several log
directories.

Lee.

--
_______________________________________

Outlook Web Access for PDA, OWA For WAP:www.leederbyshire.com
________________________________________

Hope it's not too late to post these. Here is a snippet from the logs
for our Redirect. This site listens on port 80 and redirects all
incoming traffic to the regular OWA site, but with HTTPS. I've
scrubbed it a bit to remove names and usernames, etc.

2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385324.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385325.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385326.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385327.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385328.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385329.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385330.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385331.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385332.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0
2008-11-26 20:10:15 W3SVC1074716464 <Server IP Here> HEAD /username/
Contacts/SomeFirstName+SomeLastName-385333.EML - 80 - <User IP Here>
CFNetwork/129.22 301 0 0

Looking at the logs for the website that houses the actual OWA
install, I can find no reference to this USer's IP, username,or the
URL...
.

Relevant Pages

  • Re: OWA Publishing Question
    ... To: <server to publish>. ... Listener: HTTP ... Port: Disabled ... <public name of the OWA site> ...
    (microsoft.public.isa.publishing)
  • Re: Danger to having Port 80 open on hardware firewall
    ... Seems to me that if you don't port forward 80, then you are not going to get ... the ssl redirection <http <> https>. ... >> requests never go any further. ... I usually redirect ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA Publishing Question
    ... > Listener: HTTP ... > Port: Disabled ... create your OWA Access policy as follows: ... > Authentication Mode: OWA Forms-Based ...
    (microsoft.public.isa.publishing)
  • RE: OWA - DMZ to internal Exchange 2003 Servers
    ... Do you use ISA server for publish OWA? ... Do you need to open HTTP and not use only HTTPS? ... If you using Exchange as mail relay on the DMZ there may be need to change ... > Internet to DMZ Network Port and Protocol Requirements ...
    (microsoft.public.exchange.design)
  • RE: OWA - DMZ to internal Exchange 2003 Servers
    ... Do you use ISA server for publish OWA? ... Do you need to open HTTP and not use only HTTPS? ... If you using Exchange as mail relay on the DMZ there may be need to change ... > Internet to DMZ Network Port and Protocol Requirements ...
    (microsoft.public.exchange.connectivity)