About 4 days ago, all inbound traffic to my home network using https on port 443 stopped working properly. Not all 443 traffic died--for example, my MS Direct Push from Exchange to my phone is still working without problem--just stuff actually coming over https.
- Outlook RPC over HTTP is intermittent (connect, disconnect, trying to connect, connect, ad nauseum--outbound e-mail can sit in the local outbox for 20 mins or so before being sent)
- OWA won't connect at all

To troubleshoot, I set up the IIS server to also use port 82 for https, set up the port forwarding, and webmail will work flawlessly there (problem there is that some networks block all https traffic if it's not using 443, so this isn't a permanent solution). Not to mention that RPC over HTTP can only use 443, unless I reconfigure the client OS to always use 82 for SSL traffic, which will cause all other SSL traffic not destined for my server to fail.

I've tested 443 traffic internally and it's fine, so this is limited to externally originating traffic.

I reset the router to factory defaults and reconfigured for my network, and the problem went away for about an hour and then returned.

I'm on FiOS and I have one of the older DLink DI-624 routers. If I call in a replacement, I'll get the craptastic Actiontek monolith, which I'd like to avoid if I can. I also can't flash to the latest DLink firmware, which is newer than the FiOS firmware offering, because the FiOS routers are traffic-shaped to handle VOD traffic. That means I can't just replace it permanently with any old router. I've verified with FiOS that they are not filtering anything other than port 80.

So before I have them swap it out, I'm going to pick up a cheap router from Best Buy tomorrow and test it out.

I think I have this narrowed down to the router, but you never know. Has anyone had any experience with this? I'm open to any and all suggestions.