Printers fail to map with errors when using UPS on Windows Server 20122016

The following workaround is available –

Add “LimitRequestLine 8190” in the next line after the “LimitRequestFieldSize 65535” to the httpd.conf file located at:

C:Program Files (x86)CitrixXTEconf

The LimitRequestLine directive decides the limit on the allowed size of HTTP request line (which contains HTTP Method, URI and Protocol version). Since 8190 is the default value, having it in the httpd.conf file should not make any difference.

Related:

  • No Related Posts

Re: Best way to deal with mixed speed network (10Gb & 1Gb)

This worked!

I’ve been working with our VNX 5200s for over a year now trying to figure out why performance was so poor. Even our 7 year old Win2k3 servers were outperforming it.

Our environment is similar – we also have Nexus 5548 core switches with 2k FEX.

I’ve had countless tickets open with EMC techs. No one could point to a resolution. We could see that retransmissions plagued us – between 1-4%, but no one knew what to do about it. EMC technicians would write it off as a misconfigured network. Cisco couldn’t find anything wrong. I finally brought in a wireshark expert to help pinpoint where the problem was – but we couldn’t see any errors other than retransmissions on the link.

I made the change like ebrundick2 suggested “server_param server_2 -facility tcp -modify sndcwnd -value 65535” and rebooted the datamovers. Retranmissions went to almost zero, and CPU went down into the 20% range.

When I told the tech I was going to try this suggestion to modify the sndcwnd value, he was skeptical and said that this “enters into the realm of fine tuning”. Fine tuning it may be – but it fixed our environment.

Thank you for finding this.

Related:

  • No Related Posts

Missing Information Panes in Citrix Director Activity Manager For Users with High Active Directory Group Membership

Create the following reg keys on each DDC in the environment, following which each DDC must be rebooted.

If the below does not work, increase the first value to 65535 as suggested, and reboot each DDC again.

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsaKerberosParameters

Name: MaxTokenSize

Type: REG_DWORD

Data: 48000

(in the event of failure to resolve, increase to 65535)

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesHTTPParameters

Name: MaxFieldLength

Type: REG_DWORD

Data: 65534

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesHTTPParameters

Name: MaxRequestBytes

Type: REG_DWORD

Data: 16777216

The registry keys above are listed elsewhere, but have slightly higher values in this article. There is no known ill-effect of these higher values.

Related:

  • No Related Posts

Re: CEE FIREWALL PORTS for Isilon

So I have the port (12228) frm thje isilon to the CEE server, but then the CEE server sends the data on to Varonis. (in our case).

From Varonis I got this info:

As you confirmed, port 135 is used for the initial call to the CEE/CEPA server.

From there, any one of the ports within the standard dynamic port range is utilized. I may have mentioned before that I can’t speak to why any particular port is selected from that range, but it will always be between 49152 and 65535. In this case we see that the port used is just a bit higher than the low-end of the range.”

Related:

Is there any limit on adding colunm of excel for a test cases in Decision Center?

It seems that there are some limitation for the number of column in Excel of testcase in Decision center ?
If we got too many column , we should be got some issues as following:

Caused by: java.lang.ClassFormatError: JVMCFRE042 bytecode array size > 65535; class=com/ibm/rules/generated/EngineDataClass, offset=149665

![alt text][1]

[1]: /answers/storage/temp/14366-image45a4cfa02f86f155.jpg

Related:

IP-based AUTD has detected that the registry value for the UDP listen port falls outside the allowed range of 1 to 65535, inclusive. As a result, we will proceed with the default UDP listen port of []. To avoid seeing this message in the future, please correct this registry value, or omit it entirely in order to use the default.

Details
Product: Exchange
Event ID: 3021
Source: Server ActiveSync
Version: 6.5.7638.0
Component: Microsoft Exchange ActiveSync
Message: IP-based AUTD has detected that the registry value for the UDP listen port falls outside the allowed range of 1 to 65535, inclusive. As a result, we will proceed with the default UDP listen port of [<number>]. To avoid seeing this message in the future, please correct this registry value, or omit it entirely in order to use the default.
   
Explanation

Exchange ActiveSync detected that the registry value for the User Datagram Protocol (UDP) listen port is not in the allowable range. The default value for this setting is port 2883. You can specify a value between 1 and 65535.

   
User Action

Important  This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the “Restore the Registry” Help topic in Regedit.exe or Regedt32.exe.

To edit the registry to resolve this error:

  1. On the computer running Exchange Server, start Regedit.exe.
  2. Open the following registry key:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MasSync\Parameters

    The registry value name for the UDP listen port is UdpListenPort.

  3. Do one of the following:

    • To return to the default configuration of port 2883, delete the parameter UdpListenPort.
    • To specify a different value for the UDP listen port, right-click UdpListenPort, and then click Modify. In Edit DWORD Value, in Value data, type a value between 1 and 65535.
  4. Close Registry Editor.
  5. Restart Internet Information Services (IIS).

Before you edit the registry, and for information about how to edit the registry, see Microsoft Knowledge Base article 256986, “Description of the Microsoft Windows Registry” (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).

Related: