Rest assured that you should not need DHCP enabled on the firewall if you're running it on another server. To figure out what's going on is a process of elimination.
You might try turning off DHCP on the firewall and releasing and renewing the IP address on a client and checking to see if it has the correct TCP/IP settings after you renew it. If it doesn't, then you know you have a configuration problem on the DHCP server. If it does have the correct settings, then you probably have a configuration problem on the firewall (or at least a non-matching configuration between the firewall and the DHCP server; that is, they don't agree on which traffic should be let through the firewall).
As Charles Bundy said, network testing commands like traceroute, ipconfig, nslookup, and ping should reveal the problem. You may also need to brush up on the general principles of firewall configuration, and how to institute them on your particular firewall.
Of course, it's possible that it would also work for you to turn off your internal DHCP server and just let the firewall do DHCP. If it were me, though, I'd want to know why it wasn't working even if I did decide to use the firewall's DHCP at a later time.