New ZCM 11.2.2 Monthly Update 2 installation
Primary server #1 on Win2k8 R2 64-bit
server named McDConsLLC-S02
MS SQL 2008 running on primary #1 (no, not recommended, but it's a 10 +/- device lab installation - not expecting much conflict)
Primary Server #2 on SLES 11 SP2
server named McDConsLLC-S03
Port 1433 opened on Win2k8 firewall for SQL access from Primary #2
/etc/hosts edited to include both servers (see below)
Attempting ZRS 11 SP1 installation on Primary #2 (Linux)
Error in install GUI -
As noted, hosts file has been edited appropriately:
I can ping both servers by IP and machine name from the S03 Linux server so yes, the servers can be resolved through DNS or the hosts file. There is no authoritative source in the environment, though when setting up the static IP for the SLES server it wouldn't let me get away without adding a domain name (even though there isn't one). So "consultbruce.com" is configured there, but hasn't appeared to be used anywhere else.
Thoughts and constructive guesses most welcome!
Primary server #1 on Win2k8 R2 64-bit
server named McDConsLLC-S02
MS SQL 2008 running on primary #1 (no, not recommended, but it's a 10 +/- device lab installation - not expecting much conflict)
Primary Server #2 on SLES 11 SP2
server named McDConsLLC-S03
Port 1433 opened on Win2k8 firewall for SQL access from Primary #2
/etc/hosts edited to include both servers (see below)
Attempting ZRS 11 SP1 installation on Primary #2 (Linux)
Error in install GUI -
Unresolved Hostname - McDConsLLC-S03 could not be reached. Check if the machine is on network and McDConsLLC-S03 can be resolved through DNS or through the host file (etc/hosts)
As noted, hosts file has been edited appropriately:
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.0.24 McDConsLLC-S02 McDConsLLC-S02
192.168.0.25 McDConsLLC-S03 McDConsLLC-S03
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.0.24 McDConsLLC-S02 McDConsLLC-S02
192.168.0.25 McDConsLLC-S03 McDConsLLC-S03
I can ping both servers by IP and machine name from the S03 Linux server so yes, the servers can be resolved through DNS or the hosts file. There is no authoritative source in the environment, though when setting up the static IP for the SLES server it wouldn't let me get away without adding a domain name (even though there isn't one). So "consultbruce.com" is configured there, but hasn't appeared to be used anywhere else.
Thoughts and constructive guesses most welcome!