Tlisten resolve incorrect IP add on Clustered Servers

Hi All,
I am having a problem in deploying Tuxedo v6.5, as a stand alone application, on
a pair of MS NT 4 clustered servers. The problem is when starting tlisten process
using standard command "tlisten -l //HOSTNAME:12345", tlisten picks up a different
IP addresses every time I start another tlisten process.
i.e. starting three tlisten processes may result in three tlisten processes listening
on three different IP addresses that belongs to the cluster pairs.
My two constrains are:
(1) I need 6 tlistens processes to be started on the same physical machines
(2) my client insist to use Hostname unless it is proven that it is a defacts in
BEA's tlisten
I have investigate with the Network support ppl, and according to them, their DNS
settings seems to be fine (i.e. they suggest that they have only map HOSTNAME to
a single IP address).
Any help would be appreciated.
Regards
Nathan

I added the program under the allowed apps but it still didn't work.
I disabled the firewall but it didn't work either.
Added IP addresses under DNS somewhere, but didn't work.
This would only handle the built-in software firewall that is part of the OS X operating system on your Mac.
I was told I may need to configure access to port numbers and/or server addresses. Certain ports should be open and certain server addresses "added", and it is preferable to configure a firewall by server address instead of IP address. If an IP range exception can be entered, I will need to enter a range of about 100.
By default, all incoming traffic from the Internet is blocked by your router. On the other hand, all solicitated outbound traffic is NOT blocked. Note, however, that the Apple routers do NOT support UPnP. If your application is coded to do so this may be the issue you are seeing. Using a non-Apple router would be one solution.
Opening ports on the Apple router is done via the AirPort Utility. Please check out the following AirPort User Tip for details.

Similar Messages

Resolve.conf, dnsmasq and external DNS servers

I am using dnsmasq to filter out ad urls, so my /etc/resolv.conf looks like that:
# Generated by dhcpcd from wlan0
nameserver 127.0.0.1
domain home
nameserver 192.168.1.254
# /etc/resolv.conf.tail can replace this line
However, it looks like after getting through the url filtration layer of dnsmasq, the URLs are being resolved by a DNS sever of whatever Access Point I am connected to. This create problems, because they often render me unable to connect to services like sourceforge.net, etc.
So, instead of that, I would like my system to fall back to Google and OpenDNS after filtering urls through dnsmasq.
But how can I do that? This is a specific case and wiki does not cover it.
Last edited by Lockheed (2013-05-19 16:50:43)

$ cat /etc/resolv.conf
# Generated by dhcpcd from wlan0
nameserver 127.0.0.1
nameserver 8.8.8.8
domain home
# /etc/resolv.conf.tail can replace this line
The google DNS is what I put in there earlier to be able to use internet after dnsmasq stopped starting.
$ cat /etc/resolvconf.conf
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details
resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
name_servers=127.0.0.1
# Write out dnsmasq extended configuration and resolv files
dnsmasq_conf=/etc/dnsmasq-conf.conf
dnsmasq_resolv=/etc/dnsmasq-resolv.conf
$ cat /etc/dnsmasq.conf
# Configuration file for dnsmasq.
# Format is one option per line, legal options are the same
# as the long options legal on the command line. See
# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.
# Listen on this specific port instead of the standard DNS port
# (53). Setting this to zero completely disables DNS function,
# leaving only DHCP and/or TFTP.
#port=5353
# The following two options make you a better netizen, since they
# tell dnsmasq to filter out queries which the public DNS cannot
# answer, and which load the servers (especially the root servers)
# unnecessarily. If you have a dial-on-demand link they also stop
# these requests from bringing up the link unnecessarily.
# Never forward plain names (without a dot or domain part)
#domain-needed
# Never forward addresses in the non-routed address spaces.
#bogus-priv
# Uncomment this to filter useless windows-originated DNS requests
# which can trigger dial-on-demand links needlessly.
# Note that (amongst other things) this blocks all SRV requests,
# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
# This option only affects forwarding, SRV records originating for
# dnsmasq (via srv-host= lines) are not suppressed by it.
#filterwin2k
# Change this line if you want dns to get its upstream servers from
# somewhere other that /etc/resolv.conf
#resolv-file=/etc/resolv-dnsmasq.conf
# By default, dnsmasq will send queries to any of the upstream
# servers it knows about and tries to favour servers to are known
# to be up. Uncommenting this forces dnsmasq to try each query
# with each server strictly in the order they appear in
# /etc/resolv.conf
strict-order
# If you don't want dnsmasq to read /etc/resolv.conf or any other
# file, getting its servers from this file instead (see below), then
# uncomment this.
#no-resolv
# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
# files for changes and re-read them then uncomment this.
#no-poll
# Add other name servers here, with domain specs if they are for
# non-public domains.
#server=/localnet/192.168.0.1
server=208.67.222.222
server=208.67.220.220
# Example of routing PTR queries to nameservers: this will send all
# address->name queries for 192.168.3/24 to nameserver 10.1.2.3
#server=/3.168.192.in-addr.arpa/10.1.2.3
# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.
#local=/localnet/
# Add domains which you want to force to an IP address here.
# The example below send any host in double-click.net to a local
# web-server.
#address=/double-click.net/127.0.0.1
# --address (and --server) work with IPv6 addresses too.
#address=/www.thekelleys.org.uk/fe80::20d:60ff:fe36:f83
# You can control how dnsmasq talks to a server: this forces
# queries to 10.1.2.3 to be routed via eth1
# server=10.1.2.3@eth1
# and this sets the source (ie local) address used to talk to
# 10.1.2.3 to 192.168.1.1 port 55 (there must be a interface with that
# IP on the machine, obviously).
# [email protected]#55
# If you want dnsmasq to change uid and gid to something other
# than the default, edit the following lines.
#user=
#group=
# If you want dnsmasq to listen for DHCP and DNS requests only on
# specified interfaces (and the loopback) give the name of the
# interface (eg eth0) here.
# Repeat the line for more than one interface.
#interface=lo
# Or you can specify which interface _not_ to listen on
#except-interface=
# Or which to listen on by address (remember to include 127.0.0.1 if
# you use this.)
#listen-address=127.0.0.1
# If you want dnsmasq to provide only DNS service on an interface,
# configure it as shown above, and then use the following line to
# disable DHCP and TFTP on it.
#no-dhcp-interface=
# On systems which support it, dnsmasq binds the wildcard address,
# even when it is listening on only some interfaces. It then discards
# requests that it shouldn't reply to. This has the advantage of
# working even when interfaces come and go and change address. If you
# want dnsmasq to really bind only the interfaces it is listening on,
# uncomment this option. About the only time you may need this is when
# running another nameserver on the same machine.
#bind-interfaces
# If you don't want dnsmasq to read /etc/hosts, uncomment the
# following line.
#no-hosts
# or if you want it to read another file, as well as /etc/hosts, use
# this.
addn-hosts=/etc/hosts.block
#hostsfile=/etc/hosts.block
# Set this (and domain: see below) if you want to have a domain
# automatically added to simple names in a hosts-file.
#expand-hosts
# Set the domain for dnsmasq. this is optional, but if it is set, it
# does the following things.
# 1) Allows DHCP hosts to have fully qualified domain names, as long
# as the domain part matches this setting.
# 2) Sets the "domain" DHCP option thereby potentially setting the
# domain of all systems configured by DHCP
# 3) Provides the domain part for "expand-hosts"
#domain=thekelleys.org.uk
# Set a different domain for a particular subnet
#domain=wireless.thekelleys.org.uk,192.168.2.0/24
# Same idea, but range rather then subnet
#domain=reserved.thekelleys.org.uk,192.68.3.100,192.168.3.200
# Uncomment this to enable the integrated DHCP server, you need
# to supply the range of addresses available for lease and optionally
# a lease time. If you have more than one network, you will need to
# repeat this for each network on which you want to supply DHCP
# service.
#dhcp-range=192.168.0.50,192.168.0.150,12h
# This is an example of a DHCP range where the netmask is given. This
# is needed for networks we reach the dnsmasq DHCP server via a relay
# agent. If you don't know what a DHCP relay agent is, you probably
# don't need to worry about this.
#dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
# This is an example of a DHCP range which sets a tag, so that
# some DHCP options may be set only for this network.
#dhcp-range=set:red,192.168.0.50,192.168.0.150
# Use this DHCP range only when the tag "green" is set.
#dhcp-range=tag:green,192.168.0.50,192.168.0.150,12h
# Specify a subnet which can't be used for dynamic address allocation,
# is available for hosts with matching --dhcp-host lines. Note that
# dhcp-host declarations will be ignored unless there is a dhcp-range
# of some type for the subnet in question.
# In this case the netmask is implied (it comes from the network
# configuration on the machine running dnsmasq) it is possible to give
# an explicit netmask instead.
#dhcp-range=192.168.0.0,static
# Enable DHCPv6. Note that the prefix-length does not need to be specified
# and defaults to 64 if missing/
#dhcp-range=1234::2, 1234::500, 64, 12h
# Do Router Advertisements, BUT NOT DHCP for this subnet.
#dhcp-range=1234::, ra-only
# Do Router Advertisements, BUT NOT DHCP for this subnet, also try and
# add names to the DNS for the IPv6 address of SLAAC-configured dual-stack
# hosts. Use the DHCPv4 lease to derive the name, network segment and
# MAC address and assume that the host will also have an
# IPv6 address calculated using the SLAAC alogrithm.
#dhcp-range=1234::, ra-names
# Do Router Advertisements, BUT NOT DHCP for this subnet.
# Set the lifetime to 46 hours. (Note: minimum lifetime is 2 hours.)
#dhcp-range=1234::, ra-only, 48h
# Do DHCP and Router Advertisements for this subnet. Set the A bit in the RA
# so that clients can use SLAAC addresses as well as DHCP ones.
#dhcp-range=1234::2, 1234::500, slaac
# Do Router Advertisements and stateless DHCP for this subnet. Clients will
# not get addresses from DHCP, but they will get other configuration information.
# They will use SLAAC for addresses.
#dhcp-range=1234::, ra-stateless
# Do stateless DHCP, SLAAC, and generate DNS names for SLAAC addresses
# from DHCPv4 leases.
#dhcp-range=1234::, ra-stateless, ra-names
# Do router advertisements for all subnets where we're doing DHCPv6
# Unless overriden by ra-stateless, ra-names, et al, the router
# advertisements will have the M and O bits set, so that the clients
# get addresses and configuration from DHCPv6, and the A bit reset, so the
# clients don't use SLAAC addresses.
#enable-ra
# Supply parameters for specified hosts using DHCP. There are lots
# of valid alternatives, so we will give examples of each. Note that
# IP addresses DO NOT have to be in the range given above, they just
# need to be on the same network. The order of the parameters in these
# do not matter, it's permissible to give name, address and MAC in any
# order.
# Always allocate the host with Ethernet address 11:22:33:44:55:66
# The IP address 192.168.0.60
#dhcp-host=11:22:33:44:55:66,192.168.0.60
# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"
#dhcp-host=11:22:33:44:55:66,fred
# Always give the host with Ethernet address 11:22:33:44:55:66
# the name fred and IP address 192.168.0.60 and lease time 45 minutes
#dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m
# Give a host with Ethernet address 11:22:33:44:55:66 or
# 12:34:56:78:90:12 the IP address 192.168.0.60. Dnsmasq will assume
# that these two Ethernet interfaces will never be in use at the same
# time, and give the IP address to the second, even if it is already
# in use by the first. Useful for laptops with wired and wireless
# addresses.
#dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.60
# Give the machine which says its name is "bert" IP address
# 192.168.0.70 and an infinite lease
#dhcp-host=bert,192.168.0.70,infinite
# Always give the host with client identifier 01:02:02:04
# the IP address 192.168.0.60
#dhcp-host=id:01:02:02:04,192.168.0.60
# Always give the host with client identifier "marjorie"
# the IP address 192.168.0.60
#dhcp-host=id:marjorie,192.168.0.60
# Enable the address given for "judge" in /etc/hosts
# to be given to a machine presenting the name "judge" when
# it asks for a DHCP lease.
#dhcp-host=judge
# Never offer DHCP service to a machine whose Ethernet
# address is 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,ignore
# Ignore any client-id presented by the machine with Ethernet
# address 11:22:33:44:55:66. This is useful to prevent a machine
# being treated differently when running under different OS's or
# between PXE boot and OS boot.
#dhcp-host=11:22:33:44:55:66,id:*
# Send extra options which are tagged as "red" to
# the machine with Ethernet address 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,set:red
# Send extra options which are tagged as "red" to
# any machine with Ethernet address starting 11:22:33:
#dhcp-host=11:22:33:*:*:*,set:red
# Give a fixed IPv6 address and name to client with
# DUID 00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2
# Note the MAC addresses CANNOT be used to identify DHCPv6 clients.
# Note also the they [] around the IPv6 address are obilgatory.
#dhcp-host=id:00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2, fred, [1234::5]
# Ignore any clients which are not specified in dhcp-host lines
# or /etc/ethers. Equivalent to ISC "deny unknown-clients".
# This relies on the special "known" tag which is set when
# a host is matched.
#dhcp-ignore=tag:!known
# Send extra options which are tagged as "red" to any machine whose
# DHCP vendorclass string includes the substring "Linux"
#dhcp-vendorclass=set:red,Linux
# Send extra options which are tagged as "red" to any machine one
# of whose DHCP userclass strings includes the substring "accounts"
#dhcp-userclass=set:red,accounts
# Send extra options which are tagged as "red" to any machine whose
# MAC address matches the pattern.
#dhcp-mac=set:red,00:60:8C:*:*:*
# If this line is uncommented, dnsmasq will read /etc/ethers and act
# on the ethernet-address/IP pairs found there just as if they had
# been given as --dhcp-host options. Useful if you keep
# MAC-address/host mappings there for other purposes.
#read-ethers
# Send options to hosts which ask for a DHCP lease.
# See RFC 2132 for details of available options.
# Common options can be given to dnsmasq by name:
# run "dnsmasq --help dhcp" to get a list.
# Note that all the common settings, such as netmask and
# broadcast address, DNS server and default route, are given
# sane defaults by dnsmasq. You very likely will not need
# any dhcp-options. If you use Windows clients and Samba, there
# are some options which are recommended, they are detailed at the
# end of this section.
# Override the default route supplied by dnsmasq, which assumes the
# router is the same machine as the one running dnsmasq.
#dhcp-option=3,1.2.3.4
# Do the same thing, but using the option name
#dhcp-option=option:router,1.2.3.4
# Override the default route supplied by dnsmasq and send no default
# route at all. Note that this only works for the options sent by
# default (1, 3, 6, 12, 28) the same line will send a zero-length option
# for all other option numbers.
#dhcp-option=3
# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
#dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5
# Send DHCPv6 option. Note [] around IPv6 addresses.
#dhcp-option=option6:dns-server,[1234::77],[1234::88]
# Send DHCPv6 option for namservers as the machine running
# dnsmasq and another.
#dhcp-option=option6:dns-server,[::],[1234::88]
# Ask client to poll for option changes every six hours. (RFC4242)
#dhcp-option=option6:information-refresh-time,6h
# Set the NTP time server address to be the same machine as
# is running dnsmasq
#dhcp-option=42,0.0.0.0
# Set the NIS domain name to "welly"
#dhcp-option=40,welly
# Set the default time-to-live to 50
#dhcp-option=23,50
# Set the "all subnets are local" flag
#dhcp-option=27,1
# Send the etherboot magic flag and then etherboot options (a string).
#dhcp-option=128,e4:45:74:68:00:00
#dhcp-option=129,NIC=eepro100
# Specify an option which will only be sent to the "red" network
# (see dhcp-range for the declaration of the "red" network)
# Note that the tag: part must precede the option: part.
#dhcp-option = tag:red, option:ntp-server, 192.168.1.1
# The following DHCP options set up dnsmasq in the same way as is specified
# for the ISC dhcpcd in
# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
# adapted for a typical dnsmasq installation where the host running
# dnsmasq is also the host running samba.
# you may want to uncomment some or all of them if you use
# Windows clients and Samba.
#dhcp-option=19,0 # option ip-forwarding off
#dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
#dhcp-option=45,0.0.0.0 # netbios datagram distribution server
#dhcp-option=46,8 # netbios node type
# Send an empty WPAD option. This may be REQUIRED to get windows 7 to behave.
#dhcp-option=252,"\n"
# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
# probably doesn't support this......
#dhcp-option=option:domain-search,eng.apple.com,marketing.apple.com
# Send RFC-3442 classless static routes (note the netmask encoding)
#dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8
# Send vendor-class specific options encapsulated in DHCP option 43.
# The meaning of the options is defined by the vendor-class so
# options are sent only when the client supplied vendor class
# matches the class given here. (A substring match is OK, so "MSFT"
# matches "MSFT" and "MSFT 5.0"). This example sets the
# mtftp address to 0.0.0.0 for PXEClients.
#dhcp-option=vendor:PXEClient,1,0.0.0.0
# Send microsoft-specific option to tell windows to release the DHCP lease
# when it shuts down. Note the "i" flag, to tell dnsmasq to send the
# value as a four-byte integer - that's what microsoft wants. See
# http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true
#dhcp-option=vendor:MSFT,2,1i
# Send the Encapsulated-vendor-class ID needed by some configurations of
# Etherboot to allow is to recognise the DHCP server.
#dhcp-option=vendor:Etherboot,60,"Etherboot"
# Send options to PXELinux. Note that we need to send the options even
# though they don't appear in the parameter request list, so we need
# to use dhcp-option-force here.
# See http://syslinux.zytor.com/pxe.php#special for details.
# Magic number - needed before anything else is recognised
#dhcp-option-force=208,f1:00:74:7e
# Configuration file name
#dhcp-option-force=209,configs/common
# Path prefix
#dhcp-option-force=210,/tftpboot/pxelinux/files/
# Reboot time. (Note 'i' to send 32-bit value)
#dhcp-option-force=211,30i
# Set the boot filename for netboot/PXE. You will only need
# this is you want to boot machines over the network and you will need
# a TFTP server; either dnsmasq's built in TFTP server or an
# external one. (See below for how to enable the TFTP server.)
#dhcp-boot=pxelinux.0
# The same as above, but use custom tftp-server instead machine running dnsmasq
#dhcp-boot=pxelinux,server.name,192.168.1.100
# Boot for Etherboot gPXE. The idea is to send two different
# filenames, the first loads gPXE, and the second tells gPXE what to
# load. The dhcp-match sets the gpxe tag for requests from gPXE.
#dhcp-match=set:gpxe,175 # gPXE sends a 175 option.
#dhcp-boot=tag:!gpxe,undionly.kpxe
#dhcp-boot=mybootimage
# Encapsulated options for Etherboot gPXE. All the options are
# encapsulated within option 175
#dhcp-option=encap:175, 1, 5b # priority code
#dhcp-option=encap:175, 176, 1b # no-proxydhcp
#dhcp-option=encap:175, 177, string # bus-id
#dhcp-option=encap:175, 189, 1b # BIOS drive code
#dhcp-option=encap:175, 190, user # iSCSI username
#dhcp-option=encap:175, 191, pass # iSCSI password
# Test for the architecture of a netboot client. PXE clients are
# supposed to send their architecture as option 93. (See RFC 4578)
#dhcp-match=peecees, option:client-arch, 0 #x86-32
#dhcp-match=itanics, option:client-arch, 2 #IA64
#dhcp-match=hammers, option:client-arch, 6 #x86-64
#dhcp-match=mactels, option:client-arch, 7 #EFI x86-64
# Do real PXE, rather than just booting a single file, this is an
# alternative to dhcp-boot.
#pxe-prompt="What system shall I netboot?"
# or with timeout before first available action is taken:
#pxe-prompt="Press F8 for menu.", 60
# Available boot services. for PXE.
#pxe-service=x86PC, "Boot from local disk"
# Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
#pxe-service=x86PC, "Install Linux", pxelinux
# Loads <tftp-root>/pxelinux.0 from TFTP server at 1.2.3.4.
# Beware this fails on old PXE ROMS.
#pxe-service=x86PC, "Install Linux", pxelinux, 1.2.3.4
# Use bootserver on network, found my multicast or broadcast.
#pxe-service=x86PC, "Install windows from RIS server", 1
# Use bootserver at a known IP address.
#pxe-service=x86PC, "Install windows from RIS server", 1, 1.2.3.4
# If you have multicast-FTP available,
# information for that can be passed in a similar way using options 1
# to 5. See page 19 of
# http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
# Enable dnsmasq's built-in TFTP server
#enable-tftp
# Set the root directory for files available via FTP.
#tftp-root=/var/ftpd
# Make the TFTP server more secure: with this set, only files owned by
# the user dnsmasq is running as will be send over the net.
#tftp-secure
# This option stops dnsmasq from negotiating a larger blocksize for TFTP
# transfers. It will slow things down, but may rescue some broken TFTP
# clients.
#tftp-no-blocksize
# Set the boot file name only when the "red" tag is set.
#dhcp-boot=net:red,pxelinux.red-net
# An example of dhcp-boot with an external TFTP server: the name and IP
# address of the server are given after the filename.
# Can fail with old PXE ROMS. Overridden by --pxe-service.
#dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3
# If there are multiple external tftp servers having a same name
# (using /etc/hosts) then that name can be specified as the
# tftp_servername (the third option to dhcp-boot) and in that
# case dnsmasq resolves this name and returns the resultant IP
# addresses in round robin fasion. This facility can be used to
# load balance the tftp load among a set of servers.
#dhcp-boot=/var/ftpd/pxelinux.0,boothost,tftp_server_name
# Set the limit on DHCP leases, the default is 150
#dhcp-lease-max=150
# The DHCP server needs somewhere on disk to keep its lease database.
# This defaults to a sane location, but if you want to change it, use
# the line below.
#dhcp-leasefile=/var/lib/misc/dnsmasq.leases
# Set the DHCP server to authoritative mode. In this mode it will barge in
# and take over the lease for any client which broadcasts on the network,
# whether it has a record of the lease or not. This avoids long timeouts
# when a machine wakes up on a new network. DO NOT enable this if there's
# the slightest chance that you might end up accidentally configuring a DHCP
# server for your campus/company accidentally. The ISC server uses
# the same option, and this URL provides more information:
# http://www.isc.org/files/auth.html
#dhcp-authoritative
# Run an executable when a DHCP lease is created or destroyed.
# The arguments sent to the script are "add" or "del",
# then the MAC address, the IP address and finally the hostname
# if there is one.
#dhcp-script=/bin/echo
# Set the cachesize here.
#cache-size=150
# If you want to disable negative caching, uncomment this.
#no-negcache
# Normally responses which come from /etc/hosts and the DHCP lease
# file have Time-To-Live set as zero, which conventionally means
# do not cache further. If you are happy to trade lower load on the
# server for potentially stale date, you can set a time-to-live (in
# seconds) here.
#local-ttl=
# If you want dnsmasq to detect attempts by Verisign to send queries
# to unregistered .com and .net hosts to its sitefinder service and
# have dnsmasq instead return the correct NXDOMAIN response, uncomment
# this line. You can add similar lines to do the same for other
# registries which have implemented wildcard A records.
#bogus-nxdomain=64.94.110.11
# If you want to fix up DNS results from upstream servers, use the
# alias option. This only works for IPv4.
# This alias makes a result of 1.2.3.4 appear as 5.6.7.8
#alias=1.2.3.4,5.6.7.8
# and this maps 1.2.3.x to 5.6.7.x
#alias=1.2.3.0,5.6.7.0,255.255.255.0
# and this maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
#alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
# Change these lines if you want dnsmasq to serve MX records.
# Return an MX record named "maildomain.com" with target
# servermachine.com and preference 50
#mx-host=maildomain.com,servermachine.com,50
# Set the default target for MX records created using the localmx option.
#mx-target=servermachine.com
# Return an MX record pointing to the mx-target for all local
# machines.
#localmx
# Return an MX record pointing to itself for all local machines.
#selfmx
# Change the following lines if you want dnsmasq to serve SRV
# records. These are useful if you want to serve ldap requests for
# Active Directory and other windows-originated DNS requests.
# See RFC 2782.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>
# If the domain part if missing from the name (so that is just has the
# service and protocol sections) then the domain given by the domain=
# config option is used. (Note that expand-hosts does not need to be
# set for this to work.)
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 389
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 389 (using domain=)
#domain=example.com
#srv-host=_ldap._tcp,ldapserver.example.com,389
# Two SRV records for LDAP, each with different priorities
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2
# A SRV record indicating that there is no LDAP server for the domain
# example.com
#srv-host=_ldap._tcp.example.com
# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for PTR records.)
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for TXT records.)
#Example SPF.
#txt-record=example.com,"v=spf1 a -all"
#Example zeroconf
#txt-record=_http._tcp.example.com,name=value,paper=A4
# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand
#cname=bertand,bert
# For debugging purposes, log each DNS query as it passes through
# dnsmasq.
#log-queries
# Log lots of extra information about DHCP transactions.
#log-dhcp
# Include a another lot of configuration options.
#conf-file=/etc/dnsmasq-resolvconf.conf
#conf-dir=/etc/dnsmasq.d
domain-needed
interface=lo
# If dnsmasq is compiled for DBus then we can take
# advantage of not having to restart dnsmasq.
enable-dbus
conf-file=/etc/dnsmasq-conf.conf
resolv-file=/etc/dnsmasq-resolv.conf
Logs:
May 23 00:01:06 panzor systemd[1]: Failed to start A lightweight DHCP and caching DNS server.
May 23 00:01:10 panzor dhcpcd[27267]: dhcpcd not running
May 23 00:01:10 panzor kernel: [ 7771.282756] iwl4965 0000:03:00.0: Can't stop Rx DMA.
May 23 00:01:10 panzor dhcpcd[27294]: dhcpcd not running
May 23 00:01:11 panzor dhcpcd[27330]: dhcpcd not running
May 23 00:01:14 panzor dhcpcd[27373]: wlan0: sendmsg: Cannot assign requested address
May 23 00:01:18 panzor dhcpcd[27373]: wlan0: sendmsg: Operation not permitted
May 23 00:01:22 panzor dhcpcd[27395]: wlan0: sendmsg: Operation not permitted
May 23 00:01:26 panzor dhcpcd[27395]: wlan0: sendmsg: Operation not permitted
For domain filtration, if I remember correctly, I am using this
https://bbs.archlinux.org/viewtopic.php?id=139784

TED with Clustered Servers

Hi All,
I am wondering what I need to do or even if TED can, set a package path to a clustered volume path instead of setting the package path of a distributed application to a single file server name?
TED itself is not cluster aware but can it be tricked/manipulated?
eg.
Currently apps come down and the package path changes from:
\\EnterpriseDistributorServer1\APPS1\TheApplicatio nName
To:
\\LocalFileServer1\APPS1\TheApplicationName
As it should and always has with single server sites, however our clustered SAN connected environment is also doing this. Which doesn't take advantage of the clustered servers resilience capabilities at all and renders applications unavailable if LocalFileServer1 goes down.
Instead I want it to go from:
\\EnterpriseDistributorServer1\APPS1\TheApplicatio nName
To:
\\Cluster1\APPS1\TheApplicationName
I want to do this without setting Cluster1 as the package path at the Enterprise level and configuring the distribution to keep the same source path, so our other servers maintain their own versions locally when distributed.
I also don't want to have to create secondary NAL and distribution objects just for the cluster, as I also receive enterprise distributions that I do not control apart from subscribing to.
Any help/ideas would be much appreciated.
Cheers,
Brad

brad,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Can I use Admin Console to Start Clustered Servers ?

 I have just started to look at clustering and am in the process of running through
 the cluster example tutorial. I have used the domain config wizard to create
 a manged server with a cluster and another server to act as the http proxy. As
 I prefer to use the admin console for all tasks I wondered if there is any way
 to start the managed servers from the console. The reason I ask is that I cannot
 find a way to start another server from the console apart from the admin server.
 On a seperate note can anyone tell me whether the multicast IP address is something
 that I should be concerned with as a developer. The reason I ask is that I know
 it is used for clustered servers to communicate, but how can it do that if the
 IP address is a physical box that does not have BEA installed.
 Thanks
 Justin


Yes, you can start all managed servers from the console ... Look under the
 cluser that you create and click on the control tab ... you should be able
 to start all the managed servers that will be apart of the cluster there.
 Weblogic uses a service on the local machine called node manager which will
 start and stop the services on each managed server.
 Its good for developers to know something about multicasting as far as what
 it does, how it works but most system administrators all well versed with
 the inner workings of it. You have to have weblogic installed in order for
 that particular box to become apart of the cluster, and you can run multiple
 managed servers on one physical box but be careful with resource intensive
 apps.
 "Justin Flanagan" <[email protected]> wrote in message
 news:[email protected]...
 >
 > I have just started to look at clustering and am in the process of running
 through
 > the cluster example tutorial. I have used the domain config wizard to
 create
 > a manged server with a cluster and another server to act as the http
 proxy. As
 > I prefer to use the admin console for all tasks I wondered if there is any
 way
 > to start the managed servers from the console. The reason I ask is that I
 cannot
 > find a way to start another server from the console apart from the admin
 server.
 >
 > On a seperate note can anyone tell me whether the multicast IP address is
 something
 > that I should be concerned with as a developer. The reason I ask is that
 I know
 > it is used for clustered servers to communicate, but how can it do that if
 the
 > IP address is a physical box that does not have BEA installed.
 >
 > Thanks
 >
 > Justin
 Outgoing mail is certified Virus Free.
 Checked by AVG anti-virus system (http://www.grisoft.com).
 Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004

Running BizTalk on multiple non-clustered servers. Potential serious issue

Hi,
I have just discovered what has potential to be a fairly large issue in our current BizTalk Architecture. We are running BizTalk Server 2006 R2 on 2 different servers, running Windows Server 2003 R2. These servers are NOT clustered. Instead, BizTalk is installed
to both, configured on 1 and then on the 2nd, they have joined the existing BizTalk environment. We have 1 host with 2 host-instances for say an Orchestration Host. (So 1 Orchestration Host and then 1 Orchestration Host Instance on each server), we also have
a host instance for Receive and Send on each server.
This is a problem that I have identified on an application currently in UAT:
We have a routine called 'Recovery Mode'. It doesn't matter what Recovery Mode is but what does matter is that only a single instance can go into recovery mode at the same time.
Consider this:
bool inRecovery;
while (isBroken) {
if (!inRecovery){
inRecovery = true;
// Recover
inRecovery = false;
else {
// Wait, recheck until not in recovery, or fixed.
Imagine an instance on server 1 needs to go into recovery, it first checks the inRecovery flag, gets returned false so goes into recovery, let's say this takes 5 minutes to complete. During this time, an instance on server 2 needs to go into recovery, checks
the flag, but the flag on server 2 has not been set to true.... Now I have 2 instances in Recovery...
My questions are:
1. Can I cluster 2 non-clustered servers? I'd need to upgrade from Windows Server 2003 R2 Standard to Enterprise is that possible? If so, Can I simply upgrade and cluster the servers or would I need to format the disks?
2. If no to number 1, where would you store the 'inRecovery' flag'? I can't store in a DB as there will be slight cross over where instance 2 might return false in my example just as instance 1 is writing unless I can lock it on write or something.
Some advice would be greatly appreciated.
Thanks
Rod

To answer your specific question:
1. Yes, but you would need to upgrade to at least Enterprise. Windows Server 2003 R2 Standard does not support clustering. IIRC, the upgrade from Standard to Enterprise is pretty easy, perhaps just a SKU change.
2. If you absolutely cannot upgrade Windows Server, then you'd have to store the state externally, such as SQL Server. There shouldn't be any concurrency issues if you do the check in the right sequence. Basically, begin a transaction, attempt
to UPDATE, return weather the UPDATE was successful, meaning that call grabbed the lock. If you check then update, yes, there is a miniscule chance both will return the same value but only one near-sumultaneous UPDATE will succeed.

Verity Issue - Clustered Servers

To summarize:
We have an interesting issue that I am attempting to create a
work around for. Our website exists in a clustered enviorment (3
servers), a development server, and a file server (mostly PDF's
Word docs, PPT's etc...). Each server re-indexes the Verity
collections nightly via scheduled task and the file server does as
well. Since we host our servers in a sercure external enviorment
there is no direct network connection between the clustered servers
and the file server. Our work around for this was, since our
development server can see both, we would:
1) Re-index nightly on the file server
2) Set a scheduled task on the dev server to copy the files
from the collection on the file server to the test enviorment
3) Use our source control to submit these copies to the
clustered servers via scheduled task.
Everything was working great until we upgraded the file
server to MX 7. The collection file structure has changed for
vertity in MX 7 and we cannot output the results on the search
pages. We do plan to upgrade all of our servers to MX 7 but it is
going to take a few months.
We are trying to come up with some ideas as how we can
integrate the results from the file server. (i.e CFHTTP) as we dump
the results from 3 collections into an array and then sort the
relevance.
Any thoughts?
Thanks,
Jon

I'll restate this in simpler fashion.
Can you retrieve MX 7 verity search results on a MX 6.1
server?
Can this be done via CFHTTP or any other similar method?
Thanks

Set logging severity level for clustered servers

How can I set the logging severity level for clustered servers just once at the cluster level rather than one at a time at the server level?

I know the logging is server by server, but surely there is a way to configure the multiple servers with one change rather than one by one. We have 40 some servers in the cluster.

Clustered Servers

I just installed a cluster setup and I'm now trying to test out a web app
that works fine
on a single appserver.
When attempting to access my a servlet within my webapp I get the following
error:
***weblogic.management.NoAccessRuntimeException: user myclient does not have
***access permission on weblogic.admin.mbean.BeaServer1
My webapp is deployed to a 2 server cluster. When I run it on a
non-clustered server, it works fine.
What am I missing??

Hi,
how did you create the cluster nodes ?
Are the SerializedSystemIni.dat file and the initial fileRealm.properties file
identical ?
Regards,
Christian Buchegger
Developer Relations Engineer
BEA Support
Kenneth Chin schrieb:
I have the user 'myclient' defined on all 3 servers.
I just created a new ACL, but when trying to add a Permission, I get the
error
User "system" does not have Permission "modify" based on ACL
"weblogic.admin.acl".
"Christian Buchegger" <[email protected]> wrote in message
news:[email protected]..
Hi,
what I am wondering first when reading the error message is: is the user
myclient defined on any
machine in the cluster ? Does this user have the correct permissions onany
system ?
If the user is defined, you might try to give him the correct permissionstru an
acl like:
acl=weblogic.admin.mbean.(servername) permission=access group=everyone
Regards,
Christian Buchegger
Developer Relations Engineer
BEA Support
Kenneth Chin schrieb:
I just installed a cluster setup and I'm now trying to test out a web
app
that works fine
on a single appserver.
When attempting to access my a servlet within my webapp I get thefollowing
error:
***weblogic.management.NoAccessRuntimeException: user myclient does nothave
***access permission on weblogic.admin.mbean.BeaServer1
My webapp is deployed to a 2 server cluster. When I run it on a
non-clustered server, it works fine.
What am I missing??

Acrobat Pro 11 - how do I add more review servers?

I have reviews in progress, so I do not want to remove the present server. I need to add at least one more server, but I don't see any way to do this, I only see a way to remove servers. What is the procedure for adding servers (this is not in the user manual), and how many can I add?
Thanks

You can add reviewers in Acrobat from Tracker with the following steps:
1. Open Tracker(from View menu).
2. Under Reviews->Sent node on Left hand panel, Click on the review for which you want to add the reviewers.
3. Right hand panel shows the details of that review and options to Add reviewer/Change deadline/End Review etc. Click on the Add Reviewers Option to add reviewers
Or Right clikcing on the review at step 2 also, shows an option for Add reviewers under contextual menu.

Can a single JNDI tree be shared by multiple, non-clustered servers?

We have a situation involving multiple, but non-clustered, WebLogic servers,
say Server 1 and Server 2. A client needs to access an EJB which happens to
be located only on Server 2. We would prefer that the client not need to
know the exact location of the EJB, but use the naming service hosted by a
designated server (Server 1) to locate the EJB.
At a minimum, this would require that both servers bind their respective
EJB's into a common, shared JNDI naming tree hosted by Server 1.
Is this possible?
John Armstrong
WebLink Wireless, Inc.
[email protected]

hi,
I have not tried this, althoug with the webogic rmi and weblogic jndi
implementation I would guess this is straightforward.
Binding remote objects in WL JNDI binds the stubs only, not the object
itself. The worst case scenario here would be for you to implement proxies
and bind them in JNDI, although I would guess that binding the home object
should give you the required functionality.
Just try it, rebind the home object on a different server than the one the
bean is deployed on and test. My guess is that it will work.
(I repeat : I have not tested this my self, this is just a suggestion)
Regards,
Anders M.
John N. Armstrong <[email protected]> skrev i
meldingsnyheter:3a93faba$[email protected]..
We have a situation involving multiple, but non-clustered, WebLogicservers,
say Server 1 and Server 2. A client needs to access an EJB which happensto
be located only on Server 2. We would prefer that the client not need to
know the exact location of the EJB, but use the naming service hosted by a
designated server (Server 1) to locate the EJB.
At a minimum, this would require that both servers bind their respective
EJB's into a common, shared JNDI naming tree hosted by Server 1.
Is this possible?
John Armstrong
WebLink Wireless, Inc.
[email protected]

ITS Login screen behavior different on 2 clustered servers(BBP)-config same

We have a production server(s) for Standalone ITS 6.2 (BBP) with 2 hosts and this is load-balanced and clustered.
The templates for (BBP) bbpstart and bbpglobal for the affected instance are identical on both physical servers.
The services on both the servers are also identical. But yet, Login behaviour on the 2 servers are different.
The servers are :-
Prd:    (Instance) WEP     on server it03 and it04 port 82
URL: http://it03:82/scripts/wgate/bbpstart/!
or URL:
http://it04:82/scripts/wgate/bbpstart/!
Production cluster URL - http://clusterits20:82/scripts/wgate/bbpstart/!
The problem is as follows :-
'The basic issue is that the users have to click on the 'enter' button on the BBP login screen (for server it04) main BBP screen, (hitting/pressing 'Enter' button doesnt work).
But on server IT03 users can just press enter on the login screen on their keyboards for IT03 (server it03) to login ! ..... so depending on which server they connected to within the cluster address they would have to press or click buttons etc to get past the BBP login screen.'
The templates for bbpstart and bbpglobal for the are identical on both physical servers.
The services on both the servers are also identical.
Please advice on how to solve this issue.
Thanks and regards
Avinash
Edited by: Avinash Rajan on Aug 11, 2008 5:33 PM

Hello Avinash,
Did you check the template bbpglobal/99/login.html? That is the actual file being used for the bbpstart service logon screen. The login.html should contain a function for login using the enter (function loginOnEnter(theEvent)). Maybe this is missing from your it04 server?
I would recommend publishing the bbpglobal Internet Service to your it04 server again.
Edgar

How to add osmonitor to servers

Hi all,
 
I have a bunch of galaxy servers installed with our jumpstart server. I would know manage them with N1SM. I can discover those server without any problem but can't enable the osmonitoring. Trying adding this feature always end up with :
 
Result 1: 
Server: xxx.xxx.xxx.xxx 
Status: -3 
Message: Enabling Base Management or OS Monitoring support failed. Check the Standard Output field for possible reasons for this failure. 
Standard Output: 
SunMC driver: getV3 failed: noError,-1 
 
Result 2: 
Server: xxx.xxx.xxx.xxx 
Status: 0 
Message: Failed to enable OS Monitoring support. 
 
 
How can add enable it ?
 
Best regards,

Sorry for the delay - been busy....
Ok, as far as I have been able to find, and in talking with SUN engineering, when you attempt to enable the osmonitor feature, what it actually does is install a Solaris package ( SUNWn1smsparcag-1-2 ) on the managed server.
In this package, a "lite" copy if the SunMC agent get's installed, which is typically what would be installed to enable container manager, but it's not the fully functional copy of SunMC ( SUN Management Center - V3.6.1 ). Either copy uses snmp for it's reporting capabilities, but the full copy is more easily configured to use a defferent port then 161.
My understanding is the lite copy installs as a sub-agent to the SUN native snmpd, so with that, I was a bit misleading in my previous reply.
If you have "net-snmp" installed, you might be able to configure it as a sub-agent to SUN's native snmp and get the osmonitor feature working as well, I haven't tried that combination. Aslo, you can't install the full copy of SunMC on the managed server, then enable the osmonitor feature as it creates it's own port conflict. And if you attempt to install SunMC after enabling the osmonitor feature, you'll get similiar results.
As for modifying the snmpd.conf, in one "raw" attempt I did not have to, ie, clean install of N1 System Manager on my management server as well as a clean install on the managed server without SunMC. Then a discovery, enabled base management, the osmonitor feature and it worked. Also, this was without modifying the snmp model on the managed server, ie, I did not install net-snmp and did not modify any of the SUN snmp configuration files.
Also, keep in mind something, the osmonitor feature when enabled does not give a tremendeous amount of added info so it begs the question "why bother"?
Most shops monitor disk space, cpu and memory use via something similiar to What's up Gold, etc.
As I find more info on the total functional configuration requirements, I'll reply further
Dan

Clustered Servers and Applet (Very URGENT Please)

Hi,
I'm using win2k/CF application server 4.5/IPlanet web server/NN4.79/JRE1.4.1/.
I have an applet in one of my web page which downloads a file from the web server(stored in http://www.abc.net/doc/zip directory on the server).
Now when I run this code on the development server, everything works fine.
But in production environment, we have 3 clustered web servers controlled by a controller (Local Cisco Director) machine. The applet code looks like this:-
strURL = "http://www.abc.net/doc/Zip/"; //the URL from which the zip is to be downloaded. Basically it hits the Controller first
     strZipFileName=getParameter("zipFileName");
     strURL = strURL+strZipFileName;
          //Get Connection to Server and Download the file
          try{
          objUrl = new URL(strURL);
          httpCon = (HttpURLConnection) objUrl.openConnection();
               //DownLoad the File
               InputStream fileInputStrm = httpCon.getInputStream();
               // create a file object which will contain the directory structure to copy in the local machine
               localZipFile = new File(strLocalFilePath+strZipFileName);
               FileOutputStream fileOutStrm = new FileOutputStream(localZipFile);
               int ch;
          while ((ch = fileInputStrm.read()) != -1) {
                    fileOutStrm.write(ch);
               // Close the InputStream, HTTP connection , File stream
          fileInputStrm.close();
          httpCon.disconnect();
          fileOutStrm.close();
Now when the home page of the site is loaded it makes the connection and controller redirects this request to one of the web servers (say 1) which is least loaded.
Now when the applet is loaded, the new connection is established to the controller and it may redirect the request to any one of the 3 web servers (not necessarily to 1 which is required). Now sometimes it hits the right web server on which the required zip file is stored, and sometimes it doesn't hit the correct server.
Any clue what we can do in this scenario so that the applet downloads the correct file from the right server?
Please help it is very urgent....
Thanks

Did you ever get a response to this or figure out how to run in a clustered environment? I am now running into the same issue and would be interested in whatever you learned.

Add existing OVM servers to Ops Center 11g?

We are turning an Ops Center 11g pilot project into production and we need help with our existing OVM Server for SPARC servers. We have a number of OVM 2.2 servers. When we discover them we don't see the VM asset showing in the "All Assets" list. Is there a way to discover the "Oracle VM Server for SPARC" asset that we can then add to virtual pools?
Thanks,

Try this......
Also it shouldn't allow you to add such servers in an OVM Server for SPARC Server Pool.
Here a filter is missing in Ops Center: such servers shouldn't be proposed in the list of assets that can be added to a Server Pool, instead of allowing you to try it and then see an error that can't be understood.
To have a setup with servers that you will be able to add to Server Pools, and on which you will be able to create logical domains from Ops Center, you can either install these servers from Ops Center following the documentation at :
http://docs.oracle.com/cd/E27363_01/doc.121/e27511/ftr_ovm_sparc_mgmt.htm#autoId11 "Installation of Oracle VM Server for SPARC"
or you can install manually the LDoms Virtualization Controller agent on an already installed server.
I think this is not documented for LDoms, the current documentation at http://docs.oracle.com/cd/E27363_01/doc.121/e27511/asset_mgmt.htm#autoId13 "Installing Agent Controllers From the Command Line" will install a Zone Virtualization Controller Agent.
You should first uninstall the current Zone Virtualization Controller agent on your servers, running from the control domain :
$ /var/scn/install/uninstall
then I didn't do it yet manually on S11, I think it should be done as below if someone can confirm or provide the right procedure on S11. Otherwise I'm installing a s11 setup (with an MSR to sync that will take time) and could confirm tomorrow this manual procedure.
It should be similar as in http://docs.oracle.com/cd/E27363_01/doc.121/e27511/asset_mgmt.htm#autoId13
except that the zip to download at step 4 it the IPS zip : OpsCenterAgent.SolarisIPS*.zip
then at step 7, you have to run "install -l -p <proxy IP address>" instead of "install -a"
This step will expect that the S11 version configured on this server matches the version in the MSR you defined in Ops Center.
and at step 10, before running the "agentadm configure..." command, you need to create a file providing network settings :
create a file /opt/sun/n1gc/lib/virtualController.properties with the following content that you should adpat to your host (here for example on my host smt4-24, with IP address 10.166.88.53)
xvmserver.appliancename=smt4-24
network.interface=net0
network.ipaddress=10.166.88.53
network.subnetmask=255.255.255.0
network.defaultgateway=10.166.88.1
then proceed to the agentadm configure command as described at step 10.
After this command has finished, you should have in Ops Center an OVM for SPARC with ldoms management capabilities, allowing you to add this asset to a Server Pool and create logical domains

Unable to resolve name in add user to security group screen

Hello Everybody,
Today I come to ask for advice from the FIM experts, it was just brought to my attention that when somebody tries to add a user to a security group by using the browse option they are able to search for the member and select them but when they
click on "Ok" the account isnt shown in the Members to add box. However if the person types in the full display name into the "members to add box" the user is successfully resolved.

After some intense research this issue is caused by an recent Microsoft update KB3008923. I have opened an microsoft support case after being informed of this issue. This is caused not by an FIM patch but by and internet explorer update. Please uninstall KB3008923
and your issue will be resolved. Or you can suggest to your users to use chrome with IE tab addon enabled as a walk around solution
I am awaiting microsoft to provide an hotfix for this issue but until then I have just instructed my users to do one of the listed tempory solutions above

Tlisten resolve incorrect IP add on Clustered Servers

Similar Messages

Maybe you are looking for