Search

Ads

Saturday, October 24, 2009

Some of The Best Uses Of Laptops

Installing Terminal Sevices on Windows Server 2003

Installing Terminal Sevices on Windows Server 2003.

Things You'll Need:

  • A computer with Windows Server 2003 installed correctly, knowledgeable of Windows Terminal Services and Server, network access.
Instructions:
  1. Step 1

    The first step is to create a Terminal Services Server so that our clients can connect to the server either through application or data. In our case we are going to be initializing applications remotely which works great with Terminal Services.

  2. Step 2

    Select Start--> Control Panel--> Add/Remove Programs.

  3. Step 3

    Click the option that is labeled Add/Remove Windows Components.

  4. Step 4

    The components wizard will start automatically, scroll down the list until you come to the Terminal Server option, click the checkbox next to this option. Click Next to proceed.

  5. Step 5

    The Terminal Services Server setup page will appear. You should be presented information notifying you that certain applications may not work properly after installing Terminal Services in Terminal Server mode and that you will need Terminal Servicing Licensing configured within 120 days. Click the Next button.

  6. Step 6

    The Security settings page for the Terminal Services Server will now appear and from here you can select full security or relaxed security. Select the Relaxed Security option then click Next.

  7. Step 7

    The Licensing server settings page will now appear. If you don’t already have terminal services licensing, select I will specify a license within 120 days option, otherwise select one of the other available options.

  8. Step 8

    The Terminal Server setup page for licensing mode settings will appear. Select either Per Device or Per User and then click Next to continue.

  9. Step 9

    The appropriate files will be copied from the Windows Server 2003 distribution cd and the complete Windows Components wizard page will appear, click Finish.

  10. Step 10

    The System savings change page will appear briefly then ask you to reboot your computer, click Yes.

One of the Best topics of Net Admins ever on Net: Port Numbers And Their functions

List of frequently seen TCP and UDP ports and what those meant for

The goal of this port table is to point to further resources for more information.
------------ --------- --------- --------- --------- --------- --------- ---------
0
1 tcpmux
3
4
5 rje
7 echo
9 discard
11 systat
13 daytime
15 netstat
17 qotd
18 send/rwp
19 chargen
20 ftp-data
21 ftp
22 ssh, pcAnywhere
23 Telnet
25 SMTP
27 ETRN
29 msg-icp
31 msg-auth
33 dsp
37 time
38 RAP
39 rlp
40
41
42 nameserv, WINS
43 whois, nickname
49 TACACS, Login Host Protocol
50 RMCP, re-mail-ck
53 DNS
57 MTP
59 NFILE
63 whois++
66 sql*net
67 bootps
68 bootpd/dhcp
69 Trivial File Transfer Protocol (tftp)
70 Gopher
79 finger
80 www-http
87
88 Kerberos, WWW
95 supdup
96 DIXIE
98 linuxconf
101 HOSTNAME
102 ISO, X.400, ITOT
105 cso
106 poppassd
109 POP2
110 POP3
111 Sun RPC Portmapper
113 identd/auth
115 sftp
116
117 uucp
118
119 NNTP
120 CFDP
123 NTP
124 SecureID
129 PWDGEN
133 statsrv
135 loc-srv/epmap
137 netbios-ns
138 netbios-dgm (UDP)
139 NetBIOS
143 IMAP
144 NewS
150
152 BFTP
153 SGMP
156
161 SNMP
175 vmnet
177 XDMCP
178 NextStep Window Server
179 BGP
180 SLmail admin
199 smux
210 Z39.50
213
218 MPP
220 IMAP3
256
257
258
259 ESRO
264 FW1_topo
311 Apple WebAdmin
350 MATIP type A
351 MATIP type B
360
363 RSVP tunnel
366 ODMR (On-Demand Mail Relay)
371
387 AURP (AppleTalk Update-Based Routing Protocol)
389 LDAP
407 Timbuktu
427
434 Mobile IP
443 ssl
444 snpp, Simple Network Paging Protocol
445 SMB
458 QuickTime TV/Conferencing
468 Photuris
475
500 ISAKMP, pluto
511
512 biff, rexec
513 who, rlogin
514 syslog, rsh
515 lp, lpr, line printer
517 talk
520 RIP (Routing Information Protocol)
521 RIPng
522 ULS
531 IRC
543 KLogin, AppleShare over IP
545 QuickTime
548 AFP
554 Real Time Streaming Protocol
555 phAse Zero
563 NNTP over SSL
575 VEMMI
581 Bundle Discovery Protocol
593 MS-RPC
608 SIFT/UFT
626 Apple ASIA
631 IPP (Internet Printing Protocol)
635 mountd
636 sldap
642 EMSD
648 RRP (NSI Registry Registrar Protocol)
655 tinc
660 Apple MacOS Server Admin
666 Doom
674 ACAP
687 AppleShare IP Registry
700 buddyphone
705 AgentX for SNMP
901 swat, realsecure
993 s-imap
995 s-pop
999
1024
1025
1050
1062 Veracity
1080 SOCKS
1085 WebObjects
1100
1105
1114
1227 DNS2Go
1234
1243 SubSeven
1338 Millennium Worm
1352 Lotus Notes
1381 Apple Network License Manager
1417 Timbuktu
1418 Timbuktu
1419 Timbuktu
1420
1433 Microsoft SQL Server
1434 Microsoft SQL Monitor
1477
1478
1490
1494 Citrix ICA Protocol
1498
1500
1503 T.120
1521 Oracle SQL
1522
1524
1525 prospero
1526 prospero
1527 tlisrv
1529
1547
1604 Citrix ICA, MS Terminal Server
1645 RADIUS Authentication
1646 RADIUS Accounting
1680 Carbon Copy
1701 L2TP/LSF
1717 Convoy
1720 H.323/Q.931
1723 PPTP control port
1731
1755 Windows Media .asf
1758 TFTP multicast
1761
1762
1808
1812 RADIUS server
1813 RADIUS accounting
1818 ETFTP
1968
1973 DLSw DCAP/DRAP
1975
1978
1979
1985 HSRP
1999 Cisco AUTH
2000
2001 glimpse
2005
2010
2023
2048
2049 NFS
2064 distributed. net
2065 DLSw
2066 DLSw
2080
2106 MZAP
2140 DeepThroat
2301 Compaq Insight Management Web Agents
2327 Netscape Conference
2336 Apple UG Control
2345
2427 MGCP gateway
2504 WLBS
2535 MADCAP
2543 sip
2565
2592 netrek
2727 MGCP call agent
2766
2628 DICT
2998 ISS Real Secure Console Service Port
3000 Firstclass
3001
3031 Apple AgentVU
3052
3128 squid
3130 ICP
3150 DeepThroat
3264 ccmail
3283 Apple NetAssitant
3288 COPS
3305 ODETTE
3306 mySQL
3352
3389 RDP Protocol (Terminal Server)
3520
3521 netrek
3879
4000 icq, command-n-conquer
4045
4144
4242
4321 rwhois
4333 mSQL
4444
47017
4827 HTCP
5000
5001
5002
5004 RTP
5005 RTP
5010 Yahoo! Messenger
5050
5060 SIP
5135
5150
5190 AIM
5222
5353
5400
5500 securid
5501 securidprop
5300
5423 Apple VirtualUser
5555
5556
5631 PCAnywhere data
5632 PCAnywhere
5678
5800 VNC
5801 VNC
5900 VNC
5901 VNC
5843
6000 X Windows
6112 BattleNet
6050
6499
6500
6502 Netscape Conference
6547
6548
6549
6666
6667 IRC
6670 VocalTec Internet Phone, DeepThroat
6699 napster
6776 Sub7
6968
6969
6970 RTP
6971
7000
7007 MSBD, Windows Media encoder
7070 RealServer/QuickTim e
7161
7323
7777
7778 Unreal
7640
7648 CU-SeeMe
7649 CU-SeeMe
7654
8000
8002
8010 WinGate 2.1
8080 HTTP
8100
8181 HTTP
8383 IMail WWW
8765
8875 napster
8888 napster
8890
9000
9090
9200
9704
9669
9876
9989
10008 cheese worm
10752
12345
11371 PGP 5 Keyserver
12346
13000
13223 PowWow
13224 PowWow
14000
14237 Palm
14238 Palm
14690
16969
18888 LiquidAudio
21157 Activision
22555
22703
22793
23213 PowWow
23214 PowWow
23456 EvilFTP
26000 Quake
27000
27001 QuakeWorld
27010 Half-Life
27015 Half-Life
27374
27444
27665
27910
27960 QuakeIII
28000
28001
28002
28003
28004
28005
28006
28007
28008
30029 AOL Admin
30100
30101
30102
30103
30303
30464
31335
31337 Back Orifice
32000
32771
32777 rpc.walld
34555
40193 Novell
41524 arcserve discovery
45000 Cisco NetRanger postofficed
50505
52901
54321
61000
65301
Multicast hidden
ICMP Type hidden
9998
32773 rpc.ttdbserverd
32776 rpc.spray
32779 rpc.cmsd
38036 timestep


Keep praying for me and put your hands together to make this group ""ONE OF THE BEST"" Networking groups.

You think Subnetting is a beast. Best post for MCSE And CCNA Professionals

You think Subnetting is a beast?

You think you have to be Superbrain to understand it?

You are wrong!

Here the step-by-step course.
After reading and some self-training, you should be able to fix Subnetting-Question s in CCNA Exam
without any problems in a snatch.
Relax!

What is a Subnetmask?

With Subnetmasks, we can divide an IP-Address in network-part and in host-part.
A given IP-Network can be divided in smaller parts. Each of this smaller parts is called a "Subnet".

If we for example have the network

192.168.10.0 255.255.255. 0

We have here ONE Class C - network, with 253 useable IPs for Client-PCs.


The useable IP Range of this network is

192.168.10.1 - 192.168.10.254

The very last IP of each Subnet is called Broadcast-Address.
This address is in that example 192.168.10.255 and its NOT useable for host-pcs.

If we want to divide this network in two parts, we must use subnetting.

With Subnetmask 255.255.255. 128 we would divide the network in two parts.

192.168.10.1 - 192.168.10.127

192.168.10.128 - 192.168.10.255


0 Reduced: 72% of original size [ 800 x 508 ] - Click to view full image



So in this example, BEFORE we had one big Network.
With the change of the Subnetmask we did divide it in two smaller networks.

First with Subnetmask 255.255.255. 0 we had THIS network:
192.168.10.0 >>> This is the "Network-IP" which is NOT useable for Host-PCs

192.168.10.1
192.168.10.2
192.168.10.3
192.168.10.4
192.168.10.5
...
...
...
192.168.10.253
192.168.10.254
192.168.10.255 >>>This is the Broadcast-IP, which is NOT useable for Host-PCs

Now with Subnetmask 255.255.255. 128 we have THIS two networks:

First Subnet:

192.168.10.0 >>> This is the "Network-IP" which is NOT useable for Host-PCs

192.168.10.1
192.168.10.2
192.168.10.3
192.168.10.4
192.168.10.5
...
...
...
192.168.10.125
192.168.10.126
192.168.10.127 >>>This is the Broadcast-IP, which is NOT useable for Host-PCs

Second Subnet:

192.168.10.128 >>> This is the "Network-IP" which is NOT useable for Host-PCs

192.168.10.129
192.168.10.130
192.168.10.131
192.168.10.. 132
192.168.10.133
...
...
...
192.168.10.253
192.168.10.254
192.168.10.255 >>>This is the Broadcast-IP, which is NOT useable for Host-PCs

The Subnetmask defines how big the subnet is.
That means - how many Client-PCs will have place in that subnetwork.

A Subnetmask of 255.255.255. 0 means in binary

11111111.11111111. 11111111. 00000000

So, what do we see?

4 Blocks, divided with a ".". Each of these blocks is also called "octett". Because - each Block has 8 bits.

To be able to do subnet-calculation, we first must understand binary calculation.

Lets take the first block.

The first "1" stands for a 128.

The second "1" stands for a 64.

The third "1" stands for a 32.

The fourth "1" stands for a 16.

The fifth "1" stands for a 8.

And so on. That means:

11111111=255

11110000=240

11100000=224

If we see something like "/24", that means that 24 bits are set to "1", from the left side.

Examples:

/16 = 255.255.0.0 = 11111111.11111111. 00000000. 00000000

/20 = 255.255.240. 0 = 11111111.11111111. 11110000

If we would take a subnetmask of 255.255.255. 255 that would be

128+64+32+16+ 8+4+2+1.128+ 64+32+16+ 8+4+2+1.128+ 64+32+16+ 8+4+2+1.
128+64+32+16+ 8+4+2+1

and in binary it would be

11111111.11111111. 11111111. 11111111

Calculation of Subnetmask big enough for a specified number of Hosts

If they ask..

"create a subnet with minimum 10 host IPs"

than

1. calculate a power of two, that is minimum 10

2^3=8. That is not enough
2^4=16 That is higher than 10. Good.


2. Now put the LAST 4 Bits of your subnetmask to 0.

11111111.11111111. 11111111. 11110000

That is in decimal

255.255.255. 240

With THIS Subnetmask, you have minimum 10 Host-Ips in the Subnet, without wasting to much IP-Addresses.

------------ --------- --------- --------- --------- --------- ---
Other example

If they ask

Create a subnet with minimum 70 Host-IPs

1. Calculate a Power of 2 that is MINIMUM 70

2^6=64. Not enough.
2^7=128. Thats higher than 70. Good.

2. Put the LAST 7 Bits of your Subnetmask to 0.

11111111.11111111. 11111111. 10000000

That is in decimal

255.255.255. 128

You have a Subnetmask, with more than 70 Host-IPs.


------------ --------- --------- --------- --------- --------- --------- -------

Calculation what is the Broadcast-IP of a Subnet

When they ask
"There is subnet 172.16.64.0/ 20. What is the BROADCAST ADDRESS of that Subnet, dude?"



1. Step

/20 meens 255.255.240. 0

2. Step

Now analyze the Subnet Oktett to find out the "network-jumps"

240 means 11110000

The LAST of the 1s is under decimal 16. That are our "network jumps"
(128/64/32/16/ 8/4/2/1)
3. Step

Write down the network-jumps


172.16.64.0 - 172.16.79.255
+16 172.16.80.0 - 172.16.95.255
+16 172.16.96.0 - 172.16.111.255
+16 172.16.112.0 - 172.16.127.255

Because the NEXT Subnet in the example is 172.16.80.0, the broadcast must be 172.16.79.255, cause THAT is the IP BEFORE the next Subnet starts = the BroadcastAddress.



------------ --------- ---


Other example of Broadcast-IP calculation:

If it would be 172.16.64.0 /26

Same procedure

/26 means 255.255.255. 192


192 is binary 11000000
The LAST 1 stands under the 64. That are in that example our "net-jumps".

172.16.64.0 - 172.16.64.63 <<
172.16.64.64 - 172.16.64.127
172.16.64.128 - 172.16.64.191


------------ --------- --------- --------- --------- --------- --------- ---

Calculating first and last possible IP for a Host

You have Network 192.168.20.32 /27
The very first IP is reserved for Default Gateway!
What is the first and last valid IP for a Host-PC?

1.Step

/27 is 255.255.255. 224

2.Step

224 means 11100000

The LAST 1 is under the 32. That are our "network-jumps" in this example
(128/64/32/16/ 8/4/2/1)

Valid IPs in that subnet:
192.168.20.33 - 192.168.20.62
(192.168.20. 63 is NOT useable, this is the very last IP and so the BROADCAST-IP) .
192.168.20.64 <<

So, because the very first IP is reserved for Default Gateway, our first Host-PC IP would be
192.168.20.34
The very last Host-PC IP would be
192.168.20.62

############ ######### ######### ######### ######### ######### ######### #

Here some examples of real exam questions, and step by step solutions:


Given that you have a class B IP address network range, which of the subnet masks
below will allow for 100 subnets with 500 usable host addresses per subnet?
A. 255.255.0.0
B. 255.255.224. 0
C. 255.255.254. 0
D. 255.255.255. 0
E. 255.255.255. 224

Solution:

Allways the same game... Like in 5 minute course..

Power of 2 that is minimum 500?
2^7=128
2^8=256
2^9=512 >>voila!

Now - put the last 9 Bits of your Subnetmask to "0"

11111111.11111111. 11111110. 00000000

That is in decimal
255.255.254. 0


============ ========= ========= ========= ========= ========= ========= ===
If a host on a network has the address 172.16.45.14/ 30, what is the address of the
subnetwork to which this host belongs?
A. 172.16.45.0
B. 172.16.45.4
C. 172.16.45.8
D. 172.16.45.12
E. 172.16.45.18

Solution:

172.16.45.14/ 30

/30 means 11111111.11111111. 11111111. 11111100

The last of the ones stands under the "4". That is our increment or network jump.
172.16.45.0 - 172.16.45.3
172.16.45.4 - 172.16.45.7
172.16.45.8 - 172.16.45.11
172.16.45.12 - 172.16.45.15
172.16.45.16 - 172.16.45.19

As we see, the Ip is in the Range of 172.16.45.12 - 172.16.45.15.
So the network Address is 172.16.45.12

============ ========= ========= ========= ========= =
QUESTION NO: 9
Which two of the addresses below are available for host addresses on the subnet
192.168.15.19/ 28? (Select two answer choices)
A. 192.168.15.17
B. 192.168.15.14
C. 192.168.15.29
D. 192.168.15.16
E. 192.168.15.31
F. None of the above

Solution:

/28 means 11111111.11111111. 11111111. 11110000

The last 1 stands under the 16. This is increment or network-jumps.

192.168.15.0 - 192.168.15.15
192.168.15.16 - 192.168.15.31
192.168.15.32 - 192.168.15.47

Only A and C are IPs in the right range.
Also E is in the right range. But - this is not useable for hosts, cause its broadcastaddress.
So answer is A and C.

############ ######### ######### ######### ######### ######### #######

------------ --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- -

Calculation of Wildcard-Masks (Needed for Access Lists and OSPF Configuration)

You have Network 192.168.32.0 /28
Only THIS network should be denied of accessing a network or server.

1. Step
calculate the wildcard mask

/28 means 255.255.255. 240

binary this is

11111111.11111111. 11111111. 11110000

For wildcard-mask only the ZEROS are interesting.

11110000 Make a addition of all the fields, that are set to zero

128/64/32/16/ 8/4/2/1
That is 8+4+2+1=15

So the wildcard-mask will be
0.0.0.15

access-list will be

access-list 1 deny 192.168.32.0 0.0.0.15
access-list 1 permit ip any any

now, we have to bind that access-list to a routerinterface. In the example, this is e0.

interface e0
ip access-group 1 out (or in!)
exit

------------ --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- --------- -


PS.

Its good to write on a BIG paper the powers of 2

2^2=4
2^3=8
2^4=16
2^5=32
2^6=64
2^7=128
2^8=256
2^9=512
2^10=1024
2^11=2048
2^12=4096

And write on that paper the numbers

128 192 224 240 248 252 254

Cause this are the Numbers, you will allways need in calculating Subnets.

Burn them in your mind! Hang the paper in front of your eyes to never forget them.
Then you will be able to calculate Subnets in your head in a half second!

Isnt live easy?

What Are BLADE SERVERs, A Major Component of a Network

BLADE SERVER

A blade server is a server chassis housing multiple thin, modular electronic circuit boards, known as server blades. Each blade is a server in its own right, often dedicated to a single application. The blades are literally servers on a card, containing processors, memory, integrated network controllers, an optional fiber channel host bus adaptor (HBA) and other input/output (IO) ports.

Blade servers allow more processing power in less rack space, simplifying cabling and reducing power consumption. According to a SearchWinSystems. com article on server technology, enterprises moving to blade servers can experience as much as an 85% reduction in cabling for blade installations over conventional 1U or tower servers. With so much less cabling, IT administrators can spend less time managing the infrastructure and more time ensuring high availability.

Each blade typically comes with one or two local ATA or SCSI drives. For additional storage, blade servers can connect to a storage pool facilitated by a network-attached storage (NAS), Fiber Channel, or iSCSI storage-area network (SAN). The advantage of blade servers comes not only from the consolidation benefits of housing several servers in a single chassis, but also from the consolidation of associated resources (like storage and networking equipment) into a smaller architecture that can be managed through a single interface.

A blade server is sometimes referred to as a high-density server and is typically used in a clustering of servers that are dedicated to a single task, such as:

  1. File sharing
  2. Web page serving and caching
  3. SSL encrypting of Web communication
  4. The transcoding of Web page content for smaller displays
  5. Streaming audio and video content
Like most clustering applications, blade servers can also be managed to include load balancing and failover capabilities.


Blade Servers in the Enterprise



The market for blade servers has finally caught up with the buzz that surrounds them. Blades are one way to cram more into less space, and they also allow for more effective hardware management. This article examines the types of features are available and touches on the difference between what the Big Four vendors in this space offer.

Blade Servers, Described

What is a blade server, you ask? A standard rack can fit 42U (units) of space, which means you can install 42 1U servers per rack. Assuming you have the power and cooling capacity, that is. A blade server starts with a chassis, which normally provides power and cooling for all the servers that will be inserted. Which components live on which part (chassis vs. each blade) is dependent on the manufacturer and wildly varies.

For example, if a 42U rack can house six 7U chassis that each contain 14 slots for servers, an 82-server density is possible. Some configurations, especially those with taller racks, allow for more than 100 servers each. The capacity increase is enough to persuade many enterprises to buy a blade server, but there are other important benefits to converting.

Depending on the manufacturer, many features accommodate ease of management. Most blade servers integrate the standard server components: networking, KVM, and power and cooling. Determining what level of integration actually was implemented is a per-server and per-vendor challenge. In the networking department, most blade servers have optional gigabit and Fibre Channel switch modules. Only one (or more for redundancy or throughput) connection is required per-chassis if the particular chassis supports networking. Similarly, an entire blade server consisting of 14 servers can connect to a SAN with only two fabric ports being used.

On the power and cooling front, many blade servers use two 2000W (or higher) power supplies. Many of these require 3-phase 240V power, which is an implementation consideration for data centers that don't have this type of power. The advantage is that 3-phase power operates much more efficiently. You can power a full chassis with much less power than is required to run 14 1U servers. The cooling is also centralized per-chassis, so less power is consumed turning high-speed fans within each server.

The Players

Although no longer the undisputed leader in the server blade market, IBM still commands a strong presence. IBM BladeCenter servers are available in three varieties. For all three, IBM's approach is to implement power and cooling in the chassis. Each server is a distinct real-life server, complete with CPU, RAM and hard drives. With the optional Fibre Channel or gigabit network blades, network infrastructure can be consolidated. IBM offers two different blade chassis that are quite similar. The standard BladeCenter allows 14 blades, which can be filled with mixed-and-matched IBM POWER or AMD Opteron servers.

Where the two similar BladeCenter servers differ is their target markets. One is aimed squarely at the midrange; the other, called the BladeCenter H Chassis, is geared toward enterprise operations. The H provides beefier power supplies and adds Infiniband capabilities. Both are suitable for high-performance computing, business applications and database applications. The third option, the BladeCenter T-series chassis, is specifically designed for telecommunications applications.

HP shares the top spot with IBM in the blade space. Its BladeSystem server options cover a variety of HP ProLiant servers and are available with both Xeon and Opteron processors. In July, HP introduced its C-class blade infrastructure as the successor to its p-class line.

The older p-class line offers several power options (e.g., a 1U and 3U additional chassis that enable customers to select their desired capacity and optional Cisco gigabit Ethernet card that provides real switch functionality on-chassis). HP plans to continue selling the p-Class through 2007, and it will offer service and support through 2012.

HP boasts that compared to the p-Class, its BladeSystem c-Class blades are simpler to manage, consume less energy and have more bandwidth in the backplane. Result: Each 17-inch box can hold as many as 16 servers or storage devices.

c-Class blade options include the latest and greatest in processors, as well. In August, the OEM announced a 2-socket blade and a 4-socket blade available with the AMD Opteron Rev F. processors.

Dell is a recent entrant on the current blade landscape. Its PowerEdge 1955 is a blade chassis that accepts 10 servers in a 7U footprint. Each blade can be a 2-processor Intel Xeon server, with up to 146GB of storage. Dell's Web site lists a host of market focuses, each with a "1" next to it. Selecting e-business, database, high-performance computing or Web services all lead to the 1955 server, indicating Dell claims the server is suitable for all applications.

Egenera, however, offers a completely different kettle of fish. Both its ES and EX line of blade servers provide a virtualized computing environment. The ES is designed for more light-weight applications, while the EX is ready to take on the most daunting computational loads. Of course, networking and storage (SAN) access is handled in the same way.

Each blade in the Egenera chassis becomes a pool of resources that every operating system can access. The pool is called a Processing Area Network (PAN), and the operating system isn't aware it exists. The control blades virtualize everything, allowing multiple operating systems to run concurrently and share resources in the PAN. Since the processors themselves are virtualized, you can mix and match Opteron and Xeon boards, and pull them at any time for maintenance while the system is running. Linux, Windows, and Solaris 10 are all supported.

Why Blade Servers, Anyway?

Total cost of ownership, return on investment, yada yada yada. But the reality is that blade servers really do save tremendous amounts of space, power and administrative time dealing with hardware. In the case of the traditional blade server, where one operating system runs on each blade, not much is saved in terms of configuration maintenance because the same number of operating systems must be tended to. The management advantage is realized when the same number of administrators can easily handle twice as many servers as before because less time is spent dealing with hardware issues.

As virtualization of all types becomes more prevalent, hopefully more vendors will start making blade servers that provide a virtual server environment. The additional flexibility gained from a virtualized architecture enables IT organizations to approach the marketing claims of traditional blade systems.

Making Win XP Genuine without using any Cracks

1) Open Notepad
2) Paste the following info in codes:

CODE
Windows Registry Editor Version 5.00

[HKEY_LOCAL_ MACHINE\SOFTWARE \Microsoft\ Windows NT\CurrentVersion]
"CurrentBuild" ="1.511.1 () (Obsolete data - do not use)"
"ProductId"= "55274-640- 7450093-23464"
"DigitalProductId" =hex:a4,00, 00,00,03, 00,00,00, 35,35,32, 37,34,2d, 36,34,30, 2d,\
37,34,35,30, 30,39,33, 2d,32,33, 34,36,34, 00,2e,00, 00,00,41, 32,32,2d, 30,30,30, \
30,31,00,00, 00,00,00, 00,00,62, fc,61,4c, e0,26,33, 16,05,d3, 54,e7,a0, de,00,00, \
00,00,00,00, 49,36,c2, 49,20,47, 0c,00,00, 00,00,00, 00,00,00, 00,00,00, 00,00,00, \
00,00,00,00, 00,00,00, 00,00,00, 00,33,33, 35,30,30, 00,00,00, 00,00,00, 00,65,10, \
00,00,74,99, dd,b0,f7, 07,00,00, 98,10,00, 00,00,00, 00,00,00, 00,00,00, 00,00,00, \
00,00,00,00, 00,00,00, 00,00,00, 00,00,00, 00,00,00, 00,c4,ae, d6,1c
"LicenseInfo" =hex:e7,77, 18,19,f8, 08,fc,7d, e8,f0,df, 12,6e,46, cb,3f,ad, b2,dd,b9, \
15,18,16,c0, bc,c3,6a, 7d,4a,80, 8b,31,13, 37,5a,78, a2,06,c8, 6b,b9,d9, dd,cc,6a, \
9c,c5,9b,77, aa,07,8d, 56,6a,7c, e4

[HKEY_LOCAL_ MACHINE\SOFTWARE \Microsoft\ Windows NT\CurrentVersion\ WPAEvents]
"OOBETimer"= hex:ff,d5, 71,d6,8b, 6a,8d,6f, d5,33,93, fd


3) In notepad click then .
4) For file type in the save dialog box select "all files" and for the filename type in .reg or whatever you want. It doesn't matter as long as it has the .reg extension.
5) Click save.
6) Double click the file thats now on your desktop.
7) It will ask you "are you sure ?"
8) Tell It Yes.

Now To See That It Worked, Go Here:

CODE


and click on "Validate Windows" over on the right.

Click Install if ask about ActiveX...

After Validation:

0 Reduced: 76% of original size [ 752 x 508 ] - Click to view full image

Friday, October 23, 2009

32 bit and 64 bit explained

Will this 32 bit software run on my 64 bit operating system?

or

Will this 64 bit software run on my computer?

Here's a short tutorial which attempts to answer these questions and helps us understand the concepts of 64 bit and 32 bit hardware, operating system and applications.

32 bit systems have been part of the mainstream computing for more than a decade since the time of the 80386. Therefore, most of the software and operating system code written during this time has been 32 bit compatible.

32 bit systems can address upto 4 GB memory in one go. Some modern applications require more memory than this to complete their tasks. This and progress in chip fabrication technology led to the development of 64 bit processors for mainstream computing.

So here comes the problem, much of the software available today is still 32 bit, but the processors have migrated to 64 bit. The operating systems are slowly catching up. Eventually even the applications will catch up. But for now, we have to cope up with all combinations of 32 and 64 bits in hardware, operating system and applications.

You can consider these three factors to be three layers with the processor as the lowest layer and the application as the highest layer as shown below:
Processor, OS and application hierarchy

To run a 64 bit application, you need support from all lower levels (64 bit OS and 64 bit processor).

To run a 64 bit OS, you need support from its lower level (a 64 bit processor).

A 32 bit OS will run on a 32 or 64 bit processor without any problems.

Similarly a 32 bit application will run on any combination of OS and processor (except a combination of 32 bit processor and 64 bit OS which is not possible). This is usually accomplished through emulation which is an operating system feature, part of all major operating systems.

Device drivers run in parallel to the operating system. Emulation is done at the operating system level, and is available to its higher layer: the application. Therefore, it is not possible to install a 32 bit device driver on a 64 bit operating system.

Answers to common questions

Will a 64 bit CPU run a standard (32-bit) program on a 64-bit version of an OS?

Yes it will. 64 bit systems are backward compatible with the 32 bit counterparts.

Will a 64-bit OS run a standard application on a 64 bit processor?
Again, it will. This is because of backward compatibility.

Can I run W2K and WXP on an 64 bit CPU, and use old software?
Yes, a 32 bit OS (W2K and WXP) will run on a 64 bit processor. Also, you should be able to run "old software" on a 64 bit OS.

However, before I close, let me also quote that many times, a 64 bit software will contain bits of 32 bit code. Similarly 32 bit software (usually very old ones) can have some code in 16 bit. Please be aware that 16 bit code will NOT run on 64 bit OS. This is one reason behind some 32 bit programs not working on 64 bit OSes.

How Windows 7 / Vista 64 Support 32 bit Applications

Introduction

This article provides an overview of the Windows on Windows 64 (WOW64) sub-system and associated techniques that support 32 bit applications under Windows 7 / Vista 64.

The Enterprise, Ultimate and Professional versions of 64 bit Windows 7 also support a 32 bit Windows XP virtual machine, which is available as optional download. Your PC must support hardware level virtualisation to use this facility.

The purpose of this add on, generally referred to as XPM, is to provide an environment that will support legacy hardware and software that will not work under Windows 7. Having tested XPM, I would advise that you only use it as a last resort. It will provide legacy support if you have no other options but, compared to other virtualisation products, performance is disappointing and the default configuration raises a number of security issues.

Discussion

Under Windows 7 / Vista 64, 32-bit applications run on top of an emulation of a 32 bit operating system that is called Windows on Windows 64, or WOW64 for short. WOW64 intercepts all operating system calls made by a 32 bit application.

For each operating system call made, WOW64 generates native 64 bit system calls, converting 32 bit data structures into 64 bit aligned structures. The appropriate native 64 bit system call is passed to the operating system kernel, and any output data from the 64 bit system call is converted into a format appropriate for the calling application before being passed back.

Like 32 bit applications, WOW64 runs in user mode so any errors that occur in translating an operating system call will only occur at that level. The 64 bit operating system kernel cannot be affected.

Since WOW64 runs in user mode, all 32 bit application code must also run in user mode. This explains why 32 bit kernel mode device drivers and applications that rely on them, will not work under Windows 7 / Vista 64.

The WOW64 emulator consists of the following DLLs:

  • Wow64.dll. This provides the core emulation infrastructure and the links to the Ntoskrnl.exe entry-point functions.
  • Wow64Win.dll provides links to the Win32k.sys entry-point functions.

Along with the 64-bit version of Ntdll.dll, these are the only 64-bit binaries that can be loaded into a 32-bit process.

At startup, Wow64.dll loads the 32 bit version of Ntdll.dll and runs its initialization code, which loads all necessary 32 bit DLLs. Almost all 32 bit DLLs are unmodified copies of the original 32 bit Windows binaries. However, some of these DLLs have been modified to behave differently on WOW64 than they do on 32 bit Windows. This is usually because they share memory with 64 bit system components.

In addition to handling operating system calls, the WOW64 interface needs to ensure that files and registry settings for 32 bit applications are kept apart from those for 64 bit applications. To achieve this two mechanisms are used, File and Registry Redirection.

File Redirection

This ensures that there are separate folders for program and operating system files for 32 and 64 bit applications.

32 bit applications files are installed into

C:\Program Files(x86)

32 bit system files are installed into

C:\WINDOWS\SysWOW64

For 64 bit applications, files are installed to

C:\Program Files

and

C:\WINDOWS\SYSTEM32

The WOW64 file redirector ensures that requests from 32 bit applications to open files in C:\Program Files or C:\WINDOWS\SYSTEM32 are redirected to the appropriate 32 bit directories.

There is one issue with file redirection that users and developers should be aware of.

Many 64 bit applications still use 32 bit installation routines. To ensure that an application is installed correctly, i.e. to C:\Program Files, the installation routine should make an operating system call to temporarily suspend the WOW64 file redirector. After installation another operating system call needs to be made to re-enable the redirector. If this approach isn't followed then the application will be installed to C:\Program Files (x86). A classic example of this is the 64 bit development version of Firefox 3.5, codenamed Shiretoko, which is installed to C:\Program Files(x86)\Shiretok o. Firefox still functions correctly, the only thing you can't do is change the icon for the application.

Registry Redirection

Registry keys specific to 32-bit applications are redirected from

HKEY_LOCAL_MACHINE\ Software

to

HKEY_LOCAL_MACHINE\ Software\ WOW6432Node

You may also occasionally see Registry entries under

HKEY_CURRENT_ USER\Software\ WOW6432Node

although this is unusual.

This approach allows both the 32 bit and 64 bit versions of an application to be installed side-by-side without overwriting each other’s settings.

Some redirected keys and/or values are also reflected. This means that if a 32 bit application makes a change to the redirected section of the registry, that change is also made to the 64 bit part of the registry, and vice-versa. Key reflection uses a policy of last writer wins. For example, if I:

  1. Install a 32 bit application that associates itself with the file extension XYZ.
  2. Install the 64 bit version of this application that associates itself with the file extension XYZ.
  3. Install another 32 bit application that associates itself with the file extension XYZ.

Double-clicking on a file with the extension XYZ in Explorer would load the application installed in step 3, as it was the last one to associate itself with this extension.

All of this is done transparently for 32 bit applications by WOW64, which, in intercepting calls to the operating system, detects references to file paths and registry keys and maps them accordingly.

Code Injection

Code injection is used to add functionality to existing applications. The majority of shell extensions rely on this technique to add themselves to Explorer.

Under 64 bit Windows it is not possible to inject 32 bit code into a 64 bit process, nor is it possible to inject 64 bit code into a 32 bit process. This explains why most 32 bit shell extensions do not work under Windows 7 / Vista 64.

Summary

Most 32 bit applications will run quite happily under Windows 7 / Vista 64. The main exceptions are:

  1. 32 bit device drivers.
  2. Applications that cannot function without the 32 bit device drivers that they use. Prime examples are antivirus, antimalware and firewall applications.
  3. Application extensions that rely on code injection into, for example, Explorer.

Some applications may work with reduced functionality. These include uninstallers, registry cleaners and tweaking programs, amongst others, since they only have access to that part of the Registry made visible to them by WOW64.

Cleaning Virtual Memory And Page Files in Win XP using Regedit

Virtual memory is a system enhancing functionality implemented for Microsoft Windows operating systems. When you have multiple programs or tasks running at the same time, Windows creates one or more virtual memory pagefiles that store information not used by your memory (RAM). These page files can sometimes contain sensitive information such as credit-card numbers and passwords you enter

How to clean the virtual memory pagefiles

You can make your computer automatically clear the virtual memory pagefiles whenever you shut down your computer. To do this, follow the steps below:
1. Click Start, then click Run...
2. Type "regedit" then click OK. The Registry Editor will be displayed.
3. In the left menu, expand the following registry keys in this order:
HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, Session Manager
4. Click the Memory Management folder,
5. In the right pane, double-click ClearPageFileAtShut down. The Edit DWORD Value window will be displayed.
6. Type 1 in the Value data field, then click OK.
7. Exit the Registry Editor.
8. Restart your system so the changes can take affect.