Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

OWA (Exchange 2010): "Reply" to with Firefox: "Your network connection is unavailable. Please reconnect and try again."

  • No replies
  • 1 has this problem
  • 1 view
more options

[Originally posted in Microsoft's Exchange forum: https://social.technet.microsoft.com/Forums/exchange/en-US/6420fefb-a568-4aa4-969b-768808640c54/exch-2010-reply-to-with-firefox-your-network-connection-is-unavailable-please-reconnect-and?forum=exchangesvrdeploylegacy ]

Hi guys.

I've got a bizarre problem with Outlook Web App (formerly called "Outlook Web Access", also known as "OWA") that I can only reproduce with Firefox. At first sight it seems to point to a network issue, but I think it might be an internal issue only Firefox has with constructing a request towards OWA... (URL query string? Headers such as cookie?)

First, this issue only happens with "certain" messages. I cannot tell what makes these messages special, but I currently have such a message in my inbox. When I try to respond to it I get the above error message. When I try to respond to other messages in my inbox I don't. When it happens it happens both in Firefox for Windows and Mac OS X.

Also, the issue is independent on whether I use the external or the internal URL to OWA.

Our specific Exchange version seems to be (sorry for pasting this whole snippet, I don't know what's relevant as I'm not an Exchange engineer, just a user):

Outlook Web App experience: Premium Exchange mailbox address: <deleted> Version: 14.3.224.2 Proxy host address: <deleted> Proxy version: 15.0.1076.0 Exchange Client Access server .NET Framework version: 2.0.50727.5485 Client Access server operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1 Client Access server version: 14.3.123.0 Client Access server platform: 64bit Mailbox server Microsoft Exchange version: 14.3.123.0 Other Microsoft Exchange server roles currently installed on the Client Access server: Hub Transport Authentication type associated with this Outlook Web App session: Basic Authentication type for Exchange Client Access server to Client Access server proxy session: Negotiate Public logon: No Custom Forms: loaded Segmentation settings: fffffffe6fc3ffff Restricted functionality settings: fffffffe6fc3ffff

Again this does NOT happen with any browser other than Firefox (I checked Opera, Safari, Chrome, latest versions each). I used a clean Firefox profile, so it's not due to some extension or user setting.

When I click "Reply," and in the reply convert from HTML to "Text", I can send. That supports my theory that "something" in the POST body confuses Firefox...

Any idea what might be going on here??? Any idea how to debug this? For the message where I can reproduce the issue I can look up the POST URL and headers involved by "Web Developer > Web Console > Network", but I can't do so for messages where I can't reproduce the case because the "Reply" window then closes, and the URL and POST headers are lost (or is there a way to stop the window from closing so that I can see the URL and headers and compare them to the case where I can actually reproduce the error message?).

Thanks much for your help.

Best,

Ralf

[Originally posted in Microsoft's Exchange forum: https://social.technet.microsoft.com/Forums/exchange/en-US/6420fefb-a568-4aa4-969b-768808640c54/exch-2010-reply-to-with-firefox-your-network-connection-is-unavailable-please-reconnect-and?forum=exchangesvrdeploylegacy ] Hi guys. I've got a bizarre problem with Outlook Web App (formerly called "Outlook Web Access", also known as "OWA") that I can only reproduce with Firefox. At first sight it seems to point to a network issue, but I think it might be an internal issue only Firefox has with constructing a request towards OWA... (URL query string? Headers such as cookie?) First, this issue only happens with "certain" messages. I cannot tell what makes these messages special, but I currently have such a message in my inbox. When I try to respond to it I get the above error message. When I try to respond to other messages in my inbox I don't. When it happens it happens both in Firefox for Windows and Mac OS X. Also, the issue is independent on whether I use the external or the internal URL to OWA. Our specific Exchange version seems to be (sorry for pasting this whole snippet, I don't know what's relevant as I'm not an Exchange engineer, just a user): Outlook Web App experience: Premium Exchange mailbox address: <deleted> Version: 14.3.224.2 Proxy host address: <deleted> Proxy version: 15.0.1076.0 Exchange Client Access server .NET Framework version: 2.0.50727.5485 Client Access server operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1 Client Access server version: 14.3.123.0 Client Access server platform: 64bit Mailbox server Microsoft Exchange version: 14.3.123.0 Other Microsoft Exchange server roles currently installed on the Client Access server: Hub Transport Authentication type associated with this Outlook Web App session: Basic Authentication type for Exchange Client Access server to Client Access server proxy session: Negotiate Public logon: No Custom Forms: loaded Segmentation settings: fffffffe6fc3ffff Restricted functionality settings: fffffffe6fc3ffff Again this does NOT happen with any browser other than Firefox (I checked Opera, Safari, Chrome, latest versions each). I used a clean Firefox profile, so it's not due to some extension or user setting. When I click "Reply," and in the reply convert from HTML to "Text", I can send. That supports my theory that "something" in the POST body confuses Firefox... Any idea what might be going on here??? Any idea how to debug this? For the message where I can reproduce the issue I can look up the POST URL and headers involved by "Web Developer > Web Console > Network", but I can't do so for messages where I can't reproduce the case because the "Reply" window then closes, and the URL and POST headers are lost (or is there a way to stop the window from closing so that I can see the URL and headers and compare them to the case where I can actually reproduce the error message?). Thanks much for your help. Best, Ralf

Modified by Ralf G. R. Bergs