However you can specify a custom host ID for Solaris 8 or 9 containers (non-global zone) running in Solaris 10 global zone. This can be done with using the zonecfg -z command. The instructions for changing the hostid for Solaris 10 global and non-global zones is in the bottom half of this article.

myserver # zonecfg -z myzone1
zonecfg:myzone1> add attr
zonecfg:myzone1:attr> set name=123456
zonecfg:myzone1:attr> set type=string
zonecfg:myzone1:attr> set value=”123456″
zonecfg:myzone1:attr> end
zonecfg:myzone1> exit

Stop myzone1

myserver # zonecfg -z myzone1 halt

Start myzone1

myserver # zonecfg -z myzone boot

Check on the status of myzone1

myserver # zonecfg list -vc

Now logon to the console of myzone1 and check the hostid

myserver @ zlogin -C myzone1

After you enter the login ID and password, run the command hostid.

# hostid
123456

Changing the hostid for Solaris 10 global and non-global zones.
Now you know how to change the host id for Solaris 8 and 9 containers. Here is a great script written by Brendan Gregg that can be used to change the host ID for Solaris 10 global and non-global zones. This script must run as a process in the background. Killing this process will revert the host ID to the factory ID imbedded in the hardware.

Cut and paste the below script to a file called zhostid, make the file executable. Change the following lines to refect the host IDs you want.
global 12345678
myzone1 90abcdef

#!/usr/bin/ksh
#
# zhostid – demo changing hostids for Solaris Zones.
# Written using DTrace (Solaris 10 3/05).
#
# WARNING: This is a demonstration of DTrace, it is not intended as a
# standard daemon. In particular, hostids are used by Sun to track support
# calls, so changing hostids may make life somewhat confusing for all.
#
# 21-Jun-2005, ver 0.70 (first release)
#
# USAGE: zhostid &
#
# Edit the “Configuration” section below to set the zones and
# hostids to what is desirable.
#
# BASED ON: hostid.d by Iain Hayes, and idea by Jon Haslam.
#
# COPYRIGHT: Copyright (c) 2005 Brendan Gregg.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place – Suite 330, Boston, MA 02111-1307, USA.
#
# (http://www.gnu.org/copyleft/gpl.html)
#
# 21-Jun-2005 Brendan Gregg Created this.

#
# Configuration
#
hostids=’
global 12345678
myzone1 90abcdef

‘ # simply modify the above by adding extra lines for each zone.

#
# Check hostids
#
print “$hostids” | while read zone hostid_hex; do
### Sanity check hostid
if [[ "$zone" == "" || "$zone" == "#" ]]; then continue; fi
if [[ "$hostid_hex" == *[g-zG-Z]* ]]; then
print “ERROR2: Invalid hostid $hostid_hex. ”
print “Please use hexadecimal.\n”
exit 2
fi
if (( ${#hostid_hex} > 11 )); then
# see /usr/src/uts/common/conf/param.c for limit.
print “ERROR3: Length of hostid $hostid_hex too long. ”
print “Limit 11 chars.\n”
exit 3
fi

### Convert hostid to decimal
typeset -i10 hostid_dec
hostid_dec=16#$hostid_hex

### Build DTrace code
body=”$body
syscall::systeminfo:return
/zonename == \”$zone\” && self->command == 7/
{
copyoutstr(\”$hostid_dec\”, self->buffer, 11);
}”
done

#
# Run DTrace
#
exec /usr/sbin/dtrace -n ‘

#pragma D option destructive
#pragma D option quiet
#pragma D option bufsize=32k

inline string hostid = “‘$hostid_dec’”;

syscall::systeminfo:entry
{
self->command = arg0;
self->buffer = arg1;
}

‘”$body”‘

syscall::systeminfo:return
{
self->command = 0;
self->buffer = 0;
}
‘

Now run the zhostid file in the background as a process. The & option means to run in the background and it will give you back the prompt. This file must be run from the global zone.

myserver # ./zhostid &

Check the host ID with the hostid command.

myserver # hostid
12345678

Logon the the console of myzone1

# zlogin myzone1
[Connected to zone 'myzone1' pts/10]
Last login: Tue Jun 21 03:51:10 on pts/10
Sun Microsystems Inc. SunOS 5.10 Generic January 2005

myzone1 # hostid
90abcdef

clear text. SSH is a secure protocol and is the replacement for telnet. Red Hat recommends that you use SSH to

connect to the server, which is why Telnet is disabled by default. This is why the administrator account root is

not allowed to connect using Telnet by default. However you can also allow the root account to connect via telnet

by editing a file, it is recommended that you use su to logon as root.

Check to see if the correct telnet-server and telnet RPMs installed:

# rpm -qa | grep telnet
telnet-server-0.17-39.el5
telnet-0.17-39.el5

If the telnet-server or telnet packages is not installed, then it can be installed with the RPMs available on the

installation media or use the up2date utility along with your RHN subscription to download and install the

package(s). For example:

# up2date telnet-server telnet

You can also download the telnet rpm from website other than redhat and then use the command rpm -i

telnet-0.17-017-39.el5.rpm to install.

Once you have the telnet package is installed, edit the /etc/xinetd.d/telnet file and change the disable = yes to

read disable = no. See the example below.

{
flags = REUSE
socket_type = stream

wait = no
user = root
server = /usr/sbin/in.telnetd
log_on_failure += USERID
disable = no
}

Turn the Telnet server on using the chkconfig command and then make the service available for immediate use with

the service command. You will need to restart the xinetd service. If xinetd is not already started then the

restart command will start it.

# chkconfig telnet on
# chkconfig xinetd on
# chkconfig –list telnet
telnet on
# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]

The chkconfig command will make the Telnet server available to start the next time the system is rebooted, it will

also start the xinetd service. Telnet is part of the xinetd service.

Now eveyrtime after I reboot my computer the warning message keeps popping up in my screen asking me to check my license registration on line. I know I have a valid license for XP but this was really anoying.

I will list the steps to disable the windows genuine advantage notificaton. First reboot your computer into safe mode, to do that hold down the F8 key while booting up Windows XP.

Make sure to logon with an account that has local administrator privilege. Open the registry editor with regedit.exe. Search for waglogon folder and delete it.

Now search for wga* files in your windows directory and delete them. You are done, reboot and enjoy your computer without the pesky pop up.

Open Exchange System Manager

Go to Administrative Groups – First Administrative Group – Servers – Server_Name – First Storage Group – Mailbox Store – Mailboxes.

This will display all the mailboxes, you can determine the current size of each mailboxes. This screen also provides a quick way to determine basic security auditing information such as, last logon by, logon time and logoff time.

There are many ways to achieve this, NAT, VIP, MIP etc. In this article I will explain NAT (natting) on a Cisco PIX, ASA or router.

First you need to log onto the firewall or router. Enter en (enable) to get into the privilege mode, you will then be prompted for the password. Enter Config T to get into the configure terminal mode. You can now start confguring the network appliance.

Below is what your should see in the running config after you complete the configuration.

static (inside,outside) 172.210.10.10 11.12.13.10 netmask 255.255.255.255 0 0

The above line means that the IP address 172.210.10.10 (outside interface) is mapped to 11.12.13.10 (inside interface). Clients in the outside interface will connect to resources on 11.12.13.10 by referencing the natted (NAT) IP 172.210.10.10.

You also need to configure the access list or policy to allow traffic from the outside interface to flow into the inside interface. The access list then needs to be applied to the outside intefrace.

access-list Allowed_Traffic permit tcp host any host 172.210.10.10 eq www log

The above means that the name of the access list is Allowed_Traffic. Permit TCP traffic from any host to 172.210.10.10, only allow if service request is for www (TCP port 80), and log all traffic.

You then need to apply the access list to the outside interface.

access-group Allowed_Traffic in interface outside