OK, I think I found it reason. According to the Microsoft|TechNet article: Create Inbound Rules to Support RPC... (Link) and a Blog by Jeff Graves: Using RPC custom port range with Windows Firewall (Link) the problem is due to Svchost.exe and Lsass.exe. Which makes sense as most if not all network communication is done through these two services. They sorta act as a proxy service for most network calls. Anyhoot, give the TechNet article a good read. It should point you in the right direction. Just realize the only port you need to worry about is 31416.
Hope this helps.