Router not processing port 443 traffic over https
 

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.

Maybe the problem is not with the D-Link but with Verizon. I believe they block port 80 already, and port 443 is logically the next port to get the firewall treatment. Verizon will happily sell you their business package with static IP without any filtering at 3 times the price ;)

It might be the carrier, but I've had poor luck with Dlink routers. Enough so that I've replaced them all. I can't say yours is the router, but if you have a chance to try another brand, (or a new Dlink), I'd go that route first.

I specifically pressed them for 443 blocking, and they deny it, while freely admitting the port 80 block. Also, if they did block 443, my Direct Push would fail.

One thought I had was that they limited my inbound port 443 traffic to one connection at a time, so I shut off the Direct Push on the phone and kicked everyone off webmail, but the RPCoHTTP still was screwy.

I'll find out tomorrow. There's a cheap NetGear at BestBuy I saw online tonight. Whatever I buy I'll be returning after I test it out.

What a PITA this is. It all worked perfectly for over a year and a half.

Netgear El-Cheapo 802.11g router works perfectly. Ordered replacement router from Verizon...hopefully it will still be the DLink instead of the Actiontec.

Good news! At least you found the cause of the problem. That's half the battle.

Glad the problem was just the router. I think my D-Link router has been acting up lately too.