locked
Live OneCare in a SBS2003 Network RRS feed

  • Question

  • I am seeing the backup configuration succeed when the PC is connected directly to the Internet but fail when connected within our SBS2003 network which requires going through ISA2004 firewall at the server.  I know there is a different thread for Update issues but the same is true for doing Updates:  succeed when connected directly and fail when working through the SBS and ISA.  My question is whether I missed something in the installation process of OneCare Beta 2.0 regarding an inability to configure backup or do Updates inside the ISA firewall?  If so, tell me what I missed.  If not, I can provide ISA transaction logs.  There were mentions elsewhere on this Forum about SBS2003 working with this, but no indication that ISA2004 was in play.  Thanks for any help. <Gary>

    Wednesday, September 5, 2007 9:54 PM

Answers

  •  N-N wrote:

    I am seeing the backup configuration succeed when the PC is connected directly to the Internet but fail when connected within our SBS2003 network which requires going through ISA2004 firewall at the server.  I know there is a different thread for Update issues but the same is true for doing Updates:  succeed when connected directly and fail when working through the SBS and ISA.  My question is whether I missed something in the installation process of OneCare Beta 2.0 regarding an inability to configure backup or do Updates inside the ISA firewall?  If so, tell me what I missed.  If not, I can provide ISA transaction logs.  There were mentions elsewhere on this Forum about SBS2003 working with this, but no indication that ISA2004 was in play.  Thanks for any help. <Gary>

    The SBS firewall is likely blocking the traffic from OneCare. I believe that this was the case in the current production version, too. OneCare won't work with any authenticated proxy, but a transparent proxy should allow it to pass through unless the firewall on the server is explicitly blocking the traffic.

    We may see a response in here to help, but I'd recommend contact support and also opening a bug on Connect.

     

     Support for 2.0 Beta - http://help.live.com/help.aspx?project=onecarev2 - use the "Get More Help" link in the lower right of the page to contact support via email.

     

    Please file a bug on Connect: https://connect.microsoft.com/site/sitehome.aspx?SiteID=168

    See the Bug Submission Guide - http://connect.microsoft.com/content/content.aspx?ContentID=3480&SiteID=168 - for details on how to create and submit the Support Log zip file with your bug.

     

    -steve

    Wednesday, September 5, 2007 11:55 PM
    Moderator

All replies

  •  N-N wrote:

    I am seeing the backup configuration succeed when the PC is connected directly to the Internet but fail when connected within our SBS2003 network which requires going through ISA2004 firewall at the server.  I know there is a different thread for Update issues but the same is true for doing Updates:  succeed when connected directly and fail when working through the SBS and ISA.  My question is whether I missed something in the installation process of OneCare Beta 2.0 regarding an inability to configure backup or do Updates inside the ISA firewall?  If so, tell me what I missed.  If not, I can provide ISA transaction logs.  There were mentions elsewhere on this Forum about SBS2003 working with this, but no indication that ISA2004 was in play.  Thanks for any help. <Gary>

    The SBS firewall is likely blocking the traffic from OneCare. I believe that this was the case in the current production version, too. OneCare won't work with any authenticated proxy, but a transparent proxy should allow it to pass through unless the firewall on the server is explicitly blocking the traffic.

    We may see a response in here to help, but I'd recommend contact support and also opening a bug on Connect.

     

     Support for 2.0 Beta - http://help.live.com/help.aspx?project=onecarev2 - use the "Get More Help" link in the lower right of the page to contact support via email.

     

    Please file a bug on Connect: https://connect.microsoft.com/site/sitehome.aspx?SiteID=168

    See the Bug Submission Guide - http://connect.microsoft.com/content/content.aspx?ContentID=3480&SiteID=168 - for details on how to create and submit the Support Log zip file with your bug.

     

    -steve

    Wednesday, September 5, 2007 11:55 PM
    Moderator
  • Both bug reports were submitted.  Thanks Steve.

    <Gary>

     

    Friday, September 7, 2007 11:49 PM
  • Thank-you, Gary. I appreciate getting the bug reports in as that means the developers will get a chance to review the details.

    -steve

     

    Saturday, September 8, 2007 1:32 AM
    Moderator