|If there's no particular reason to have the two separate subnets I would just put everything on the same subnet.|
As it stands, it looks like you're using your server to route between the two subnets. At least, to allow traffic from 192.168.10.x to the 192.168.1.x network and therefore the internet.
Your wireless clients can't communicate with the 192.168.10.x network because there's no route from the 192.168.1.x subnet to the 10.x subnet. You would have to create a route in the server for this.
What I would do if there's no special need for two separate subnets is leave 192.168.1.6 statically assigned to the server and disable it's DHCP. Let the client PC's get their TCP/IP settings from the router. If you're physically setup as follows:
Internet >> Router >> Server & Clients
Then it'll work out nicely and have the added benefit of LAN communication between the wired and wireless clients without messing around with static routes.
If you have an Active Directory domain setup, you will have to make the DNS address DHCP gives out to clients point at the DC and then in turn, forward the DNS on the DC to your ISP's DNS server(s).
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.