Re: Sonicwall SOHO DHCP problem

From: Bill Somerville (bsomerville@toad.net)
Date: 04/10/02


From: "Bill Somerville" <bsomerville@toad.net>
Date: Tue, 9 Apr 2002 23:47:49 -0400

SonicWALL keeps track of IP addresses that access the Internet on a first
come, first served basis. That includes not only DHCP clients, but also
static clients (e.g. servers). You can see who has grabbed licenses by
doing a tech support report (Tools / Diagnostic / Tech Support Report).
Scroll down to the "License info" section. They should expose this
information somewhere in the UI, rather than just a count.

They generally recommend that you exclude (via rules) any clients (or
servers) who you don't want to consume a license by adding a Deny rule for
WAN access for each IP address (or range) you don't want to consume a
license.

One way to exclude certain DHCP clients is to assign those clients static
addresses and exclude those static addresses.

Or, put everyone behind another NAT router to save on licenses. :-)

-- Bill

"nobody you know" <nobodythere@anywhereyoulook.com> wrote in message
news:es02buk85ceu493p3fgs91irq3j673hqo6@4ax.com...
> I'm running firmware release 5.1.7.0 (the most recent - and evidently
> the last ever) on my Sonicwall SOHO. There is a problem with the DHCP
> server which is annoying but not crippling. No matter what value I
> set the "lease time" setting to, it doesn't seem to drop non-connected
> systems after the lease time has expired and keep a correct count of
> leases in place - but he data box which has the listing of current
> DHCP leases seems to be accurate.
>
> That is, when I click on the DHCP "status" tab, the count of current
> DHCP leases doesn't match the detail listing of the leases (e.g.
> number of current leases = 10 but only 4 actual leases are shown).
> This is a real annoyance because I have people connecting to and from
> the network and run out of "allowed" connections while still having
> only a small number of actual systems connected. The only way to get
> it to count leases correctly is to restart the unit.
>
> Anybody have a clue what (if anything) I'm doing wrong? Or is this a
> known problem?
>
> TIA
>
>



Relevant Pages

  • Re: Unable to Ping
    ... It will also show what DNS servers are being used - which for clients should be the IP address of your server. ... Also, if you run the DHCP manager, does it show DHCP running? ... Coupled with the name resolution problem I'd suspect another DHCP server is giving out leases with the wrong DNS options. ...
    (microsoft.public.windows.server.sbs)
  • Re: error 20169
    ... You will never see leases to VPN clients in DHCP. ... RRAS server leases the IP addresses, then allocates them to clients as ...
    (microsoft.public.win2000.ras_routing)
  • DNS and DHCP
    ... I have a small environment where all clients receive IP's via DHCP. ... leases are 2 hours. ... update DNS A and PTR records", "Discard A and PTR records when lease is ...
    (microsoft.public.win2000.dns)
  • Re: DHCP scopes setup
    ... but what happens to the leases from DHCP that are outstanding? ... I really don't want to delete my existing scope ... Your clients will get whatever address ...
    (microsoft.public.windows.server.sbs)
  • Re: Multiple PTR records wont go away in the reverse zone.
    ... Now please consider how disabling DDNS on DHCP clients ... networks and need to get an IP address and possibly register with DNS. ... remove it or update it when Secure only updates are enabled. ...
    (microsoft.public.windows.server.dns)