From: L. Jankok (ljankok@gmail.com)
Date: Sun Oct 05 2008 - 05:42:58 ART
I had a terrible first time experience today with proctor labs.
Minutes after I logged in it seems like there was a crash.. The proctorlabs
website and session panel were not accessible. I could still connect to the
terminal server but the other devices would not accept my credentials.
Oh well I thought this could happen, it is not fun but ok.
So I sent an email to support notifying them of the event. About 1 hour
after my
email I got an email from support telling me that they are onsite trying to
fix
the problem. At about 15 minutes later I got an email telling
me that all issues have been fixed.. from there on it was hell.. I had
authentication
issues with the devices [Username: Error during authentication]..
then that was solved.. then I had one router which will ask me a second
password after
I was logged in with my credentials.. which offcourse I didn't know.. after
about 3
hours of frustration I got this last email:
: We were able to guess the UN/PW on your R2 and erase the configuration on
: there for you. You should now be able to access that device.
At that moment I haven't done any configuration yet, so this was a router
with
some leftover configuration.
I can understand that a server can crash and that the proctorlab website can
become
inaccessible but I really can't understand what happened afterwards..
I am really really disappointed with proctor labs.
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:19 ARST