Lewis,
I don't think that's my problem...

In this case, the DHCP Monitor shows:
Settings->Monitor_Interface->LAN1
Status:  DHCP Client is not running.

The first of the above is as it should be.  The second is wrong!
  i.e.,  When I display the active tasks [Ctrl-Task_List on eCenter],
         there, right at the top is:
                DHCPCD.EXE (82)
Methinks DHCPMON is confused!  And, it did not work this way a while
back.  But, I've forgotten when it changed or what I might have done to
cause the change.  FWIW, the DHCP Monitor is V4.1.

Carl

On Mon, 25 Sep 2006 09:37:25 -0400, Lewis G Rosenthal wrote:

  

Carl, I've found that when that issue occurs, I simply wait a bit, and then re-start DHCPMON. Eventually, it gets the idea that the interface it previously accessed is no longer there, and gets the new information. Bug? Probably. I haven't seen it overly persistent, however.

On 09/24/06 11:57 pm, Carl Gehr thus wrote :
    

Lewis,

In the set of commands you show below [I use them almost verbatim.],
there is the command that stops the DHCP Monitor.  [ dhcpmon -t ]

BUT, I have had problems trying to get the monitor back so it will
display the status, config, etc., of the newly started LAN1.  I've
tried specifying:
dhcpmon -i LAN1
but this seems to do absolutely nothing.

Can this be done?  What, if anything, am I missing?

TIA,
Carl