Quantcast
Channel: Symantec Connect - Products - Discussions
Viewing all 18527 articles
Browse latest View live

Need assistance installing file share encryption

$
0
0
I need a solution

I have been trying for over an hour to install file share encryption with no luck.  I originally attempted to download the three files that appeared and one downloaded but I don't know where it is or what it is called.  How do I get access set up?  I can be reached at 225-299-3955 in the U.S.

Leslie Jones

leslie.jones@amedisys.com

0

Blue Coat Systems 800 Series User Manual Required

$
0
0
I need a solution

I would like to request the user manual for the Blue Coat 800 Series device.  We need the instructions on how to open the device and remove the internal hard drives for proper disposal.

0

Block and Allow Specific Email user

$
0
0
I need a solution

Hi All,

i need advice

i want to create Policy in DLP,

 "email employee@company.comcan only send email to some external email "

can DLP do that?

Thanks,

Ali Zainal

0

Azure login issue (TECH237159) - anything on the roadmap to fix this?

$
0
0
I need a solution

Hi,

I am hitting the issue that is documented in the TECH237159.  The solution provided by the tech article is to log out of AzureAD and log back in.  The issue is that if a Windows 10 PC is workplace joined/AzureAD joined the user is always logged in.  The only way to access the SEPC managment console is by starting a private browser session and even then I have to enter my userID in two different places before it logs in.  The rest of the product is pretty slick but this part just feels very clunky and has room for improvement.  Are there any plans to fix this issue in future releases of SEPC?

Thanks

Rob

0

IP Blocked by messagelabs:501 Connection rejected by policy [7.7]

$
0
0
I need a solution

Hello,

We try to send email to domains that use messagelabs system and receiving errors like the ones listed below:

  host cluster8.us.messagelabs.com [216.82.241.196]
    SMTP error from remote mail server after initial connection:
    501 Connection rejected by policy [7.7] 4607, please visit www.messagelabs.com/support for more details about this error message.

Try checking ip at  http://ipremoval.sms.symantec.com/lookup/ but ip not list as negative 

  The IP address you submitted, 103.22.181.103, does not have a negative reputation and therefore cannot be submitted for investigation.

Sending IP: 103.22.181.103

Recipient domains: apl.com, th.kline.com

Please help unblock/delist asap.

Thanks in advance.

0

Question about information flow

$
0
0
I need a solution

Hello guys,

Recently we have installed Symantec ATP endpoint. I have the following question that I would like help:

The clients (SEP endpoint clients) communicate with the ATP appliance only when there is a need for file upload to Cynic or the clients communicate regularly in order to send info to the appliance?

Kind regards,

0

mailserver blacklist removal

$
0
0
I need a solution

we have recently had all email messages from our clients sent to messagelabs assistants returned .

It looks like you have blacklisted our email server ip address.

I can not see any reason for this as i have checked all common blacklists and reputation checks and our ip address seems fine.

message received is :

: host

    cluster1.eu.messagelabs.com[195.245.230.83] refused to talk to me: 501

    Connection rejected by policy [7.7] 20813, please visit

    www.messagelabs.com/support for more details about this error message.

is it possible that you can delist our ip

The server is hosting.fyldecomputersolutions.co.uk  164.132.783.157

The RIPE ip address is registered to Fylde Computer Solutions ltd

122 Victoria Road West

Thornton Cleveleys

Lancashire

FY5 3LG

UK

0

501 Connection rejected by policy [7.7] - 13 days

$
0
0
I need a solution

We are currently being blocked by Message labs.

I submited an investigation here: https://support.symantec.com/en_US/article.TECH828... almost 13 days ago with no replys.

I have checked mxtoolbox & symantec's blacklist checks and we are not black listed.

I have also attempted to phone Symantec support however they can't raise a case as I'm not a symantec customer.

Example logs:

Dec  7 00:45:04 mx1 postfixpool_1/smtp[11065]: 4D5FF7CF1ED: to=<Roger.Milton@moore-scarrott.co.uk>, relay=cluster5.eu.messagelabs.com[193.109.254.3]:25, delay=25705, delays=25704/0.5/0.14/0, dsn=4.0.0, status=deferred (host cluster5.eu.messagelabs.com[193.109.254.3] refused to talk to me: 501 Connection rejected by policy [7.7] 18405, please visit www.messagelabs.com/support for more details about this error message.)

Dec  6 00:18:49 mx1 postfixpool_1/smtp[47437]: E6D467CF660: to=<Roger.Milton@moore-scarrott.co.uk>, relay=cluster5.eu.messagelabs.com[85.158.138.179]:25, delay=25578, delays=25578/0.04/0.35/0, dsn=4.0.0, status=deferred (host cluster5.eu.messagelabs.com[85.158.138.179] refused to talk to me: 501 Connection rejected by policy [7.7] 16909, please visit www.messagelabs.com/support for more details about this error message.)

I URGENTLY need this issue resolved as currently we are relaying all of our email through a temporary IP range which we will soon lose access to.

Please advise the quickest way to get this issue resolved and also to find out why we are being blocked to ensure we can prevent this from happening again.

0

Having to turn SEP off to run windows updates on Server 2012 R2

$
0
0
I need a solution

I currently have 14.0 MP1 on my servers.

Windows update fails unless I disable SEP.

Is this corrected in 14.0.1 RU1?

0

Warning 3900 DLP Console

$
0
0
I need a solution

Hello,

I have an alert in my DLP Enforce 

Code 3900

When I review the Aggregator.log can see this

2017-12-17 15:36:45.354  TC - Unexpected exception                                                        0  Write failed.                                     

Connection specific medium frequency logs for connection number = 17309 and 'AIRE_ACOND'.

will someone know the meaning of that?

0

SDCSSS IPS and IDS Registry Filter Drivers being blocked by Windows Program Compatibility Assistant

$
0
0
I need a solution

Hi Team

I have installed a DCS Agent  6.7 MP2 on Windows 2016 Standard  and just noticed that the Windows Program Compatibility Assistant is blocking the installation of SDCSS IDS Registry Filter and IPS Drivers.

Based on the current KB it was not possible to find something around this error and the DCS Agent (similar situations happened with SEP 12.1.6 MP8 / Per TECH246824)

I'm assuming that a 6.7 MP3 potentially will fix this error but in the meantime seems that a workaround could be: Disabling Secure Boot

Does anybody have something better than that?

Best Regards

0

Stable SGOS version for ASG-S400-20

$
0
0
I need a solution

Can someone let me know which is the stable SGOS version for the model ASG--S400-20

0

Unable to get virus definitions to install

$
0
0
I need a solution

I have SEP 14 installed on Windows 2012.  This is a computer that does not connect to the internet.  I downloaded the latest definitions file (I've tried both 32-bit and 64-bit just in case), but the updater fails every time.  I've checked the boards and my dlls are set correctly.  How do I solve this?  The application is there but has no definitions at this point.  Thank you.

Wed Dec 20 22:20:23 2017 : ******************************************************************
Wed Dec 20 22:20:23 2017 : Starting Intelligent Updater - Version 5.1.7.21
Wed Dec 20 22:20:23 2017 : ******************************************************************
Wed Dec 20 22:20:23 2017 : AUTH SYMSIGNED BEGIN: Started.
Wed Dec 20 22:20:23 2017 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Wed Dec 20 22:20:23 2017 : AUTH SYMSIGNED CLASS3: Finding code signing : TRUE.
Wed Dec 20 22:20:23 2017 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Wed Dec 20 22:20:23 2017 : IU RES SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the iuResource DLL
Wed Dec 20 22:20:23 2017 : IU RES LOAD: Successfully loaded the resource file..
Wed Dec 20 22:20:23 2017 : CONFIG LOAD SUCCESS: Successfully loaded the configuration file: iuConfig.xml.
Wed Dec 20 22:20:23 2017 : IU INFO: File-name : 20171220-008-Core16v5i32.EXE
Wed Dec 20 22:20:23 2017 : IU INFO: Creation-date : 20171220
Wed Dec 20 22:20:23 2017 : AUTH DLL LOCATION: IU will read the DLL SAVIUAuth location from registry.
Wed Dec 20 22:20:24 2017 : REG FAILURE: Failed while opening the key  from registry. Return code: 2
Wed Dec 20 22:20:24 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:24 2017 : REG SUCCESS: Succeeded while fetching the path from registry.
Wed Dec 20 22:20:24 2017 : AUTH DLL: DLL found for Entry number 0.
Wed Dec 20 22:20:24 2017 : Identified as 32-bit product installation. Continuing...
Wed Dec 20 22:20:24 2017 : IU MODE: IU is running is FULL mode.
Wed Dec 20 22:20:26 2017 : CONFIG LOAD SUCCESS: Successfully loaded the configuration file: iuConfig.xml.
Wed Dec 20 22:20:26 2017 : IU INFO: File-name : 20171220-008-Core16v5i32.EXE
Wed Dec 20 22:20:26 2017 : IU INFO: Creation-date : 20171220
Wed Dec 20 22:20:26 2017 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Wed Dec 20 22:20:26 2017 : Entry details:
Wed Dec 20 22:20:26 2017 : Update-File: VIRSCAN.zip
Wed Dec 20 22:20:26 2017 : Update-Desc: Virus Definitions
Wed Dec 20 22:20:26 2017 : Auth DLL Name: SAVIUAuth
Wed Dec 20 22:20:26 2017 : Auth DLL Location: local
Wed Dec 20 22:20:26 2017 : Auth Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy DLL Name: SAVIUDeploy
Wed Dec 20 22:20:26 2017 : Deploy DLL Location: local
Wed Dec 20 22:20:26 2017 : AUTH DLL LOCATION: IU will read the DLL location from registry - SAVIUAuth
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Succeeded while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - SAVIUDeploy
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Succeeded while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED BEGIN: Started.
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED CLASS3: Finding code signing : TRUE.
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the authorization dll C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.3752.1000.105\Bin\LuAuth.dll
Wed Dec 20 22:20:26 2017 : AUTH LOAD SUCCESS: Successfully loaded the authorization dll - C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.3752.1000.105\Bin\LuAuth.dll
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED BEGIN: Started.
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED CLASS3 BEGIN: Entering CriticalSection Initialization .
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED CLASS3: Finding code signing : TRUE.
Wed Dec 20 22:20:26 2017 : AUTH SYMSIGNED END: Finished processing. Returns TRUE
Wed Dec 20 22:20:26 2017 : DEPLOY SYMSIGNED SUCCESS: Successfully verified Symantec Signature for the deployment dll C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.3752.1000.105\Bin\DuLuCbk.dll
Wed Dec 20 22:20:26 2017 : DEPLOY LOAD SUCCESS: Successfully loaded the deployment dll - C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.3752.1000.105\Bin\DuLuCbk.dll
Wed Dec 20 22:20:26 2017 : AUTHORIZATION FAILED: VIRSCAN.zip is not authorized for deployment. Error code : 104
Wed Dec 20 22:20:26 2017 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because it is not authorized for deployment
Wed Dec 20 22:20:26 2017 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Wed Dec 20 22:20:26 2017 : Entry details:
Wed Dec 20 22:20:26 2017 : Update-File: VIRSCAN.zip
Wed Dec 20 22:20:26 2017 : Update-Desc: Virus Definitions
Wed Dec 20 22:20:26 2017 : Auth DLL Name: ISAuthDLL
Wed Dec 20 22:20:26 2017 : Auth DLL Location: local
Wed Dec 20 22:20:26 2017 : Auth Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy DLL Name: ISDeployDLL
Wed Dec 20 22:20:26 2017 : Deploy DLL Location: local
Wed Dec 20 22:20:26 2017 : AUTH DLL LOCATION: IU will read the DLL location from registry - ISAuthDLL
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - ISDeployDLL
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Wed Dec 20 22:20:26 2017 : The product corresponding to this entry in iuconfig.xml is not installed on the system.
Wed Dec 20 22:20:26 2017 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Wed Dec 20 22:20:26 2017 : Entry details:
Wed Dec 20 22:20:26 2017 : Update-File: VIRSCAN.zip
Wed Dec 20 22:20:26 2017 : Update-Desc: Virus Definitions
Wed Dec 20 22:20:26 2017 : Auth DLL Name: Norton X32 AuthDLL
Wed Dec 20 22:20:26 2017 : Auth DLL Location: local
Wed Dec 20 22:20:26 2017 : Auth Content-Type: VirusDefs
Wed Dec 20 22:20:26 2017 : Deploy Content-Type: VirusDefs
Wed Dec 20 22:20:26 2017 : Deploy DLL Name: Norton X32 DeployDLL
Wed Dec 20 22:20:26 2017 : Deploy DLL Location: local
Wed Dec 20 22:20:26 2017 : AUTH DLL LOCATION: IU will read the DLL location from registry - Norton X32 AuthDLL
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - Norton X32 DeployDLL
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Wed Dec 20 22:20:26 2017 : The product corresponding to this entry in iuconfig.xml is not installed on the system.
Wed Dec 20 22:20:26 2017 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Wed Dec 20 22:20:26 2017 : Entry details:
Wed Dec 20 22:20:26 2017 : Update-File: VIRSCAN.zip
Wed Dec 20 22:20:26 2017 : Update-Desc: Virus Definitions
Wed Dec 20 22:20:26 2017 : Auth DLL Name: SSEIUAuth
Wed Dec 20 22:20:26 2017 : Auth DLL Location: local
Wed Dec 20 22:20:26 2017 : Auth Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy DLL Name: SSEIUDeploy
Wed Dec 20 22:20:26 2017 : Deploy DLL Location: local
Wed Dec 20 22:20:26 2017 : AUTH DLL LOCATION: IU will read the DLL location from registry - SSEIUAuth
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - SSEIUDeploy
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Wed Dec 20 22:20:26 2017 : The product corresponding to this entry in iuconfig.xml is not installed on the system.
Wed Dec 20 22:20:26 2017 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Wed Dec 20 22:20:26 2017 : Entry details:
Wed Dec 20 22:20:26 2017 : Update-File: VIRSCAN.zip
Wed Dec 20 22:20:26 2017 : Update-Desc: Virus Definitions
Wed Dec 20 22:20:26 2017 : Auth DLL Name: SSEIUAuth
Wed Dec 20 22:20:26 2017 : Auth DLL Location: local
Wed Dec 20 22:20:26 2017 : Auth Content-Type: csapi_defs
Wed Dec 20 22:20:26 2017 : Deploy Content-Type: csapi_defs
Wed Dec 20 22:20:26 2017 : Deploy DLL Name: SSEIUDeploy
Wed Dec 20 22:20:26 2017 : Deploy DLL Location: local
Wed Dec 20 22:20:26 2017 : AUTH DLL LOCATION: IU will read the DLL location from registry - SSEIUAuth
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - SSEIUDeploy
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Wed Dec 20 22:20:26 2017 : The product corresponding to this entry in iuconfig.xml is not installed on the system.
Wed Dec 20 22:20:26 2017 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Wed Dec 20 22:20:26 2017 : Entry details:
Wed Dec 20 22:20:26 2017 : Update-File: VIRSCAN.zip
Wed Dec 20 22:20:26 2017 : Update-Desc: Virus Definitions
Wed Dec 20 22:20:26 2017 : Auth DLL Name: SMSDOMIUAuth
Wed Dec 20 22:20:26 2017 : Auth DLL Location: local
Wed Dec 20 22:20:26 2017 : Auth Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy DLL Name: SMSDOMIUDeploy
Wed Dec 20 22:20:26 2017 : Deploy DLL Location: local
Wed Dec 20 22:20:26 2017 : AUTH DLL LOCATION: IU will read the DLL location from registry - SMSDOMIUAuth
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - SMSDOMIUDeploy
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Wed Dec 20 22:20:26 2017 : The product corresponding to this entry in iuconfig.xml is not installed on the system.
Wed Dec 20 22:20:26 2017 : PROCESSING ENTRY: VIRSCAN.zip - Virus Definitions
Wed Dec 20 22:20:26 2017 : Entry details:
Wed Dec 20 22:20:26 2017 : Update-File: VIRSCAN.zip
Wed Dec 20 22:20:26 2017 : Update-Desc: Virus Definitions
Wed Dec 20 22:20:26 2017 : Auth DLL Name: SMSMSEIUAuth
Wed Dec 20 22:20:26 2017 : Auth DLL Location: local
Wed Dec 20 22:20:26 2017 : Auth Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy Content-Type: virus definitions x32
Wed Dec 20 22:20:26 2017 : Deploy DLL Name: SMSMSEIUDeploy
Wed Dec 20 22:20:26 2017 : Deploy DLL Location: local
Wed Dec 20 22:20:26 2017 : AUTH DLL LOCATION: IU will read the DLL location from registry - SMSMSEIUAuth
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : DEPLOY DLL LOCATION: IU will read the DLL location from registry - SMSMSEIUDeploy
Wed Dec 20 22:20:26 2017 : REG SUCCESS: Success while opening key 
Wed Dec 20 22:20:26 2017 : REG FAILURE: Failed while fetching the path from registry.
Wed Dec 20 22:20:26 2017 : IGNORE ENTRY: Ignoring entry for VIRSCAN.zip because of registry read failure. Error occurred while reading the path for the Authorization DLL from the registry.
Wed Dec 20 22:20:26 2017 : The product corresponding to this entry in iuconfig.xml is not installed on the system.
0

Seems to be a cryptominer attack ?

$
0
0
I need a solution

We have discovered on one of our Redhat linux server (6.0) ...2 services that are running and utilizing 400-500 % of the CPU....and resurfacing again even after killing the processes...This server is running ORACLE applications...we doubt it might be triggered because of the application have some flaw.

Process names : watch-smartd & carbon

On checking the FW logs below IPs' were found to which the server was trying to communicate to on port 80 : we blocked the same on the FW :

176.31.117.82
37.59.51.212
46.105.103.169
 

These Trojan infection got associated with application and using the service account to associated with application for their communication and other actions. So that might hinder RCA.

YOur thoughts >??

0

Technical comparison sheet

$
0
0
I need a solution

i need comparison sheet between symantec Endpont DLP and Trend Micro DLP

0

ASG Best Practice

$
0
0
I need a solution

Dear Support,

What is the best practice to give Hostname to ASG device like hypen,Aplha numeric and so on.

Whether that hostname can we give to join domain ?

0
1513856252

Proxy ASG | License install invalid

$
0
0
I need a solution

Dear All Concerned,

  Please help to check license file i have download from license portal but after install license it invalid component license still not update about expiration date.

you can see picture as below.

after included license file  and check on appliance component license still not update and do following KB still not update.

now i'm contact to customer care still waiting response. because old license will expire 26 DEC 2017

Thank you everyone for your help.

0

LiveUpdate System Requirements

$
0
0
I need a solution

Hi All,

I am about to requires a server for a new LiveUpdate Administrator instance and looking at the documentation for LiveUpdate Administrator 2.3.6 I cannot see any CPU or RAM requirements it only has Disk space Requirements.

https://symwisedownload.symantec.com//resources/sites/SYMWISE/content/live/SOLUTIONS/134000/TECH134809/en_US/LiveUpdate%20Administrator%20Getting%20Started%20Guide%202.3.6_EN.pdf?__gda__=1513984468_5691badfe615577dc493b972752387ad

I was wondering if it is safe to assume that the 2.3.6 requirements would be the same as the 2.3.1 and 2.3.2 which is?

Hardware

3.2 GHz Intel Pentium 4 CPU or equivalent.

1 GB of RAM minimum (2 GB of RAM recommended), in addition to the amount recommended by the operating system vendor.

0

ProxySG - Simulate User Traffic

$
0
0
I need a solution

Hi All,

has there anyway we can simulate user traffic in Proxy SG ? has any 3rd party tools are available ?

Thanks in Advance..

0

Proxy SG license failed to install

$
0
0
I need a solution

We are trying to reinstall the license for a ProxySG SGOS 5.3.2.1 (I know very old) , but he license file keeps failing.

We keep getting the following:” % Licensing: Could not validate license key.”

The license file was downloaded directly from Symantec.

The License is perpetual with no expiration date, so far we tried the following:

1. Retrieve license through the web manager

2. Change password as recommended by Symantec.

3. did  a file install from CLI.

5. did  a text install.

Nothing worked.... does anyone have any suggestions ...appreciate any help on this.

0
Viewing all 18527 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>