Hello,
I am sharing a project working with you so that you can open and compare what you did with the project and I will share some insites about what you need to focus on:
First, you were concerned about the firewall and the ACLs but you did not mind about the basic connectivity. In a project like that, prior to worry about security you need to make sure the communication is fine.
You need to have routes on the firewall and in both routers. You did right on the "Microsoft Router" by puting a default route sending to firewall. As this router have only one possibility, the default route here suilts very well.
But, it is not enough. The Firewall does not know about the network where the server is in, and you need to tell the Firewall that in order to reach the server it must send the packets to "Microsoft Router" . Do a "show run" on the firewall ASA and look how I built the routing.
Then you have the "D-Ocean Clinic" router. This router also had to be instructed on how to reach the server network. On this case you can also use a default route sending to Firewall as the Firewall ASA is the only option it have.
And the Firewall ASA needs to be instructed that , in order to send packets back to PCs and Phones , it needs to send the packets to the Router "D-Ocean Clinic" . Again, check how I build the routing on the ASA.
Only after all this, after you are able to ping from PC and Phone to the Web server, you can worry about security.
Then, you can add the Access list on the ASA just like I did.
