Hindi actor Amitab Bachchan

Mother Terasa

Tip to use Notepad as a dairy

Tip to use Notepad as a dairy 

1. Open a blank Notepad file. 

2. Type .LOG as the first line of the file, followed by an Enter. Save the file and close it. 

3. Double-click the file to open it and notice that Notepad appends the current date and time to the end of the file and places the cursor on the line after. 

4. Type your notes and then save and close the file. 

5. Each time you open the file, Notepad repeats the process, appending the time and date to the end of the file and placing the cursor below it.

Tip to use Notepad as a dairy

Tip to use Notepad as a dairy 

1. Open a blank Notepad file. 

2. Type .LOG as the first line of the file, followed by an Enter. Save the file and close it. 

3. Double-click the file to open it and notice that Notepad appends the current date and time to the end of the file and places the cursor on the line after. 

4. Type your notes and then save and close the file. 

5. Each time you open the file, Notepad repeats the process, appending the time and date to the end of the file and placing the cursor below it.

Bug in Windows

Subject: Bug in Windows
Importance: High

Bush Hid The Facts

For those of you using Windows, do the following:


1.) Open an empty notepad file

2.) Type "Bush hid the facts" (without the quotes)

3.) Save it as whatever you want.

4.) Close it, and re-open it.


is it just a really weird bug?

Jesus Christ

Who invented CTRL+ALT+DEL

Ciao meaning @ Oxford dictionary

Indian national emblem

Old flower from old phone

Super deer

Awesome Nature

USA - Snow fall

HP Notebook 15-ac122tu Product Specifications

Purchased on - 1-Feb-2016
Product Name

15-ac122tu

Product Number

N8M18PA

Microprocessor

2 GHz Intel Core i3-5005U with Intel HD Graphics 5500 - 5th Generation processor

Microprocessor Cache

3 MB cache, 2 cores

Memory

4 GB DDR3L-1600 SDRAM (1 x 4 GB)

Video Graphics

Intel HD Graphics 5500

Display

15.6" diagonal HD BrightView WLED-backlit (1366 x 768)

Hard Drive

1 TB 5400 rpm SATA

Multimedia Drive

SuperMulti DVD burner

Network Card

Integrated 10/100 BASE-T Ethernet LAN

Wireless Connectivity

802.11b/g/n (1x1) and Bluetooth 4.0 combo

External Ports

1 multi-format SD media card reader

1 USB 3.0

2 USB 2.0

1 HDMI

1 RJ-45

1 headphone/microphone combo

Sound

DTS Studio Sound with 2 speakers

Keyboard

Island-style keyboard with integrated numeric keypad

Pointing Device

Touchpad with multi-touch gesture support

Diminsions

38.43 x 25.46 x 2.43 cm

Weight

Starting at 2.19 kg

Power

65 W EM AC power adapter

4-cell, 41 Wh Li-ion polymer

Camera

HP TrueVision HD Webcam (front-facing) with integrated dual array digital microphone

Beautiful bird

The cockroach theory for self development - by Sunder Pitchai, CEO of Google.

At a restaurant, a cockroach suddenly flew from somewhere and sat on a lady.

She started screaming out of fear.

With a panic stricken face and trembling voice, she started jumping, with both her hands desperately trying to get rid of the cockroach.

Her reaction was contagious, as everyone in her group also got panicky.

The lady finally managed to push the cockroach away but ...it landed on another lady in the group.

Now, it was the turn of the other lady in the group to continue the drama.

The waiter rushed forward to their rescue.

In the relay of throwing, the cockroach next fell upon the waiter.

The waiter stood firm, composed himself and observed the behavior of the cockroach on his shirt.

When he was confident enough, he grabbed it with his fingers and threw it out of the restaurant.

Sipping my coffee and watching the amusement, the antenna of my mind picked up a few thoughts and started wondering, was the cockroach responsible for their histrionic behavior?

If so, then why was the waiter not disturbed?

He handled it near to perfection, without any chaos.

It is not the cockroach, but the inability of those people to handle the disturbance caused by the cockroach, that disturbed the ladies.

I realized that, it is not the shouting of my father or my boss or my wife that disturbs me, but it's my inability to handle the disturbances caused by their shouting that disturbs me.

It's not the traffic jams on the road that disturbs me, but my inability to handle the disturbance caused by the traffic jam that disturbs me.

More than the problem, it's my reaction to the problem that creates chaos in my life.

Lessons learnt from the story:

I understood, I should not react in life.

I should always respond.

The women reacted, whereas the waiter responded.

Reactions are always instinctive whereas responses are always well thought of.

A beautiful way to understand............LIFE.

Person who is HAPPY is not because Everything is RIGHT in his Life..

He is HAPPY because his Attitude towards Everything in his Life is Right..!!,,,,,,,

Difference Between VLAN and Subnet

Subnetting and implementation of VLANs provide administrators flexibility when trying to come up

with networks on medium to very large scales. In essence, VLANs and subnets are similar in the

Difference Between VLAN and Subnet | Difference Between | VLAN vs Subnet purpose of their development. But when you peel off their general similarities, obvious differences emerge whether by functionality,operation, or deeper objectives.

VLAN (Virtual Local Area Network) exists when two or more ports are connected physically or grouped together by some piece of network hardware/software that supports VLAN functionalities. On the whole, a VLAN is very similar to that of a physical LAN. Their main difference is VLANs capability to group end stations together without the requirement of

being located on the same network switch. In VLAN, configuration of the network can be done via

software extensively. Basically, VLANs are used at layer 2 to break up broadcast domains.

Each VLAN is considered as a separate entity and it can only reach another VLAN through a

router. You can use a single network with VLANs but when one network goes down for some

reason, the entire logical network is concerned. VLANs are very useful when an IT professional

(system or network admin) wants to group organization departments for better work performance,

less traffic, and more efficiency.

A subnet is essentially a group of IP addresses. Any particular address can reach any address without using any routing device if they belong to the same subnet. Now, if the address you want to reach is outside of your subnet, then just like in VLANs, you will have to go through a router. 

Subnet is at layer 3 (IP), wherein IP addresses belong.

When you are subnetting, you are actually dividing an IP address into smaller subnets. This

accomplishes an addition of multiple networks to the system, a thing that any organization or

agency would constantly need. The great thing about subnetting is that subnets are unaffected with

other subnets going down or having technical breakdowns.

It can be said that VLAN is software-based and subnetting is primarily hardware-based. Though

VLANS are somewhat perceived to be lacking in security as they can be hacked, it is still the

more popular network segregation of choice by many administrators.

Summary:

1. VLAN is found to be more popular than subnetting but, more often than not, both are used to

complement each other.

2. VLAN is works at the layer 2 while subnet is at layer 3.

3. Subnets are more concerned about IP addresses. 

4. Many would consider that subnetting is more secure but VLAN brings more network efficiency.

5. VLAN is largely software-based while subnet is hardware-based.

Nature

The basic steps in configuring a VLAN are:

Plan your network.

Create the VLANs.

Associate switch ports with the VLANs.

Test VLAN connectivity.

Implement security measures as appropriate.

Active vs Passive FTP

Introduction

One of the most commonly seen questions when dealing with firewalls and other Internet connectivity issues is the difference between active and passive FTP and how best to support either or both of them. Hopefully the following text will help to clear up some of the confusion over how to support FTP in a firewalled environment.

This may not be the definitive explanation, as the title claims, however, I've heard enough good feedback and seen this document linked in enough places to know that quite a few people have found it to be useful. I am always looking for ways to improve things though, and if you find something that is not quite clear or needs more explanation, please let me know! Recent additions to this document include the examples of both active and passive command line FTP sessions. These session examples should help make things a bit clearer. They also provide a nice picture into what goes on behind the scenes during an FTP session. Now, on to the information...

The Basics

FTP is a TCP based service exclusively. There is no UDP component to FTP. FTP is an unusual service in that it utilizes two ports, a 'data' port and a 'command' port (also known as the control port). Traditionally these are port 21 for the command port and port 20 for the data port. The confusion begins however, when we find that depending on the mode, the data port is not always on port 20.

Active FTP

In active mode FTP the client connects from a random unprivileged port (N > 1023) to the FTP server's command port, port 21. Then, the client starts listening to port N+1 and sends the FTP command PORT N+1 to the FTP server. The server will then connect back to the client's specified data port from its local data port, which is port 20.

From the server-side firewall's standpoint, to support active mode FTP the following communication channels need to be opened:

FTP server's port 21 from anywhere (Client initiates connection)

FTP server's port 21 to ports > 1023 (Server responds to client's control port)

FTP server's port 20 to ports > 1023 (Server initiates data connection to client's data port)

FTP server's port 20 from ports > 1023 (Client sends ACKs to server's data port)

When drawn out, the connection appears as follows:

In step 1, the client's command port contacts the server's command port and sends the command PORT 1027. The server then sends an ACK back to the client's command port in step 2. In step 3 the server initiates a connection on its local data port to the data port the client specified earlier. Finally, the client sends an ACK back as shown in step 4.

The main problem with active mode FTP actually falls on the client side. The FTP client doesn't make the actual connection to the data port of the server--it simply tells the server what port it is listening on and the server connects back to the specified port on the client. From the client side firewall this appears to be an outside system initiating a connection to an internal client--something that is usually blocked.

Active FTP Example

Below is an actual example of an active FTP session. The only things that have been changed are the server names, IP addresses, and user names. In this example an FTP session is initiated from testbox1.slacksite.com (192.168.150.80), a linux box running the standard FTP command line client, to testbox2.slacksite.com (192.168.150.90), a linux box running ProFTPd 1.2.2RC2. The debugging (-d) flag is used with the FTP client to show what is going on behind the scenes. Everything in red is the debugging output which shows the actual FTP commands being sent to the server and the responses generated from those commands. Normal server output is shown in black, and user input is in bold.

There are a few interesting things to consider about this dialog. Notice that when the PORT command is issued, it specifies a port on the client (192.168.150.80) system, rather than the server. We will see the opposite behavior when we use passive FTP. While we are on the subject, a quick note about the format of the PORT command. As you can see in the example below it is formatted as a series of six numbers separated by commas. The first four octets are the IP address while the last two octets comprise the port that will be used for the data connection. To find the actual port multiply the fifth octet by 256 and then add the sixth octet to the total. Thus in the example below the port number is ( (14*256) + 178), or 3762. A quick check with netstat should confirm this information.

testbox1: {/home/p-t/slacker/public_html} % ftp -d testbox2

Connected to testbox2.slacksite.com.

220 testbox2.slacksite.com FTP server ready.

Name (testbox2:slacker): slacker

---> USER slacker

331 Password required for slacker.

Password: TmpPass

---> PASS XXXX

230 User slacker logged in.

---> SYST

215 UNIX Type: L8

Remote system type is UNIX.

Using binary mode to transfer files.

ftp> ls

ftp: setsockopt (ignored): Permission denied

---> PORT 192,168,150,80,14,178

200 PORT command successful.

---> LIST

150 Opening ASCII mode data connection for file list.

drwx------ 3 slacker users 104 Jul 27 01:45 public_html

226 Transfer complete.

ftp> quit

---> QUIT

221 Goodbye.

Passive FTP

In order to resolve the issue of the server initiating the connection to the client a different method for FTP connections was developed. This was known as passive mode, or PASV, after the command used by the client to tell the server it is in passive mode.

In passive mode FTP the client initiates both connections to the server, solving the problem of firewalls filtering the incoming data port connection to the client from the server. When opening an FTP connection, the client opens two random unprivileged ports locally (N > 1023 and N+1). The first port contacts the server on port 21, but instead of then issuing a PORT command and allowing the server to connect back to its data port, the client will issue the PASV command. The result of this is that the server then opens a random unprivileged port (P > 1023) and sends P back to the client in response to the PASV command. The client then initiates the connection from port N+1 to port P on the server to transfer data.

From the server-side firewall's standpoint, to support passive mode FTP the following communication channels need to be opened:

FTP server's port 21 from anywhere (Client initiates connection)

FTP server's port 21 to ports > 1023 (Server responds to client's control port)

FTP server's ports > 1023 from anywhere (Client initiates data connection to random port specified by server)

FTP server's ports > 1023 to remote ports > 1023 (Server sends ACKs (and data) to client's data port)

When drawn, a passive mode FTP connection looks like this:

In step 1, the client contacts the server on the command port and issues the PASV command. The server then replies in step 2 with PORT 2024, telling the client which port it is listening to for the data connection. In step 3 the client then initiates the data connection from its data port to the specified server data port. Finally, the server sends back an ACK in step 4 to the client's data port.

While passive mode FTP solves many of the problems from the client side, it opens up a whole range of problems on the server side. The biggest issue is the need to allow any remote connection to high numbered ports on the server. Fortunately, many FTP daemons, including the popular WU-FTPD allow the administrator to specify a range of ports which the FTP server will use. See Appendix 1 for more information.

The second issue involves supporting and troubleshooting clients which do (or do not) support passive mode. As an example, the command line FTP utility provided with Solaris does not support passive mode, necessitating a third-party FTP client, such as ncftp.

NOTE: This is no longer the case--use the -p option with the Solaris FTP client to enable passive mode!

With the massive popularity of the World Wide Web, many people prefer to use their web browser as an FTP client. Most browsers only support passive mode when accessing ftp:// URLs. This can either be good or bad depending on what the servers and firewalls are configured to support.

Passive FTP Example

Below is an actual example of a passive FTP session. The only things that have been changed are the server names, IP addresses, and user names. In this example an FTP session is initiated from testbox1.slacksite.com (192.168.150.80), a linux box running the standard FTP command line client, to testbox2.slacksite.com (192.168.150.90), a linux box running ProFTPd 1.2.2RC2. The debugging (-d) flag is used with the FTP client to show what is going on behind the scenes. Everything in red is the debugging output which shows the actual FTP commands being sent to the server and the responses generated from those commands. Normal server output is shown in black, and user input is in bold.

Notice the difference in the PORT command in this example as opposed to the active FTP example. Here, we see a port being opened on the server (192.168.150.90) system, rather than the client. See the discussion about the format of the PORT command above, in the Active FTP Example section.

testbox1: {/home/p-t/slacker/public_html} % ftp -d testbox2

Connected to testbox2.slacksite.com.

220 testbox2.slacksite.com FTP server ready.

Name (testbox2:slacker): slacker

---> USER slacker

331 Password required for slacker.

Password: TmpPass

---> PASS XXXX

230 User slacker logged in.

---> SYST

215 UNIX Type: L8

Remote system type is UNIX.

Using binary mode to transfer files.

ftp> passive

Passive mode on.

ftp> ls

ftp: setsockopt (ignored): Permission denied

---> PASV

227 Entering Passive Mode (192,168,150,90,195,149).

---> LIST

150 Opening ASCII mode data connection for file list

drwx------ 3 slacker users 104 Jul 27 01:45 public_html

226 Transfer complete.

ftp> quit

---> QUIT

221 Goodbye.

Other Notes

A reader, Maarten Sjouw, pointed out that active FTP will not function when used in conjunction with a client-side NAT (Network Address Translation) device which is not smart enough to alter the IP address info in FTP packets.

Summary

The following chart should help admins remember how each FTP mode works:

Active FTP :

command : client >1023 -> server 21

data : client >1023 <- 20="" font="" server="">

Passive FTP :

command : client >1023 -> server 21

data : client >1024 -> server >1023

A quick summary of the pros and cons of active vs. passive FTP is also in order:

Active FTP is beneficial to the FTP server admin, but detrimental to the client side admin. The FTP server attempts to make connections to random high ports on the client, which would almost certainly be blocked by a firewall on the client side. Passive FTP is beneficial to the client, but detrimental to the FTP server admin. The client will make both connections to the server, but one of them will be to a random high port, which would almost certainly be blocked by a firewall on the server side.

Luckily, there is somewhat of a compromise. Since admins running FTP servers will need to make their servers accessible to the greatest number of clients, they will almost certainly need to support passive FTP. The exposure of high level ports on the server can be minimized by specifying a limited port range for the FTP server to use. Thus, everything except for this range of ports can be firewalled on the server side. While this doesn't eliminate all risk to the server, it decreases it tremendously. See Appendix 1 for more information.  

Active and passive are the two modes that FTP can run in. FTP uses two channels between client and server, the command channel and the data channel, which are actually separate TCP connections. The command channel is for commands and responses, the data channel is for actually transferring files. It's a nifty way of sending commands to the server without having to wait for the current data transfer to finish.

In active mode, the client establishes the command channel (from client port X to server port 21(b)) but the server establishes the data channel (from server port 20(b) to client port Y, where Y has been supplied by the client).

In passive mode, the client establishes both channels. In that case, the server tells the client which port should be used for the data channel.

Passive mode is generally used in situations where the FTP server is not able to establish the data channel. One of the major reasons for this is network firewalls. While you may have a firewall rule which allows you to open up FTP channels to ftp.microsoft.com, Microsoft's servers may not have the power to open up the data channel back through your firewall.

Passive mode solves this by opening up both types of channel from the client side. In order to make this hopefully clearer:

Active mode:

Client opens up command channel from client port 2000(a) to server port 21(b).

Client sends PORT 2001(a) to server and server acknowledges on command channel.

Server opens up data channel from server port 20(b) to client port 2001(a).

Client acknowledges on data channel.

Passive mode:

Client opens up command channel from client port 2000(a) to server port 21(b).

Client sends PASV to server on command channel.

Server sends back (on command channel) PORT 1234(a) after starting to listen on that port.

Client opens up data channel from client 2001(a) to server port 1234(a).

Server acknowledges on data channel.

At this point, the command and data channels are both open.

(a)Note that the selection of ports on the client side is up to the client, as the selection of the server data channel port in passive mode is up to the server.

(b)Further note that the use of port 20 and 21 is only a convention (although a strong one). There's no absolute requirement that those ports be used although the client and server both have to agree on which ports are being used. I've seen implementations that try to hide from clients by using different ports (futile, in my opinion).