What is i386 and i586 and i686

These are different generations of Intel 86 architecture. 
8086 and 8088, 1st gen
80286, 2nd gen
80386, 3rd gen 
80486, 4th gen
80586, 5th gen (intel pentium and amd k5)
80686, 6th gen (intel pentium pro, II and amd k6)

I386:


Intel 80386 was a 32-bit computer processor more commonly known as the i386 or the 386. The i386 was backward compatible with hardware that targeted earlier x86 chips. The i386 was also the first consumer processor to support 4 gigabytes of memory. The low price of the i386 made possible the growth of the personal computer market


I586:


Most commonly seen as a suffix to binary packages (such as RPM packages) to be installed on a Linux system. It simply means that the package was designed to be installed on 586 based machines, ie. 586 class machines such as the 586 Pentium-100. Packages for this class of machine will run on later x86 based systems but there is no guarantee that they will run on i386 class machines.


I686:
It simply means that the package was designed to be installed on the 686 based machines, ie. 686 class machines such as the Celeron 766. Packages for this class of machine will run on later x86 based systems

local policy doesn't allow logon interactively

IN 2003 Domain Controller by default only 5 groups have the right to log on locally on the computer


1.Administrators Group
2.Account 
3.Print  
4.Backup 
5.Server Operators


If any others when they try to login to DC they will get below error message 


"The local policy of this system does not permit you to log-on interactively"


To give a specific user or group the right to log on locally on the DC You need to follow below steps

Login to Domain Controller As a Administrator

Go to administrator tools - > Domain controller security policy -> Local Policy -> User right Assignment 

you may find allow logon locally

Go to properties click on Add user or group 

Click on browse - > then enter user/ group name you want to give the access 

then click ok and Apply 

Exchange Server 2003 message tracking Event ID's list

Event Number	Event Type	Description
0	Message transfer in	The message was received from a server, a connector, or a gateway.
1	Probe transfer in	An X.400 probe was received from a gateway, a link, or a message transfer agent (MTA).
2	Report transfer in	A delivery receipt or a non-delivery report (NDR) was received from a server, a connector, or a gateway.
4	Message submission	The message was sent by the client.
5	Probe submission	An X.400 probe was received from a user.
6	Probe transfer out	An X.400 probe was sent to a gateway, a link, or an MTA.
7	Message transfer out	The message was sent to a server, a connector, or a gateway.
8	Report transfer out	A delivery receipt or an NDR was sent to a server, a connector, or a gateway.
9	Message delivered	The message was delivered to a mailbox or a public folder.
10	Report delivered	A delivery receipt or an NDR was delivered to a mailbox.
18	StartAssocByMTSUser
23	ReleaseAssocByMTSUse
28	Message redirected	The message was sent to mailboxes other than the mailboxes of the recipients.
29	Message rerouted	The message was routed to an alternative path.
31	Downgrading	An X.400 message was downgraded to 1984 format before relay.
33	Report absorption	The number of delivery receipts or of NDRs exceeded a threshold and the reports were deleted.
34	Report generation	A delivery receipt or an NDR was created.
43	Unroutable report discarded	A delivery receipt or an NDR could not be routed and was deleted from the queue.
50	Gateway deleted message	The administrator deleted an X.400 message that was queued for a gateway.
51	Gateway deleted probe	The administrator deleted an X.400 probe that was queued for a gateway.
52	Gateway deleted report	The administrator deleted an X.400 report that was queued for a gateway.
1000	Local delivery	The sender and the recipient are on the same server.
1001	Backbone transfer in	Mail was received from another MAPI system across a connector or across a gateway.
1002	Backbone transfer out	Mail was sent to another MAPI system across a connector or across a gateway.
1003	Gateway transfer out	The message was sent through a gateway.
1004	Gateway transfer in	The message was received from a gateway.
1005	Gateway report transfer in	A delivery receipt or an NDR was received from a gateway.
1006	Gateway report transfer out	A delivery receipt or an NDR was sent through a gateway.
1007	Gateway report generation	A gateway generated an NDR for a message.
1010	SMTP queued outbound	Outgoing mail was queued for delivery by the Internet Mail Service.
1011	SMTP transferred outbound	Outgoing mail was transferred to an Internet recipient.
1012	SMTP received inbound	Incoming mail was received from by the Internet Mail Service.
1013	SMTP transferred	Incoming mail that was received by the Internet Mail Service was transferred to the information store.
1014	SMTP message rerouted	An Internet message is being rerouted or forwarded to the correct location.
1015	SMTP report transferred In	A delivery receipt or an NDR was received by the Internet Mail Service
1016	SMTP report transferred out	A delivery receipt or an NDR was sent to the Internet Mail Service.
1017	SMTP report generated	A delivery receipt or an NDR was created.
1018	SMTP report absorbed	The receipt or the NDR could not be delivered and was absorbed. (You cannot send an NDR for an NDR.)
1019	SMTP submit message to AQ	A new message is submitted to Advanced Queuing.
1020	SMTP begin outbound transfer	A message is about to be sent over the wire by SMTP.
1021	SMTP bad mail	The message was transferred to the Badmail folder.
1022	SMTP AQ failure	A fatal Advanced Queuing error occurred. Information about the failure was written to the Event Manager.
1023	SMTP local delivery	A message was successfully delivered by a store drive (logged by Advanced Queue).
1024	SMTP submit message to cat	Advanced Queuing submitted a message to the categorizer.
1025	SMTP begin submit message	A new message was submitted to Advanced Queuing.
1026	SMTP AQ failed message	Advanced Queuing could not process the message. The message caused an NDR to be sent, or the message was put in the Badmail folder.
1027	SMTP submit message to SD	A message was submitted to the store driver by the MTA.
1028	SMTP SD local delivery	The store driver successfully delivered a message (logged by store driver).
1029	SMTP SD gateway delivery	The store driver transferred the message to the MTA.
1030	SMTP NDR all	All recipients were sent an NDR.
1031	SMTP end outbound transfer	The outgoing message was successfully transferred.
1032	SMTP message scheduled to retry categorization
1033	SMTP message categorized and queued for routing
1034	SMTP message routed and queued for remote delivery
1035	SMTP message scheduled to retry routing
1036	SMTP message queued for local delivery
1037	SMTP message scheduled to retry local delivery
1038	SMTP message routed and queued for gateway delivery
1039	SMTP message deleted by Intelligent Message Filtering
1040	SMTP message rejected by Intelligent Message Filtering
1041	SMTP message archived by Intelligent Message Filtering
1042	Message redirected to the alternate recipient

enable message tracking in Exchange Server 2003

1. Start Exchange System Manager.
2. Expand Administrative Groups, expand AdministrativeGroupName, expand Servers, expand ServerName, and then click Properties.
3. Click the General tab.
4. To log information about the sender, about the time the message was sent or received, about the message size and priority, or about the message recipients, click to select the Enable message tracking check box.
5. To record the subject of any message sent to, sent from, or sent through the server, click to select the Enable subject logging and display check box.  
6.  By default, the tracking logs are located in the C:\Program Files\Exchsrvr\YourServerName.log folder. Each daily log is named in the yyyymmdd.log format according to the date that the log was created.

 For message tracking Event ID's list

http://pca2z.blogspot.in/2012/05/exchange-server-2003-message-tracking.html  

Active X controls are disabled in IE

Common problem when ever open IE its giving an warning message Active X controls are disabled.

To Enable Active x controller follow the bellow steps

Open you IE -> go to Tools from the menu bar then select Internet Options 


Click on the Security tab then Select the Custom Level

Select the Enable in the Run ActiveX Controls and Plug-ins.

Now click OK and apply to change the settings.


.

How to check your open Ports

In Command prompt type netstat -a  you will get below result

 Proto  Local Address          Foreign Address        State
 13.72.128.111:51572   maa03s17-in-f2:http    ESTABLISHED

Proto: Shows which protocol it is (TCP or UDP)
Local address : this is your computer IP address you can see a number also in the above 51572. This is the port number is used by your computer.
 in this

0 - 1023 = This ports are used by "Services"
1024 - 49151 = This ports are used by "Network" ect Your Internet Browser and E-Mail clients.
49152 - 65535 = This ports are used by private users they are rarly used so this may indicate that you are infected with something.

Foreign Address: This is the Remote computer and the port is by default ftp port number is 21(port number for FTP).

State:  Shows is that computer connected to you or not.  its may ESTABLISHED / LISTENING / TIME_WAIT.

If you want to check your external IP(your Public IP) address and detect open ports on your connection go to 
http://www.yougetsignal.com/tools/open-ports/