Re: CPF4168

["Terry" <tnonamaker@xxxxxxxxxxxxxxxx>]

This may not be correct, but I think if the other device had been previously 
granted that address and had not renewed yet, that device  would not get the 
message.

The 1st device wouldn't know because the other was not on yet.

Terry Nonamaker
  ----- Original Message ----- 
  From: Chuck Lewis<mailto:clewis@xxxxxxxxxx> 
  To: 'Midrange Systems Technical Discussion'<mailto:midrange-l@xxxxxxxxxxxx> 
  Sent: Tuesday, June 08, 2004 9:03 AM
  Subject: RE: CPF4168


  Tim,

  In that case shouldn't the "2nd" device requesting this IP address have
  gotten the "IP address already in use" message ?

  Chuck

  -----Original Message-----
  From: midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>
  [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Kredlo
  Sent: Tuesday, June 08, 2004 10:17 AM
  To: 'Midrange Systems Technical Discussion'
  Subject: RE: CPF4168

  Dave,

  We had this (at least similar) situation here. Seemed to be caused by
  duplicate IP addresses. System would 'soft-assign' an IP address to a
  device, then another device with the same address that had been
  'hard-assigned' would be powered on and devices would start erroring
  out. This may not be a technically exact description of our problem, but
  sounds similar, and might give you somewhere to look.

  Tim



  --
  This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
  To post a message email: 
MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
  To subscribe, unsubscribe, or change list options,
  visit: 
http://lists.midrange.com/mailman/listinfo/midrange-l<http://lists.midrange.com/mailman/listinfo/midrange-l>
  or email: 
MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
  Before posting, please take a moment to review the archives
  at 
http://archive.midrange.com/midrange-l<http://archive.midrange.com/midrange-l>.