[AccessD] Haylp!

jwcolby jwcolby at colbyconsulting.com
Mon Jun 18 16:05:37 CDT 2012


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




More information about the AccessD mailing list