Unconfigured Ad Widget

Collapse

Huge headache with AD, DNS, DHCP, Server 2003

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • moarammo
    Banned
    • Oct 2010
    • 9

    Huge headache with AD, DNS, DHCP, Server 2003

    I know the title isn't very telling, but that's how vague and weird this little group of problems is.

    Here's the layout of the network.

    We have three public IP's from our ISP that are routed through an older sonicwall router using one-to-one NAT. We'll call them .241 .242 and .243. The way it's currently set up, on the WAN settings of the Router, it has .241 listed as the "WAN Gateway (Router) address", and .242 as the "SonicWall WAN IP (NAT Public) Address". Under "one-to-one NAT", it has .243 pointed to the local server here, at 192.168.10.3. The server functions as the local DNS server and DHCP server.

    Now, for some STRANGE reason, it hands out IP addresses no problem and everything works awesomely up until we get past 192.168.10.50. Once IP addresses start getting assigned higher than that, they just refuse to connect to the internet. All of the IP info is coming correct,

    IP 192.168.10.52
    SUBNET 255.255.255.0
    GATEWAY 192.168.10.1

    DNS 192.168.10.3

    But it just goes nowhere. I have DHCP set up to assign IP's all the way up to .75 so that's good. I just have no idea where this could be locking up as I don't use windows servers as DHCP servers very often. Someone set this up a LONG time ago.


    Any clue what the problem might be? I'm tearing my hair out here.
  • #2
    Dark Paladin
    學者, 羇客, 神戰士
    CGN Contributor - Lifetime
    • Sep 2008
    • 1531

    Based on the limited information here, it sounds like a Sonicwall issue. Tried rebooting the device? I am assuming IPs above .50 has worked before?

    I have worked with sonicwalls before and have seen them act finicky every now and then.

    It looks like you have your DHCP scope and subnetting set correctly, so it isn't a logical network issue. I am not entirely sure why you have a Gateway IP and then a NAT Public IP. . . so I'm going to guess it has something to do with your topology or business requirement.
    Last edited by Dark Paladin; 11-08-2012, 2:27 PM.

    Comment

    • #3
      m03
      Senior Member
      • Nov 2007
      • 1911

      It's a Sonicwall licensing issue, as IIRC, they license per client IP. 50 clients sounds like the default license limit on their old SoHo firewalls.

      In order to allow more, you'll either need to pay for a license upgrade, or replace it with something else.

      Comment

      • #4
        Bete Noire
        Senior Member
        • Apr 2008
        • 578

        The licensing on the older model sonic walls were sold in IP address blocks, ie 0-10 users, 11-20, etc. only allows access to that number of users. You can reset the leases in the security tab on the sonic admin console.

        Comment

        • #5
          Bete Noire
          Senior Member
          • Apr 2008
          • 578

          You cannot even buy more licenses for the end of life products. I had to buy a new unit that doesn't restrict number of users.

          Comment

          • #6
            TML
            Member
            • Apr 2012
            • 262

            Bete Noire is right about the licensing model, but I wouldn't be surprised if it were something else. I learned too late into my career that SonicWall is not the most reliable product...

            Comment

            Working...
            UA-8071174-1