ProxySG- TCP_NC_MISS- cannot access the application

I need a solution

Hi Team,

When we are accessing the lsapl application (https://egs-lsapl-02.singaporeair.com.sg) we are getting error.

While we are checking those error we found below logs:

PROXIED “none” – 200  TCP_NC_MISS POST  https://egs-lsapl-02.singaporeair.com.sg 8443/ SMTSERVERweb/post services …….

Please find the attached error screenshot for reference.

We have checke below KB articles but we are not sure that the issue related to this(in KB the error for 404 code but in our case its 200)

https://support.symantec.com/en_US/article.TECH242…

Below defined the code:

TCP-NC_miss: The object returned from the origin server was noncacheable

Proxy version: 6.2.15.6

Please advice to proceed further.

Thanks,

Ram.

0

Related:

  • No Related Posts

Citrix Provisioning Services Boot Process

Understanding the Boot process in PVS:

==========================================

When a target device starts it needs to somehow be able to find and contact a provisioning server to eventually stream down the appropriate vDisk.This information is stored in a so-called Bootstrap file named ARDBP32.BIN. It contains everything that the target devcie needs to contact a pVS server so that streaming process can be initialized.

The boot strap file be delivered through a TFTP server, this also partly applies to the alternative BDM(Boot Device Manager)approach. There are some distinct differences between TFTP and BDM

TFTP

When using TFTP , target device needs to know how and where it can find the TFTP server to download the bootstrap file before connecting PVS server. TFTP can be configure in HA through Netscaler to avoid single point of failure. Provisoning services has its own built-in TFTP server. However, we are free to use whatever you prefer.

One of the most popular approach in delivering TFTP server address to your target devices is through DHCP, but there are other option as well..

BDM(Boot Device Manager)

There are actually two different methods to make use of the Boot Device Manager.

Let start with PVS, PVS offers a quick wizard which will generate a relatively small .ISO(around 300KB). Next , you configure your Target devices to boot from this .ISO file, using their CDROM/DVD players. This method uses a two-stage process where the PVS server location will be hardcoded into the bootstrap generated by BDM. The rest of the information like the (PVS device drivers) is downloaded from the PVS server using a TFTP protocol (UDP port 6969), here TFTP will still be used.

As of XenDesktop version 7.x, when using XenDesktop setup wizard we can create and assign a small BDM hard disk partition, which will be attached to the virtual machine as a separate virtual disk. Using this method the above mentioned two-stage approach is no longer needed because partition already contains all the PVS drivers. This way all the information needed will be directly available without the need of PXE,TFTP & DHCP.

Note:

As and added advantage using the BDM method will also decrease the boot time by around 5 to 10 sec since we don’t have to wait for PXE and TFTP

Provisioning Services Boot Process Diagram

https://support.citrix.com/content/dam/supportWS/kA460000000CcClCAK/Provisioning_Services_Boot_Process.pdf

Related:

  • No Related Posts

7022987: Error 4701 “Server services not running”

This document (7022987) is provided subject to the disclaimer at the end of this document.

Environment

Verastream Host Integrator

Situation

  • Connection attempts by a remote client fail with error ID 4701 “Server services not running.”
  • Session server log (viewed in Administrative Console; see also KB 7021303) contains error MessageID 3152 “Allocated session timed out waiting for client connection.”
  • Local connections on the server (such as with SOAP Services tester) work fine.
  • Firewall or device with Network Address Translation (NAT) may be between the server and client, or the server’s machine name may not be resolvable from the client system.

Resolution

With version VHI 7.5 or higher:
  1. Temporarily stop the session server service. (See also KB 7021352.)
  2. Manually edit the %VHI_ROOT%/etc/sesssrvr.config file in a text editor to set the ApptrieveServer > Server property to the fully qualified host name or IP address as the server is known on the client’s side of the network.
  3. Save the edited file and start the session server service.

Cause

The client connector is able to establish the initial connection to the session server to request the session, and the server readies the session and tells the client the address to connect to it, but the client fails to make the secondary connection. That is, the client can’t connect to the address the server told it to use. The session server must be configured to tell clients (connectors, Design Tool, and model deployment utilities) to use a different address.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

  • No Related Posts

The Tftp service is not running on the PVS server


To resolve this issue:

1. Launch the Services console: Click **Start** and then type **Services**.

2. Verify the TFTP Service is present and restart the service: From the Services console, right-click **Citrix PVS TFTP Service** and select **Start**.

3. Check the Event Log for any errors.

For more information, see Starting, stopping, or restarting Provisioning Services in the product documentation

Note: If you are not using the Boot Device Manager boot partition, this service is not required. Click **Hide Alert** to prevent this alert from appearing. You can show this alert again by clicking **Site Options > Show Hidden Alerts**. For more information, see Manage Smart Check alerts and notifications in the product doumentation.

Related:

  • No Related Posts

Re: About emc unity 600 replication

Hi taylan@ln.com.tr

I am very very confused with your post as you talk about FC Ethernet, which doesn’t really exist unless you are talking about FCoE, etc. Otherwise, in this context, it’s either FC or Ethernet.

Unity uses Ethernet for async replication and the management traffic, but sync rep is all of ver FC, not Ethernet.

Looking briefly at your switch it seems to be Ethernet only, not FC. So sync rep will never work here.

If you mean you have Eth setup for the sync management interfaces, and FC for the actual connection, then remember that the FC replication ports are the first FC ports on the system, and these need to be zoned to the other array on your FC switch.

I would recommend starting here:

https://support.emc.com/docu69886_Dell-EMC-Unity:-Replication-Technologies—A-Detailed-Review.pdf?language=en_US

Andre @ Dell EMC

Related:

  • No Related Posts

Cannot create fs_dhsm connection

Hey folks, we recently replaced windows2003DC with windows2016DC,i updated DNS via server_dns,server_cifs

today our vnx cannot add fs_dhsm connection now, see below command result,please give some suggestion genius

cifs share access is not affected

thanks



[nasadmin@wal-vnx-cs01 ~]$ fs_dhsm -connection qa-cifs -create -type cifs -admin ‘qa.arkivio.comadministrator’ -secondary ‘\arkqa2012-15.qa.arkivio.coma$’ -local_server vnxp1.qa.arkivio.com

Enter Password:*******



Error 13158252563: Cannot establish connection between secondary server arkqa2012-15.qa.arkivio.com and local server vnxp1.qa.arkivio.com with share a$ with user qa.arkivio.comadministrator NT status=ACCESS_DENIED c0000022H.

Related:

  • No Related Posts

TCP tunnel requests when a protocol error is detected

I need a solution

Hi guys 

in the transparence mode

When enable  “TCP tunnel requests when a protocol error is detected ” 

– Where to see the tunnel sessions ?

– The tunnel seesions by “TCP tunnel requests when a protocol error is detected ”  can not apply to the policy in VPM correct ? 

When create Service by Source IP address and port | Proxy :TCP Tunnel | Intercept 

– The tunnel seesions can apply to the source  policy in the VPM   but destiantion policy can’t correct  ? 

BR 

PK

0

Related:

  • No Related Posts