I believe that there are several issues in this config.
- certainly the first and most important is the no ip routing command. You should enable ip routing.
- another issue is in your static default route which points only to the outbound interface and has no next hop information
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0
this might work - but it might not work (depends entirely on whether the upstream router has enabled proxy arp).
Even if it does work it is not a good idea. When the outbound interface is Ethernet than a static route specifying outbound interface without next hop will force the router to arp for every destination it is trying to forward to.
I would suggest that a better static default route would be like this
ip route 0.0.0.0 0.0.0.0 dhcp
- you mention that server and computers connect through the switch associated with the router. Do these devices receive an IP address? Your config has a name for a DHCP pool. But no pool is configured.
- also if the server and computers are connected through the switch it looks like they are all in vlan 1. But vlan 1 has no ip address. How would these devices communicate?
- I do agree with the suggestion that you make some changes in address translation. (I do not see the benefit from changing the IP addressing to 172.16). You are using an extended access list to identify the traffic to translate and I see no need, no benefit is using an extended access list when a standard access list would do just as well.
- you specify address translation for 192.168.0.0 and 192.168.1.0. But those networks do not show up anywhere else in your config. Where are they?
- you do have 192.168.4.0 in your config but do not have address translation for it. Is that on purpose?
- you specify no ip cef. Why is this? I am not sure that it is a problem. But in general routers like the 1941 operate much better when cef is enabled.
... View more