RE: CPF4168 -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: CPF4168
From: "Chuck Lewis" <clewis@xxxxxxxxxx>
Date: Tue, 8 Jun 2004 11:03:38 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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] 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

Follow-Ups:

Re: CPF4168 , Terry
RE: CPF4168 , Tim Kredlo

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.