Netgear R7000 not letting cell phones connect to internet but laptops work fine

> I have the router set up as access point, because I have another
> service set up as DHCP server host and providing ip addresses. [...]

   What is this "another service" (server?)?  Does it provide only
client IP addresses, or does it also provide (appropriate) DNS server
and default gateway addresses?

> [...] will not allow cell phones to connect to internet. [...]

   What kind of "not allow" is this?  What's missing in the IP
configuration of the (unspecified) "cell phones"?  Are they getting IP
addresses?  DNS server addresses?  Default gateway addresses?

> [...] Right now I am using my laptop without any issues. [...]

   And how is it connected to anything?  And what is its IP
configuration?

      "My car doesn't work.  What's wrong with it?"

   That's bad enough.  Now add: "I have another car, and it works fine."
What, exactly, is that supposed to tell anyone?

   If your DHCP server was doing its job properly, then I'd expect an
R7000 in wireless-access-point mode to work properly, and that would
normally be the best way to configure it.


   Marking this thread as "Solved!" may not have been the best way to
get more help with this problem.


> Now I have it set up as Router, [...]

   You can expect that to cause new and different problems.  Without
knowing what the actual problem was when you had the R7000 configured as
a WAP, I'd still advise configuring the R7000 as a WAP.  But, if you
want to use two routers, ...

> [...] will let me connect to net but not my local network b/c it
> issues ip address starting with 192 while my server issues ip address
> starting with 10. [...]

   That's one of the problems with cascading two routers.  When a system
on your "10.u.v.*" subnet has a message for a system on your
"192.168.1.*" subnet, it sees it as foreign (not "10.u.v.*"), and so it
sends it to the outside world, where it gets lost.  To make this work,
that system, or the router on the "10.u.v.*" subnet, needs to have an
explicit route to the "192.168.1.*" subnet (using the R7000 as its
gateway).  One solution would be to add a static route on the router for
the "10.u.v.*" subnet like:
      Destination: 192.168.1.0/24
      Gateway:     <WAN/Internet address of the R7000>

   Naturally, that will work properly only if the WAN/Internet address
of the R7000 is fixed (static or reserved), and so you would need to
deal with that somehow.

   Knowing nothing about the main router on the "10.u.v.*" subnet, or
the DHCP server there, makes it hard to offer specific advice.