[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-developers] Conflict between Virtual Site IP address and Hardware IP Address



I would test that to be sure. First, ping .51 and see if you get a response
(when it's not being used by the rack). If no response is returned, try
assigning .51 to another machine (maybe a handy laptop?) and see if you can
communicate with it then.


Regards, 

Chris


-----Original Message-----
From: cobalt-developers-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx] On Behalf Of Nigel Neilsen
Sent: Wednesday, May 12, 2004 1:59 PM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: RE: [cobalt-developers] Conflict between Virtual Site IP address
and Hardware IP Address


Thought of that... but there are only 3 devices on that network .49, .51 and
.62 nothing else is plugged in there. Nigel

-----Original Message-----
From: cobalt-developers-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx] On Behalf Of Or-Or
Sent: Wednesday, May 12, 2004 12:41 PM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: RE: [cobalt-developers] Conflict between Virtual Site IP address
and Hardware IP Address

Sounds like another device on your network has attempted to also use .51.


Regards, 

Chris

-----Original Message-----
From: cobalt-developers-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx] On Behalf Of Nigel Neilsen
Sent: Wednesday, May 12, 2004 12:46 PM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: [cobalt-developers] Conflict between Virtual Site IP address and
Hardware IP Address


Has anyone ever seen an error like this before?

I came it to work this morning and my Users couldn't access there email and
I couldn't access my 550 via SSH or HTTP. 

I changed the IP address through the LCD from .51 to .52 then I could access
the server fine. The Virtual sites and email are still serving from the old
IP address .51 . I have 3 virtual sites that are served from .51 and the
hardware had also used that address without incident for about 18 months
until this morning.  Note I hadn't applied the EOL Patch when this error
occurred.

 

I am up and running now but this error has baffled me as to what caused it.

 

Nigel

_______________________________________________
cobalt-developers mailing list cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers

_______________________________________________
cobalt-developers mailing list cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers

_______________________________________________
cobalt-developers mailing list cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers