Support Process for DVD Burning related issues

Network latency and bandwidth can affect user experience and USB device operation when using generic USB redirection for some types of USB devices. Operations that are highly data driven such as for archival devices can be problematic due to multiple factors that lay outside the realm of user configurable settings within Citrix software.

USB Redirection DVD Burning is one of them and relies heavily on a number of things including but limited to:

  • Buffer size
  • Network Latency
  • Write Speed of the device
  • Thin-Client hardware limitations
  • Drivers from the device vendors themselves

Because Citrix cannot modify these limitations we cannot guarantee its functionality past CD Rom functionality. If the DVD Rom is redirected, visible within the OS and can be read and booted from, it is considered to be functioning as expected.

The use of the manufacture driver may be required for further functionality and will need to be explored through the specific manufacture of the DVD Rom itself.

Related:

  • No Related Posts

Error: :Failed to load folder -The folder you are looking for could not be found. on ShareFile Web App while accessing Network shares

You may see following error while accessing Network Shares on ShareFile Web App:

Error message :- Request timed out Failed to load folder -The folder you are looking for could not be found. This can occur if the link you used is incorrect, or if it points to a folder that has been deleted or to which you do not have access. All the users got requested permission.

If you attempt to access the ShareFile network share and it prompts for users credentials. The ShareFile Web App credentials may not work.

Related:

Location awareness not working

I need a solution

Hi,

I want to apply the location-based policy based on the ethernet network connection in SEPM. Like if I’m connected with the certain ethernet connection say ‘XYZ’ than my location changes to say ‘Office’ and when I’m connected with the ethernet say ‘ABC’ my location changes to the home.

I have tried NIC Description where I provided my network SSID and also tried NIC name but no results.
 

0

Related:

  • No Related Posts

Failover issues with SGOS on ESX and Cisco

I need a solution

Hi there,

I’m having an issue with failover on two virtualized Symantec ( Bluecoat) proxies on two ESX hosts in two datacenters connected with Cisco switches.

I can see the Mulicast traffice leaving the proxy getting out into the world over the Cisco switches till the firewall blocks them. The packets should be delivered on L2 to the other switch to get into the other ESX-host on the other proxy running there.

But on the other host I don’t see any multicast-traffic incoming. Hence both feel responsible for the virtual IP what makes problems with Skype etc.

Did anyone have such an issue before? On ESX we activated promiscuous mode already for that vlan/subnet. But that didn’t change the issue.

The hardware proxies in the same network see the multicast-traffic incoming from the virtual machines and behave accordingly. As the virtual proxies don’t receive any multicast traffic they always assume to be master as the other one is not sending any updates.

I would understand that there might be an issue between the two Cisco-Switches that multicast traffic is not forwarded to the other. Other idea is – that there is a special setting on the ESX-Machine I’m not aware of? Any idea?

Thanks in advance,

Manfred

0

Related:

Debugging options for Encryption Management Server Logs

I need a solution

Hi,

I have a ticket open with Symantec Technical Support.  My issue is that my primary SEMS server constantly reports the secondary cluster server as “unreachable” before flipping back to “normal.”  Basically, it’s flipping back and forth all the time.

The “Cluster” log clearly shows that the link is being established, followed by an EOF and the link being dropped.  This repeats itself every few seconds.

The tech I’m working with at Symantec isn’t frankly, the greatest.  He asked me to turn on debugging, and sent me a KB article (https://support.symantec.com/en_US/article.TECH177…) on how to do that by editing the debug.xml log.  The KB says to turn on the debugging options I need, and I kept asking him which ones those are, but he just told me to turn them all on, and leave it for a day (which I have no intention of doing for fear my server will crash sometime in the middle of the night.)

I’m looking at the console, and I see debug logs being created in the “Client,” “Groups,” and “Mail” logs.  However, I DON’T see any debugs being created in the “Cluster” log.

Does anyone know if turning on debugging in this way will actually help with the cluster service?  Or is this tech just wasting my time?

Thank you,

– Steve

0

Related:

Network share encryption with software access.

I need a solution

Hi 

I have file server and couple shared folders that are used by domain users and OCR software that runs from AD user. Is there a way to encrypt this file shares?

When I encrypt shares that are used only by users there all is simple, but how to be when I nedd to service or software use this shares?

0

Related:

Add a seccond endpoint server Fail – Dlp 15.5

I need a solution

Iam testing the version 15.5 and Iike to add another endpoint server but the status in the enforce server is “Unknown”

The single tier server was create in a W2008 and the second endpoint server using a W10 computer.

Additional the W2008 stay in vlan 10.99.220.xxx and the W10 stay in vlan 10.99.116.xxx 

How can be the problem ? I need to do some additional configuration?

0

1553715485

Related:

  • No Related Posts

Vibe 4.0.6 is Now Available!

Nick Scholz

Micro Focus is pleased to announce the general availability of Micro Focus Vibe 4.0.6, the popular framework that allows teams to work together on projects, manage and share documents, and retain knowledge. As a team and workforce productivity platform, Vibe provides a single place for building intranets, collaborating in team and personal workspaces, building landing pages, collaborating on projects, …

+read more

The post Vibe 4.0.6 is Now Available! appeared first on Cool Solutions. Nick Scholz

Related:

  • No Related Posts

Cisco IP Phone 7800 and 8800 Series Cisco Discovery Protocol and Link Layer Discovery Protocol Denial of Service Vulnerability

A vulnerability in the Cisco Discovery Protocol or Link Layer Discovery Protocol (LLDP) implementation for the Cisco IP Phone 7800 and 8800 Series could allow an unauthenticated, adjacent attacker to cause an affected phone to reload unexpectedly, resulting in a temporary denial of service (DoS) condition.

The vulnerability is due to missing length validation of certain Cisco Discovery Protocol or LLDP packet header fields. An attacker could exploit this vulnerability by sending a malicious Cisco Discovery Protocol or LLDP packet to the targeted phone. A successful exploit could allow the attacker to cause the affected phone to reload unexpectedly, resulting in a temporary DoS condition.

There are no workarounds that address this vulnerability.

This advisory is available at the following link:
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190220-cdp-lldp-dos

Security Impact Rating: Medium

CVE: CVE-2019-1684

Related: