jwcolby
jwcolby at colbyconsulting.com
Tue Jun 19 13:38:53 CDT 2012
Lucky I suppose. This is OT for AccessD, I forgot to put that in my subject line. I have 3 Areca controllers circa 2006 or so which work beautifully. They provide an application to find and hook the controller to a browser somehow so that I can manage my arrays from inside of Windows. That stuff no longer works. Now I can only manage my arrays from the bios as it boots which is ... clumsy at best. John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 6/19/2012 12:21 PM, Benson, William (GE Global Research, consultant) wrote: > Am I misfortunate or just lucky that I understand none of this thread, though I have read it all including link posted! > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert > Sent: Tuesday, June 19, 2012 8:48 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Haylp! > > ?? http://forums.adobe.com/message/3840720 ?? > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Monday, June 18, 2012 5:06 PM > To: Access Developers discussion and problem solving > Subject: [AccessD] Haylp! > > That's southern. > > I have an Areca 1220 controller which works fine. I have arrays configured and all is well. > ARCHTTP GUI is supposed to launch the default browser and look at 127.0.0.1:81 for the controller. > This worked. I could monitor and manage my raid through the browser page. I hate managing through browsers but hey, it worked. It appears that the controller is a web server which serves up this management software. > > I downloaded the latest version of ARCHTTP.exe from Areca and suddenly the application does not find the controller any more. Going straight to 127.0.0.1:81 in Firefox gives me > > Unable to connect > Firefox can't establish a connection to the server at 127.0.0.1:81 > > This is really bad news since I can no longer manage the raid from the (sucky but servicable) browser based stuff. > > Does anyone have a clue what the problem might be? It seems that the more modern version of the gui exe did something to cause the raid controller web server to cease functioning? > > I am digging out my CD for the original software to see if that exe will "see" the controller". > > -- > John W. Colby > Colby Consulting > > Reality is what refuses to go away > when you do not believe in it > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >