Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 20 replies
  • Subscribers 30 subscribers
  • Views 5522 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG210 blown up

Big_Buck

Yes blown up.  Dead.  Nothing. Nada.

Power supply most probably toasted.  No fan. No LED. No LCD.

Called Sophos.  Waited around 75 minutes.  Then line hung up or lost connection.  I re-called.  Waited.

Meanwhile, Sophos WEB site was dead.  Cursor was turning around permanently waiting for HTTPS connection.  That was while trying to open a new case.  One more hour toasted.  At that point, it was more than two in total.  Remember that meanwhile, my phone speaker is repeating the "Please wait while somebody will assist you shortly" ...  Two hours of that message has the potential of turning you numb.

At one point I told myself maybe the chat box works.  It did answer at one point.  The tech there opened the case.

A little before 3 hours waiting, repeating messages stop, then someone on the phone !!!

That tech organised the RMA.  But ...  My business has no phone, no VPN, no mails.  And I'm told I could receive the replacement between 1 to 4 days.

Holy sh...

Paul Jr 



This thread was automatically locked due to age.
Parents
  • 0

    One welcome addition to the revision 3 is the external power connector in the form of a castrated/mini/reduced ATX connector.

    That alone will probably help users solve a very high percentage of problems.  For example, what do you do if the appliance won't boot (most likely a blown CPU), and the backup you made earlier fail to load ?  Particularly since Sophos has decided that BU would imperatively be locked with a password in SFOS 17.5 MR4.

    Lesson learned for a second time.  In version 71 of Checkpoint Firewall, external backups (internal BU did not have the problem) would generate a normal size BU archive file with nothing in there.  I have told Checkpoint about this.  They did not correct this up until two versions later.  Why did I knew that ? Well I let you guess.  It means hundreds, if not thousands, of users have found themself with no backup.  What is absolutely stunning, is the tech at Checkpoint who was asking me if I wanted to open a case.  

    Paul Jr

  • 0 in reply to Big_Buck

    Hey Paul.

    with  your backup are you using the internal or external mail setting? I found using the internal setting does not. Waiting a fix to the alerts which did work before MR-1. I get my daily reports and the backup which reminds me I must document my backup password. I was hoping that the password would be optional.

    Ian

  • 0 in reply to rfcat_vk

    We have two XG210 and two XG105.  Internal mail or external mail seems to change nothing.  At home, I was using my ISP provided mail. Which I know works.  At the office, I use the internal Exchange server.  Like I have mentionned before, after the upgrade, both would fail.  For some reasons, one started to work few days later.  Or so I thought.  Because the file I tried to use to recover did not work.

  • 0 in reply to Big_Buck

    I found the issue with the internal XG mail server was the port it tried to use and my ISP does not like it so everything was queued and nothing sent. Also there internal mail server does not appear to assign a source IP address for the mail messages which means nothing sent.

    Ian

     

    Minor gripe, you cannot see the backup password, you can only change it. Not a very successful implementation of security.

  • 0 in reply to rfcat_vk

    Hello

    "Minor gripe, you cannot see the backup password, you can only change it. Not a very successful implementation of security."

    Not only that.  You do not see the SFOS version.   An MR3 backup will not restore on a MR5 SFOS.  So if your backup dates back one or two version, you better have noted it down.  Otherwise go figure.  But wait !!! It gets worse.  You will not restore either if some of your pattern updates does not match.  Particularly "AP Firmare" I presume.  

    It is most possibly THAT problem I had.

    Paul Jr Robitaille

Reply
  • 0 in reply to rfcat_vk

    Hello

    "Minor gripe, you cannot see the backup password, you can only change it. Not a very successful implementation of security."

    Not only that.  You do not see the SFOS version.   An MR3 backup will not restore on a MR5 SFOS.  So if your backup dates back one or two version, you better have noted it down.  Otherwise go figure.  But wait !!! It gets worse.  You will not restore either if some of your pattern updates does not match.  Particularly "AP Firmare" I presume.  

    It is most possibly THAT problem I had.

    Paul Jr Robitaille

Children
  • 0 in reply to Big_Buck

    Hi Paul,

    I think there was a documented change between MR-3 and MR-5, something about a format change. Your mail message if you have one should identify the SFOS version or at least mine does and I don't mean the name of the backup.

    More testing is required before an update release.

    Ian