Came across this on/via the sygate website. If you try and navigate to the support pages or user forum you get a Symantec page offering to sell you Norton with the following at the top: I had not seen this before and can find nothing on the web about it. I guess this means its now a dead duck. Which firewall to switch to now?
Re: Symatic killing Sygate NOW No such problems going directly to the Sygate Forums here: http://forums.sygate.com/vb/ Also nothing at the regular Sygate site here: http://sygate.com/ Not sure what you are talking about. Also, even if they discontinued everything tomorrow, there's no reason why you can't keep using Sygate as long as you like if it's working for you.
Re: Symatic killing Sygate NOW You can go directly to the forums - if you know the URL. Interestingly they don't appear to know of their impending demise there either. If you go to sygate.com and follow the top menu support button. You go to http://www.sygate.com/support/index.htm. This includes three links (one in the left menu). These are http://smb.sygate.com/support, http://smb.sygate.com/service_support.htm and http://support.sygate.com/ The latter is for the enterprise products and still works (to a degree). If you follow either of the SMB/Soho Links you are redirected to: http://www.symantecstore.com/dr/v2/...203890&CUR=840&DSP=&PGRP=0&ABCODE=&CACHE_ID=0 This page includes the "announcement" and the offer to sell you Norton. As I am not stupid I do realise I can continue to use the product, BUT we will now never see any updates, fixes or other security issues addressed. We will not even have the forum for users to help each other. Sygate (other than enterprise) is now as dead as most of the other compeditors that symantec has bought out of the business.
Re: Symatic killing Sygate NOW There are several discussions of the possibility since Symantec buying them out that the software might be dropped but no official word yet. The odds are just as good that it will continue as is or be incorporated into one of the symantec products. Just anuther Sygate user. edit: I see from the link it is official now dang ahh well as long as it keeps working.
Re: Symatic killing Sygate NOW There have been no updates to it for a long time anyway. Aside from the old proxy issue, it works fine for the most part. There's no need for updates to something that already works fine. If I needed it, I'd use it as long as it ran on my OS of choice with my network card drivers of choice. No big deal...
Re: Symatic killing Sygate NOW It is sad news indeed. I went to the link immediately above and I see the announcement about everything ending on Nov 30th, 2005, however, I don't see any offer to purchase Norton. Am I blind or missing something(?) Or maybe my ad blocker is hiding it?
Re: Symatic killing Sygate NOW Take a look here: http://www.symantecstore.com/dr/v2/ec_main.entry25?page=SygateList&client=Symantec&sid=49998&CID=203890&CUR=840&DSP=&PGRP=0&ABCODE=&CACHE_ID=203890
Re: Symatic killing Sygate NOW I guess they changed their mind. The header on the webpage clearly contradicts the plan in the October 10th Press Release. They appear to be retaining the Enterprise Products but bining the personal and soho products. Was I really the first user to come across the withdrawal notice - if we can dignify it with that term? Does anyone know when the "its dead" page went up - its a generated page so the timestamp doesn't tell us much. I thought it was strange and checked the net for other mentions and could find none. So I've publicised it on a few forums to try and raise the alert a bit. Even forums.sygate.com had no mention of it.
Re: Symatic killing Sygate NOW Has now: http://forums.sygate.com/vb/showthread.php?threadid=14605 http://forums.sygate.com/vb/showthread.php?threadid=14606 Thanks for your posts KWR. Unbelievably bad support from symantec, if that is really true. According to BRB site firewall poll, Sygate was next up second to ZA in popularity if i remember right. So vast a user base and stopping the forum
Re: Symatic killing Sygate NOW This is to be expected - Symantec already have a product aimed at the personal firewall market so the only point in acquiring Sygate was to gain access to its enterprise products. Personal users are low-margin and high-cost (in support terms) compared to business/enterprise customers so you can expect them to be cast adrift in any acquisition.
Re: Symatic killing Sygate NOW Symantec to Ditch Sygate Firewall http://blogs.washingtonpost.com/securityfix/2005/11/symantec_to_dit.html As of this week, will no longer support any Sygate firewall, i.e. Pro or Free Personal Firewall products. From www.symantecstore.com link in above blog article: Important Notice: Effective November 30th, 2005 all Sygate products and forum support will be discontinued. For technical assistance, please email SMBSupport@Symantec.com. Thank you and we look forward to assisting you with the wonderful line of Symantec products. User Guides for Sygate Personal Firewall and Sygate Personal Firewall Pro are available at the following links: Sygate Personal Firewall Pro User Guide Version 5.5 (1327KB) http://smb.sygate.com/support/userguides/pspf/pspf55_userguide.pdf Sygate Personal Firewall User Guide Version 5.5 (1351KB) http://smb.sygate.com/support/userguides/spf/spf55_userguide.pdf -- Tom
Re: Symatic killing Sygate NOW So how can one update the IDS, after reinstalling or whatever, once they take it offline? Is there any way to do that manually?
Re: Symatic killing Sygate NOW Doubtful.. Probably have to do without the IDS updates, or else just find another product...
Re: Symatic killing Sygate NOW found http://207.33.111.31/spf/spf-ids/on sygate forums thread couldn't that help?
Re: Symatic killing Sygate NOW sellouts, If its the signatures your talking about, http://forums.sygate.com/vb/showthread.php?s=&threadid=14608 Copy sdi.dat and trojan.dat , I'd bet there won't be any new ones. Hope that helps, ParaNodes
Re: Symatic killing Sygate NOW Cool! Yeah I know there won't be any new ones. I just wondered if there was a way to re-install .3044 and that is less painless than I figured it would be. I was guessing there would be registry keys that needed changing at the very least.