Reserve Port for BES Client for DNS Servers (Windows 2008/2008 R2)
Log In or Register to download the BES file, and more.

0 Votes

Description


In some situations, the DNS service may bind to the same port as the Tivoli Endpoint Manager Client. This will cause a Socket Error on the Client and prevent it from communicating properly with the rest of the deployment making it unable to receive messages from the Tivoli Endpoint Manager Server or Relay.


The default task will change ephemeral port range to exclude the Tivoli Endpoint Manager Client port used in your deployment (default of port 52311) by moving the range to above that port.


A secondary task is available allowing you to specify a different range if this range does not work for your environemnt which will be validated against the port the client is using.


Note: Due to where the setting is stored, we cannot examine the success of this action. Please record that the event has taken place as this fixlet will remain relevant on systems with a running DNS server.


Property Details

ID300
TitleReserve Port for BES Client for DNS Servers (Windows 2008/2008 R2)
Category<Unspecified>
Download Size0
SourceBigFix
Source ID<Unspecified>
Source Severity<Unspecified>
Source Release Date11/22/2011 12:00:00 AM
KeywordsClient DNS port Tivoli Endpoint
Added by on 10/17/2012 1:14:45 PM
Last Modified by on 10/17/2012 1:14:45 PM
Counters 6195 Views / 0 Downloads
User Rating 1 star 2 star 3 star 4 star 5 star * Average over 0 ratings. ** Log In or Register to add your rating.

Relevance

Used in 223 fixlets   * Results in a true/false
Show indented relevance
(if exists property "in proxy agent context" then ( not in proxy agent context ) else true )
Used in 92 fixlets and 24 analyses   * Results in a true/false
Show indented relevance
version of client >= "5.1"
Used in 24 fixlets   * Results in a true/false
Show indented relevance
((if (version of client >= "8.0") then (windows of it) else (name of it starts with "Win")) AND platform id of it != 3) of operating system
Used in 1 fixlet   * Results in a true/false
Show indented relevance
((product type of it != nt workstation product type) AND (major version of it = 6)) of operating system
Used in 2 fixlets   * Results in a true/false
Show indented relevance
exists running service "DNS"

Actions

Action 1 (default)

Action Link Click here to move the ephemeral port range to above the port the client is using.
Script Type BigFix Action Script
waithidden netsh interface ipv4 set dynamicport udp start={(value "ListenPort" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\GlobalOptions" of registry as integer + 1) as string} num={(65535 - (value "ListenPort" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\GlobalOptions" of registry as integer + 1)) as string}
Success Criteria

This action will be considered successful when the applicability relevance evaluates to false.

Action 2

Action Link Click here to choose the ephemeral port range.
Script Type BigFix Action Script
action parameter query "STARTPORT" with description "Enter the starting port number of the range to permit" with default value "52312"
action parameter query "RANGE" with description "Enter the number of ports after the starting port to permit" with default value "13223"
continue if {exists parameter "STARTPORT"}
continue if {exists parameter "RANGE"}
// If failure on the next line then your range exceeds the maximum 65535
continue if {((parameter "STARTPORT" as integer) + (parameter "RANGE" as integer)) <= 65535}
// If failure on the next line then the start port or range selected doesn't protect the port the client is using
continue if {((parameter "STARTPORT" as integer) > (value "ListenPort" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\GlobalOptions" of registry as integer)) | (((parameter "STARTPORT" as integer) + (parameter "RANGE" as integer)) < (value "ListenPort" of key "HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\GlobalOptions" of registry as integer))}
waithidden netsh interface ipv4 set dynamicport udp start={parameter "STARTPORT"} num={parameter "RANGE"}
Success Criteria

This action will be considered successful when the applicability relevance evaluates to false.

Action 3

Action Link Click here to view Microsoft KB Article 956188, which describes how the DNS service may cause problems when selecting random ports and how to work around the issue.
Script Type URL
http://support.microsoft.com/kb/956188/
    

Sharing

Social Media:
Share this page on Yammer

Comments

Log In or Register to leave comments!