Information Technology

Implementing SPF and DKIM in Mail System

noreply@blogger.com (mushtaqnaik) — Thu, 26 Apr 2012 17:46:00 +0000

How to use authorization in sending mails, as we know there is lot of spammers and phishers which exploit Mail Servers daily and not only this if you are sending Bluck Mails to your clients having mail ids in different domains (yahoo, gmail, hotmail etc) in most cases your mail will land on spam or junk, so to avoid these things we can implement SPF and DKIM.

First lets understand what is SFP and DKIM

Sender Policy Framework (SPF) is an email validation system designed to prevent email spam by detecting email spoofing, a common vulnerability, by verifying sender IP addresses. SPF allows administrators to specify which hosts are allowed to send mail from a given domain by creating a specific SPF record (or TXT record) in the Domain Name System (DNS). Mail exchangers use the DNS to check that mail from a given domain is being sent by a host sanctioned by that domain's administrators.

Domain Keys: DKIM embeds a cryptographic signature to e-mail messages and an indication of which DNS entry to examine. The receiving server can then look up the DNS entry and use the data it finds to verify the signature.

To Generate SPF you can get help from Here or you can generate SPF through this URL .

And to generate DKIM signature you can use this URL and if you are concerned about your Keys may be misused by above URL then you can generate DKIM Keys through OPENSSL to do this you can follow the steps from this Website

I hope this will help you out from some spamming frustration and there is another thing we can implement that is DMARC (Domain-based Message Authentication, Reporting & Conformance), we will talk about this in coming post....

How to Trace Deadlocks in SQL Server

noreply@blogger.com (mushtaqnaik) — Sat, 28 Jan 2012 11:04:00 +0000

In SQL Server Trace flags are used to diagnose performance issues or to debug stored procedures or complex computer systems.Trace flags are valuable DBA tools that allow you to enable or disable a database function temporarily. Once you turn on a trace flag, it remains on until you either manually turn it off or restart SQL Server. So to Trace Deadlocks in SQL Server we use two Trace Flags

1. 1222

Used to trace deadlocks in SQL Server.

Syntax

DBCC TRACEON (1222,-1)

2. 3605

Used to write Deadlocks to Errorlog.

Syntax

DBCC TRACEON (3605,-1)

So above two Trace Flags are enough to Trace Deadlocks in SQL Server Databases. To Disable above Trace Flags we have to use DBCC TRACEOFF command.

Windows 7 As VPN Server

noreply@blogger.com (mushtaqnaik) — Sat, 27 Aug 2011 11:20:00 +0000

Hi ,

Today i am going to show you how to use Windows 7 as a VPN Server.

We all know what the VPN Server is and for what purpose we use VPN, still I will give you some quick information regarding VPN then we will proceed .

VPN is virtual private network. When you allow a computer to act as a VPN server, you basically allow computers outside your network to connect to VPN host and utilize the private network’s capabilities (e.g., accessing Internet, share files, Printer etc…). To make this a little clearer, you can sit in a hotel room and access your office’s n/w through Internet connection of Hotel. So that means you are accessing your Office n/w through Public n/w so in order to make it secure we use VPN. With a private Internet connection such as your office’s Internet connection, you don’t have to worry about unknown users sniff your Internet traffic (e.g., prying on your Internet activities, stealing your plain text password). In addition, the VPN connection will automatically encrypt all of your data from and to both ends of VPN (i.e., from the public to the private networks).

Now lets see how to use Widows 7 as a VPN Server

1. First Open Network and Sharing Center from the network system tray icon.

2. From the Control Panel\All Control Panel Items\Network and Sharing Center, click Change adapter settings.

3. Press the Alt button to show the File menu, then click File and select New Incoming Connection…

4. From the Allow connections to this computer window, select the users’ accounts that you would like to give VPN access. You can create new users through the Add someone… button. The Account Properties button allows you to change the user’s passwords and other details.

5. Click Next.

6. Check the Through the Internet option to the question How will people connect? And click Next.

7. At the Networking software list, select the protocols and other services that you want users to have access to, such as, File and Printer Shares. In addition to the default services you can add other network features through the Install… button. The Properties button allows you to configure advanced option for each network service that has additional features such as Internet Protocol Version 4 (TCP/IP).

8. Click Allow Access to enable the selected items for incoming connections.

9. The final screen displays the computer name that users will be connecting to and allows you to print this information. Click Close.

Now, in Control Panel\Network and Internet\Network Connections you should have a new connection named Incoming Connections. Double clicking this connection would load all properties for the VPN server.

Show specific devices that allow incoming connections if installed.

Enable and disable the VPN service.

Modify the allowed users properties while adding/removing users from the list.

Configure additional properties of the network components that connecting users have access to.

For example, to define the IPv4 address range for VPN clients:

1. Double click the Incoming Connections connection.

2. Select the Networking tab and Internet Protocol version 4 (TCP/IP), then click the Properties button.

3. Select Specify IP address and enter a starting and ending IP addresses that are not used internally or defined in your internal DHCP scope. You have the option to allow users specify their own IP address by checking the Allow calling computer to specify its own IP address. From this tab you can also allow/disallow users access to the LAN.

4. Click OK twice.

And I recommend that you assign IP addresses to VPN users automatically using DHCP as this would be the safest option. These options are also available when setting up the VPN server for the first time.

The HTTP status codes in IIS 7.0

noreply@blogger.com (mushtaqnaik) — Wed, 06 Apr 2011 09:29:00 +0000

Hi All, I am writing the Post after long time.

Some times when we open any website and we come across with some Error codes like "403.9 - Forbidden". "403.7 ." etc and we gets confused because we didn't get detailed error information, So in this Post I am trying to collect these error codes with their meaning (Source Microsoft)

IIS 7.0 uses the following success HTTP status codes:
•    200 - OK. The client request has succeeded.
•    201 - Created.
•    202 - Accepted.
•    203 - Nonauthoritative information.
•    204 - No content.
•    205 - Reset content.
•    206 - Partial content.
3xx - Redirection
These HTTP status codes indicate that the client browser must take more action to fulfill the request. For example, the client browser may have to request a different page on the server. Or, the client browser may have to repeat the request by using a proxy server.

IIS 7.0 uses the following redirection HTTP status codes:
•    301 - Moved permanently.
•    302 - Object moved.
•    304 - Not modified.
•    307 - Temporary redirect.
4xx - Client error
These HTTP status codes indicate that an error occurred and that the client browser appears to be at fault. For example, the client browser may have requested a page that does not exist. Or, the client browser may not have provided valid authentication information.

IIS 7.0 uses the following client error HTTP status codes:
•    400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 400 error:
o    400.1 - Invalid Destination Header.
o    400.2 - Invalid Depth Header.
o    400.3 - Invalid If Header.
o    400.4 - Invalid Overwrite Header.
o    400.5 - Invalid Translate Header.
o    400.6 - Invalid Request Body.
o    400.7 - Invalid Content Length.
o    400.8 - Invalid Timeout.
o    400.9 - Invalid Lock Token.
•    401 - Access denied.

IIS 7.0 defines several HTTP status codes that indicate a more specific cause of a 401 error. The following specific HTTP status codes are displayed in the client browser but are not displayed in the IIS log:
o    401.1 - Logon failed.
o    401.2 - Logon failed due to server configuration.
o    401.3 - Unauthorized due to ACL on resource.
o    401.4 - Authorization failed by filter.
o    401.5 - Authorization failed by ISAPI/CGI application.
•    403 - Forbidden.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 403 error:
o    403.1 - Execute access forbidden.
o    403.2 - Read access forbidden.
o    403.3 - Write access forbidden.
o    403.4 - SSL required.
o    403.5 - SSL 128 required.
o    403.6 - IP address rejected.
o    403.7 - Client certificate required.
o    403.8 - Site access denied.
o    403.9 - Forbidden: Too many clients are trying to connect to the Web server.
o    403.10 - Forbidden: Web server is configured to deny Execute access.
o    403.11 - Forbidden: Password has been changed.
o    403.12 - Mapper denied access.
o    403.13 - Client certificate revoked.
o    403.14 - Directory listing denied.
o    403.15 - Forbidden: Client access licenses have exceeded limits on the Web server.
o    403.16 - Client certificate is untrusted or invalid.
o    403.17 - Client certificate has expired or is not yet valid.
o    403.18 - Cannot execute requested URL in the current application pool.
o    403.19 - Cannot execute CGI applications for the client in this application pool.
o    403.20 - Forbidden: Passport logon failed.
o    403.21 - Forbidden: Source access denied.
o    403.22 - Forbidden: Infinite depth is denied.
•    404 - Not found.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 404 error:
o    404.0 - Not found.
o    404.1 - Site Not Found.
o    404.2 - ISAPI or CGI restriction.
o    404.3 - MIME type restriction.
o    404.4 - No handler configured.
o    404.5 - Denied by request filtering configuration.
o    404.6 - Verb denied.
o    404.7 - File extension denied.
o    404.8 - Hidden namespace.
o    404.9 - File attribute hidden.
o    404.10 - Request header too long.
o    404.11 - Request contains double escape sequence.
o    404.12 - Request contains high-bit characters.
o    404.13 - Content length too large.
o    404.14 - Request URL too long.
o    404.15 - Query string too long.
o    404.16 - DAV request sent to the static file handler.
o    404.17 - Dynamic content mapped to the static file handler via a wildcard MIME mapping.
o    404.18 - Querystring sequence denied.
o    404.19 - Denied by filtering rule.
•    405 - Method Not Allowed.
•    406 - Client browser does not accept the MIME type of the requested page.
•    408 - Request timed out.
•    412 - Precondition failed.
5xx - Server error
These HTTP status codes indicate that the server cannot complete the request because the server encounters an error.

IIS 7.0 uses the following server error HTTP status codes:
•    500 - Internal server error.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 500 error:
o    500.0 - Module or ISAPI error occurred.
o    500.11 - Application is shutting down on the Web server.
o    500.12 - Application is busy restarting on the Web server.
o    500.13 - Web server is too busy.
o    500.15 - Direct requests for Global.asax are not allowed.
o    500.19 - Configuration data is invalid.
o    500.21 - Module not recognized.
o    500.22 - An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
o    500.23 - An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
o    500.24 - An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
o    500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
Note Here is where the distributed rules configuration is read for both inbound and outbound rules.
o    500.51 - A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
Note Here is where the global rules configuration is read.
o    500.52 - A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
o    500.53 - A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
o    500.100 - Internal ASP error.
•    501 - Header values specify a configuration that is not implemented.
•    502 - Web server received an invalid response while acting as a gateway or proxy.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 502 error:
o    502.1 - CGI application timeout.
o    502.2 - Bad gateway.
•    503 - Service unavailable.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 503 error:
o    503.0 - Application pool unavailable.
o    503.2 - Concurrent request limit exceeded.
Back to the top
Common HTTP status codes and the causes
The causes of some common HTTP status codes are as follows:
•    200 - OK. IIS 7.0 successfully processed the request.
•    304 - Not modified. The client browser requests a document that is already in the cache, and the document has not been modified since the document was cached. The client browser uses the cached copy of the document instead of downloading the document from the server.
•    400 - Bad request. The Http.sys file blocks IIS 7.0 from processing the request because of a problem in the request. Typically, this HTTP status code means that the request contains characters or sequences that are not valid or that the request contradicts the security settings in the Http.sys file.
•    401.1 - Logon failed. The logon attempt is unsuccessful probably because of a user name or a password that is not valid. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942044 (http://support.microsoft.com/kb/942044/ ) Error message when you try to run a Web application that is hosted on IIS 7.0: "HTTP Error 401.1 - Not Found"
•    401.2 - Logon failed due to server configuration. This HTTP status code indicates a problem in the authentication configuration settings on the server. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942043 (http://support.microsoft.com/kb/942043/ ) Error message when you try to visit a Web page that is hosted on IIS 7.0: "HTTP Error 401.2 - Unauthorized"
•    401.3 - Unauthorized due to ACL on resource. This HTTP status code indicates a problem in the NTFS file system permissions. This problem may occur even if the permissions are correct for the file that you are trying to access. For example, this problem occurs if the IUSR account does not have access to the C:\Winnt\System32\Inetsrv directory. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942042 (http://support.microsoft.com/kb/942042/ ) Error message when you try to browse a Web page that is hosted on a server that is running IIS 7.0: "HTTP Error 401.3 - Unauthorized"
•    401.4 - Authorization failed by filter. An ISAPI filter does not let the request be processed because of an authorization problem. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942079 (http://support.microsoft.com/kb/942079/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 401.4 - Authorization failed by filter"
•    401.5 - Authorization failed by ISAPI/CGI application. An ISAPI application or a Common Gateway Interface (CGI) application does not let the request be processed because of an authorization problem. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942078 (http://support.microsoft.com/kb/942078/ ) Error message when you visit a Web site that is hosted on a computer that is running IIS 7.0: "HTTP Error 401.5 - Authorization failed by ISAPI/CGI application"
•    403.1 - Execute access forbidden. The appropriate level of the Execute permission is not granted. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942065 (http://support.microsoft.com/kb/942065/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.1 - Forbidden"
•    403.2 - Read access forbidden. The appropriate level of the Read permission is not granted. Verify that you have set up IIS 7.0 to grant the Read permission to the directory. Additionally, if you use a default document, verify that the default document exists. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942036 (http://support.microsoft.com/kb/942036/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.2 - Forbidden"
•    403.3 - Write access forbidden. The appropriate level of the Write permission is not granted. Verify that the IIS 7.0 permissions and the NTFS file system permissions are set up to grant the Write permission to the directory. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942035 (http://support.microsoft.com/kb/942035/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.3 – Forbidden"
•    403.4 - SSL required. The request is made over a nonsecure channel, and the Web application requires a Secure Sockets Layer (SSL) connection. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942070 (http://support.microsoft.com/kb/942070/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.4 - Forbidden"
•    403.5 - SSL 128 required. The server is configured to require a 128-bit SSL connection. But, the request is not sent by using 128-bit encryption. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942069 (http://support.microsoft.com/kb/942069/ ) Error message when you try to browse a Web page that is hosted on IIS 7.0: "HTTP Error 403.5 - Forbidden"
•    403.6 - IP address rejected. The server is configured to deny access to the current IP address. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942068 (http://support.microsoft.com/kb/942068/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.6 - IP Address Rejected"
•    403.7 - Client certificate required. The server is configured to require a certificate for client authentication. But, the client browser does not have an appropriate client certificate installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942067 (http://support.microsoft.com/kb/942067/ ) Error message when you try to run a Web application that is hosted on a server that is running IIS 7.0: "HTTP Error 403.7 - Forbidden"
•    403.8 - Site access denied. The server is configured to deny requests based on the Domain Name System (DNS) name of the client computer. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
942066 (http://support.microsoft.com/kb/942066/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.8 - Forbidden"
•    403.12 - Mapper denied access. The page that you want to access requires a client certificate. But, the user ID that is mapped to the client certificate is denied access to the file. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942064 (http://support.microsoft.com/kb/942064/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.12 - Client Certificate Denied"
•    403.13 - Client certificate revoked. The client browser tries to use a client certificate that was revoked by the issuing certification authority. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942063 (http://support.microsoft.com/kb/942063/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.13 - Forbidden"
•    403.14 - Directory listing denied. The server is not configured to display a content directory listing, and a default document is not set. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942062 (http://support.microsoft.com/kb/942062/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.14 - Forbidden"
•    403.16 - Client certificate is untrusted or invalid. The client browser tries to use a client certificate that is not trusted by the server that is running IIS 7.0 or that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942061 (http://support.microsoft.com/kb/942061/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.16 - Forbidden"
•    403.17 - Client certificate has expired or is not yet valid. The client browser tries to use a client certificate that is expired or that is not yet valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942038 (http://support.microsoft.com/kb/942038/ ) Error message when you try to visit a Web page that is hosted on Internet Information Services 7.0: "HTTP Error 403.17 (Forbidden) - The client certificate has expired"
•    403.18 - Cannot execute requested URL in the current application pool. A custom error page is configured, and the custom error page resides in a different application pool than the application pool of the requested URL. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942037 (http://support.microsoft.com/kb/942037/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.18 - Forbidden"
•    403.19 - Cannot execute CGI applications for the client browser in this application pool. The identity of the application pool does not have the Replace a process level token user right. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942048 (http://support.microsoft.com/kb/942048/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 403.19 - Forbidden"
•    404.0 - Not found. The file that you are trying to access was moved or does not exist. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942041 (http://support.microsoft.com/kb/942041/ ) Error message when you try to open a Web page that is hosted on IIS 7.0: "HTTP Error 404.0 - Not Found"
•    404.2 - ISAPI or CGI restriction. The requested ISAPI resource or the requested CGI resource is restricted on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942040 (http://support.microsoft.com/kb/942040/ ) Error message when you try to visit a Web page that is hosted on a computer that is running IIS 7.0: "HTTP Error 404.2 – Not Found"
•    404.3 - MIME type restriction. The current MIME mapping for the requested extension type is not valid or is not configured. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942032 (http://support.microsoft.com/kb/942032/ ) Error message when users visit a Web site that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 404.3 - Not Found"
•    404.4 - No handler configured. The file name extension of the requested URL does not have a handler that is configured to process the request on the Web server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942052 (http://support.microsoft.com/kb/942052/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.4 - Not Found"
•    404.5 - Denied by request filtering configuration. The requested URL contains a character sequence that is blocked by the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942053 (http://support.microsoft.com/kb/942053/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.5 - URL Sequence Denied"
•    404.6 - Verb denied. The request is made by using an HTTP verb that is not configured or that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942046 (http://support.microsoft.com/kb/942046/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.6 - VERB_DENIED"
•    404.7- File extension denied. The requested file name extension is not allowed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942045 (http://support.microsoft.com/kb/942045/ ) Error message when you try to browse a Web page that is hosted on IIS 7.0: "HTTP Error 404.7 - FILE_EXTENSION_DENIED"
•    404.8 - Hidden namespace. The requested URL is denied because the directory is hidden. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942047 (http://support.microsoft.com/kb/942047/ ) Error message when you try to visit a Web page that is hosted on IIS 7.0: "HTTP Error 404.8 - HIDDEN_NAMESPACE"
•    404.9 - File attribute hidden. The requested file is hidden. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942049 (http://support.microsoft.com/kb/942049/ ) Error message when you try to visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.9 - File Attribute Hidden"
•    404.10 - Request header too long. The request is denied because the request headers are too long. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942077 (http://support.microsoft.com/kb/942077/ ) Error message when you visit a Web site that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 404.10 - REQUEST_HEADER_TOO_LONG"
•    404.11 - Request contains double escape sequence. The request contains a double escape sequence. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942076 (http://support.microsoft.com/kb/942076/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.11 - URL_DOUBLE_ESCAPED"
•    404.12 - Request contains high-bit characters. The request contains high-bit characters, and the server is configured not to allow high-bit characters. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942075 (http://support.microsoft.com/kb/942075/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.12 - URL_HAS_HIGH_BIT_CHARS"
•    404.13 - Content length too large. The request contains a Content-Length header. The value of the Content-Length header is larger than the limit that is allowed for the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942074 (http://support.microsoft.com/kb/942074/ ) Error message when you visit a Web site that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE"
•    404.14 - Request URL too long. The requested URL exceeds the limit that is allowed for the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942073 (http://support.microsoft.com/kb/942073/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.14 - URL_TOO_LONG"
•    404.15 - Query string too long. The request contains a query string that is longer than the limit that is allowed for the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942071 (http://support.microsoft.com/kb/942071/ ) Error message when you visit a Web site that is hosted on a server that is running IIS 7.0: "HTTP Error 404.15 - Not Found"
•    404.17 - Dynamic content mapped to the static file handler. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2019689 (http://support.microsoft.com/kb/2019689/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 404.17 - Not Found"
•    405.0 - Method not allowed. The request is made by using an HTTP method that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942051 (http://support.microsoft.com/kb/942051/ ) Error message when a user visits a Web site that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 405.0 - Method not allowed"
•    406.0 - Invalid MIME type. The request is made by using an Accept header that contains a MIME value that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942050 (http://support.microsoft.com/kb/942050/ ) Error message when you visit a Web site that is hosted on a server that is running Internet Information Services 7.0: "HTTP Error 406 - Not Acceptable"
•    412.0 - Precondition failed. The request is made by using an If-Match request header that contains a value that is not valid. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942056 (http://support.microsoft.com/kb/942056/ ) Error message when you visit a Web site that is hosted on Internet Information Services (IIS) 7.0: "HTTP Error 412 - Precondition failed"
•    500 - Internal server error. This HTTP status code may occur for many server-side reasons. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942031 (http://support.microsoft.com/kb/942031/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.0 - Internal Server Error"
•    500.11 - Application is shutting down on the Web server. The request is not processed because the destination application pool is shutting down. Wait for the worker process to finish shutting down, and then try the request again. If this problem persists, the Web application may be experiencing problems that prevent the Web application from shutting down correctly.
•    500.12 - Application is busy restarting on the Web server. The request is not processed because the destination application pool is restarting. This HTTP status code should disappear when you refresh the page. If this HTTP status code appears again after you refresh the page, the problem may be caused by antivirus software that is scanning the Global.asa file. If this problem persists, the Web application may be experiencing problems that prevent the Web application from restarting correctly.
•    500.13 - Web server is too busy. The request is not processed because the server is too busy to accept any new incoming requests. Typically, this HTTP status code means that the number of incoming concurrent requests exceeds the number that the IIS 7.0 Web application can process. This problem may occur because the performance configuration settings are set too low, the hardware is insufficient, or a bottleneck occurs in the IIS 7.0 Web application. A common troubleshooting method is to generate a memory dump file of the IIS 7.0 processes when the error is occurring and then to debug the memory dump file.
•    500.15 - Direct requests for Global.asax are not allowed. A direct request for the Global.asa file or for the Global.asax file is made. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942030 (http://support.microsoft.com/kb/942030/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.15 - Direct request for global.asa are not allowed"
•    500.19 - Configuration data is invalid. This HTTP status code occurs because of a problem in the associated Applicationhost.config file or in the associated Web.config file. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942055 (http://support.microsoft.com/kb/942055/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.19 - Internal Server Error"
•    500.100 - Internal ASP error. An error occurs during the processing of an Active Server Pages (ASP) page. To obtain more specific information about the error, disable friendly HTTP error messages in the Web browser. Additionally, the IIS log may show an ASP error number that corresponds to the error that occurs. For more information about ASP error messages and about the meaning of ASP error messages, click the following article number to view the article in the Microsoft Knowledge Base:
294271 (http://support.microsoft.com/kb/294271/ ) ASP error codes
•    501.0 - Not implemented. The client browser sends an HTTP-Trace verb, and the server is not configured to process the HTTP-Trace verb. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942058 (http://support.microsoft.com/kb/942058/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 501.0 - Not Implemented"
•    502.1 - CGI application timeout. A CGI application does not return a valid HTTP response in the configured time limit. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942059 (http://support.microsoft.com/kb/942059/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 502.1 - Bad Gateway"
•    502.2 - Bad gateway. A CGI application returns an HTTP response that is not valid to the server that is running IIS 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
942057 (http://support.microsoft.com/kb/942057/ ) Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 502.2 - Bad Gateway"
•    503.0 - Service unavailable. The request is sent to an application pool that is currently stopped or that is currently disabled. To resolve this issue, make sure that the destination application pool is started. The event log may give information about why the application pool is stopped or disabled.
•    503.2 - Concurrent request limit exceeded. The appConcurrentRequestLimit property is set to a value that is lower than the current number of concurrent requests. IIS 7.0 does not allow more concurrent requests than the value of the appConcurrentRequestLimit property.

Creating a Virtual Machine in Microsoft Virtual PC

noreply@blogger.com (mushtaqnaik) — Thu, 30 Dec 2010 13:30:00 +0000

Hi, in this Post you will get to know how to Create Virtual Machine in Microsoft Virtual PC

1. Open Virtual PC and click on New.

2. In the New Virtual Machine Wizard click Create a Virtual Machine.
3. In the Virtual Machine Name and Location click to browse to point to the location where you want to place your new VM. Note that the best location for the VM is on a separate disk and NOT on the same physical disk as your

4. In the Operating System window select your required guest operating system. Note the large list of Microsoft-based operating systems. If you plan to install a non-Microsoft OS then choose "Other".

5. In the Memory window note that Virtual PC tries its best to determine the recommended amount of RAM to allocate to the new Guest VM based upon your selection in the previous step. You can manually change that setting.

6. In the Virtual Hard Disk Options window click to select A New Virtual Hard Disk. If you've already created the hard disk in a different manner (read my "How to create a new Virtual Machine (Hyper-V) " article for more info), then select An Existing Hard Disk.

7. In the Virtual Hard Disk Location window browse to the location of the new hard disk, and give it a proper name. Try to be as specific as possible and try to place each VM in its own folder. You need to specify the size of the new virtual hard disk. Make sure you'll have enough space on it to install whatever OS that you want, and also plan for any additional software or services.

Note: Virtual PC uses dynamically expanding disks, meaning they start out as small .VHD files, but the VM itself "sees" them in their full size. As space is taken on the virtual hard disk by the VM, the size of the .VHD file increases.
10. When you're done click Finish. Your new VM is ready to boot.

Some PowerShell Commands

noreply@blogger.com (mushtaqnaik) — Mon, 27 Dec 2010 10:22:00 +0000

Some PowerShell Commands Every Windows Admin should Know

Almost all the newer Microsoft server products require PowerShell, and there are lots of management tasks that can't be accomplished without delving into the command line. As a Windows administrator, you need to be familiar with the basics of using PowerShell. Here are some commands to start with

1: Get-Help

The first PowerShell cmdlet every administrator should learn is Get-Help. You can use this command to get help with any other command. For example, if you want to know how the Get-Process command works, you can type:

Get-Help –Name Get-Process

And Windows will display the full command syntax.

You can also use Get-Help with individual nouns and verbs. For example, to find out all the commands you can use with the Get verb, type:

Get-Help –Name Get-*

2: Set-ExecutionPolicy

Although you can create and execute PowerShell scripts, Microsoft has disabled scripting by default in an effort to prevent malicious code from executing in a PowerShell environment. You can use the Set-ExecutionPolicy command to control the level of security surrounding PowerShell scripts. Four levels of security are available to you:

Restricted -- Restricted is the default execution policy and locks PowerShell down so that commands can be entered only interactively. PowerShell scripts are not allowed to run.

All Signed -- If the execution policy is set to All Signed then scripts will be allowed to run, but only if they are signed by a trusted publisher.

Remote Signed -- If the execution policy is set to Remote Signed, any PowerShell scripts that have been locally created will be allowed to run. Scripts created remotely are allowed to run only if they are signed by a trusted publisher.

Unrestricted -- As the name implies, Unrestricted removes all restrictions from the execution policy.

You can set an execution policy by entering the Set-ExecutionPolicy command followed by the name of the policy. For example, if you wanted to allow scripts to run in an unrestricted manner you could type:

Set-ExecutionPolicy Unrestricted

3: Get-ExecutionPolicy

If you're working on an unfamiliar server, you'll need to know what execution policy is in use before you attempt to run a script. You can find out by using the Get-ExecutionPolicy command.

4: Get-Service

The Get-Service command provides a list of all of the services that are installed on the system. If you are interested in a specific service you can append the –Name switch and the name of the service (wildcards are permitted) When you do, Windows will show you the service's state.

5: ConvertTo-HTML

PowerShell can provide a wealth of information about the system, but sometimes you need to do more than just view the information onscreen. Sometimes, it's helpful to create a report you can send to someone. One way of accomplishing this is by using the ConvertTo-HTML command.

To use this command, simply pipe the output from another command into the ConvertTo-HTML command. You will have to use the –Property switch to control which output properties are included in the HTML file and you will have to provide a filename.

To see how this command might be used, think back to the previous section, where we typed Get-Service to create a list of every service that's installed on the system. Now imagine that you want to create an HTML report that lists the name of each service along with its status (regardless of whether the service is running). To do so, you could use the following command:

Get-Service | ConvertTo-HTML –Property Name, Status > C:\services.htm

6: Export-CSV

Just as you can create an HTML report based on PowerShell data, you can also export data from PowerShell into a CSV file that you can open using Microsoft Excel. The syntax is similar to that of converting a command's output to HTML. At a minimum, you must provide an output filename. For example, to export the list of system services to a CSV file, you could use the following command:

Get-Service | Export-CSV c:\service.csv

7: Select-Object

If you tried using the command above, you know that there were numerous properties included in the CSV file. It's often helpful to narrow things down by including only the properties you are really interested in. This is where the Select-Object command comes into play. The Select-Object command allows you to specify specific properties for inclusion. For example, to create a CSV file containing the name of each system service and its status, you could use the following command:

Get-Service | Select-Object Name, Status | Export-CSV c:\service.csv

8: Get-EventLog

You can actually use PowerShell to parse your computer's event logs. There are several parameters available, but you can try out the command by simply providing the –Log switch followed by the name of the log file. For example, to see the Application log, you could use the following command:

Get-EventLog –Log "Application"

Of course, you would rarely use this command in the real world. You're more likely to use other commands to filter the output and dump it to a CSV or an HTML file.

9: Get-Process

Just as you can use the Get-Service command to display a list of all of the system services, you can use the Get-Process command to display a list of all of the processes that are currently running on the system.

10: Stop-Process

Sometimes, a process will freeze up. When this happens, you can use the Get-Process command to get the name or the process ID for the process that has stopped responding. You can then terminate the process by using the Stop-Process command. You can terminate a process based on its name or on its process ID. For example, you could terminate Notepad by using one of the following commands:

Stop-Process –Name notepad

Stop-Process –ID 2668

Keep in mind that the process ID may change from session to session.

11: Get-Acl

This will give you a quick report of your security rights to the specified path (note that it won’t give the share access). That alone is nothing too exciting, as it will report only the single specified path, but if you want to include recursion for the entire path, you can use other strategies. For the same path (N:\Data), you’d use the Get-ChildItem command (cmdlet) within PowerShell, combined with the Get-Acl command. For example:

PS E:\>Get-ChildItem N:\Data -recurse | Get-Acl

This will span the entire N:\Data path and display the ACLs for the contents of the path. What happens here is that the Get-ChildItem provides an inventory of the file system objects, and that collection is passed to Get-Acl to provide the results for each item.

If you want to archive this to a comma-separated variable (CSV) document, you pass “| export-csv c:\filename.csv” at the end of the cmdlet. You can also pass the normal “> C:\filename.txt” to the end of the command to get it exported to a text file. Note that when you use the –recurse option, it does just that and will traverse the entire path you specify. So be careful when doing it across a large volume or over the network.

Installing IIS 7 on Windows Server 2008

noreply@blogger.com (mushtaqnaik) — Fri, 10 Dec 2010 20:13:00 +0000

Before going to start lets have a look on IIS in Recent Times
If you think back a few years to IIS 5.0, the future for Microsoft's web server looked rather bleak, because network-savvy worms such as Nimda, Code Red, Code Red II, and their variants were affecting thousands of computers worldwide, and rapidly damaging IIS's reputation. Microsoft introduced the IIS lockdown tool to combat these exploits and, with the release of IIS 6.0, made "locked down" mode settings the default at installation, which helped minimize such security problems, and helped IIS 6.0 recapture a major part of trust that IIS 5.0 lost. No major security disasters have been reported since the release of IIS 6.0.

A market survey (Netcraft Web Server Survey—April 2007 ) indicated that Microsoft's IIS has a 31.13 percent market share, which places it in second position behind the open source Apache Web Server. Another survey by Port80 Software that takes Fortune 1000 companies into consideration reports that IIS has overtaken Apache among Fortune 1000 sites.

Figure 1. IIS 7.0 Core Components: IIS 7.0 is composed of three core components.
Now, Microsoft is looking to consolidate IIS 7.0's position as a secure and robust web server.

Figure 1.

IIS 7.0 Core Components
IIS 7.0's core components differ from those in IIS 6.0. IIS 7.0 is made up of three core components as illustrated in Figure 1.

Protocol Listeners: A protocol listener listens to specific requests based on a specific protocol and sends the request to the IIS worker process for processing. Protocol listeners provided with IIS 7.0 include HTTP.sys, NET.TCP, NET.MSMQ and NET.PIPE.
WWW Service: This service acts as a listener adapter for the HTTP.sys protocol listener and monitors the HTTP requests.
Windows Activation Service (WAS): WAS is a new service in IIS 7.0 that manages application pool configuration and worker processes. In IIS 6.0, this responsibility was part of the WWW Service. The shift to a separate core component ensures that developers can use the same process model and configuration for both HTTP and non-HTTP based sites. It is possible to configure the other three protocol listeners (NET.TCP, NET.MSMQ and NET.PIPE) using WAS.

Figure 2. IIS 7.0 Pillars: The figure shows the five major focus areas of IIS 7.0 in which Microsoft made improvements.
For example, when the NET.TCP protocol listener is configured it listens for TCP requests. WAS can also be used to host a Windows Communication Foundation (WCF) based service.

Figure 2.

IIS 7.0 Pillars
Apart from the change in the core components Microsoft made various changes in five major focus areas. These five areas (see Figure 2) form the pillars of IIS 7.0.

Now Installing IIS 7 on Windows Server 2008

2. In Server Manager scroll down to Roles Summary, and click on Add Roles

3. The Add Roles Wizard starts at this point and warns you that if you are going to add a role to make sure:
The administrator account has a strong password
Network settings, such as static IP, are configured
The latest security updates from Windows Updates are installed

4. Click Next to go the Add Server Role page. Place a checkmark next to Web Server (IIS) and then click on the button Next

5. The next page will give you some basic information on IIS Web Servers and a few links with extra information if needed. Click on the button Next to continue

6. The next window is the Select Role Services. This very important screen will allow you to add only the modules necessary for your planned installation of IIS.
When you choose a module in this screen in the upper right corner you will get more information about what the module is for. For our example we are going to load the following modules:
Static Content – Lets the Web server publish static Web file formats, such as HTML pages and image files.

Use Static Content to publish files on your Web server that users can view using a Web browser.
Default Document – Lets you configure a default file for the Web server to return when users do not specify a file in a URL.

Default Documents make it easier and more convenient for users to reach your Web site.
HTTP Errors – Allows you to customize the error messages returned to users’ browsers when the Web server detects a fault condition.

Use HTTP Errors to provide users with a better user experience when they run up against an error message. Consider providing users with an e-mail address for staff who can help them resolve the error.
HTTP Redirection – Provides support to redirect user requests to a specific destination.

Use HTTP redirection whenever you want customers who are using one URL to actually end up at another URL. This is helpful in many situations, from simply renaming your Web site, to overcoming a domain name that is difficult to spell, or forcing clients to use a secure channel.
HTTP Logging – Provides logging of Web site activity for this server.

When a loggable event, usually an HTTP transaction, occurs, IIS calls the selected logging module, which then writes to one of the logs stored in the files system of the Web server. These logs are in addition to those provided by the operating system.
Request Filtering – Screens all incoming requests to the server and filters these requests based on rules set by the administrator.

Many malicious attacks share common characteristics, like extremely long requests, or requests for an unusual action. By filtering requests, you can attempt to mitigate the impact of these types of attacks.
IIS Management Console – Provides infrastructure to manage IIS 7 by using a user interface.

You can use the IIS management console to manage a local or remote Web server that runs IIS 7. To manage SMTP or FTP, you must install and use the IIS 6 Management Console.

7. Click Next to get to the Confirm Installation Selections screen to verify your chosen settings.

8. Click Install and installation will start

9. After installation you should see the Installation Results page. Click Close to finish the process.

10. In the Server Manager window, under Roles Summary, you should now see Web Server (IIS)

11. Let’s go ahead and open IIS Manager by going to Start -> Administrative Tools -> Internet Information Services (IIS) Manager

12. Once IIS Manager opens, expand out the web server and then expand the Sites folder. Right click on sites and then click on Add Web Site

13. In the Add Web Site window we have some basic information to fill out for a static site:
Site Name – Name of the site, this will be either domain.com or *.domain.com (Where * would represent a sub domain name such as www or blog for example)
Physical Path – The location on the local server that will hold the files for the website. If you did not set this up beforehand you can create a folder through this interface
Type – choose either http or https depending on whether your site will use Secure Socket Layer (SSL) certificate or not
IP Address – From the dropdown you can specify what IP the website should answer on or use the default switch of All Unassigned
Host Name – If you would like this site to respond to other domain names you can put these here

You have now installed IIS 7 and configured a static website. Just place your html files in the directory you specified when creating the site and you are good to go.

How DNS Recursive Queries Work

noreply@blogger.com (mushtaqnaik) — Thu, 09 Dec 2010 11:46:00 +0000

The basic concept of DNS name resolution is fairly simple. Every Web site is assigned a unique IP address. In order to access a website, a client needs to know what the site’s IP address is. Of course users don't usually enter an IP address into their Web browser, but rather enter the site's domain name instead. In order to access the requested website, the Web browser must be able to convert the site's domain name into the corresponding IP address. This is where DNS comes into play. The client computer is configured with the address of a preferred DNS server. The requested URL is forwarded to the DNS server, and the DNS server returns the IP address for the requested website. The client is then able to access the requested site.

As you can see, the name resolution process is pretty cut and dry. However, there are countless websites in the world, and new sites are being created every day. It is impossible for your DNS server to know the IP address of every single website. When a DNS server does not know the address for a requested site, it uses one of two methods to determine the site's IP address.

The preferred name resolution method is called recursion. Generally speaking, recursion refers to the process of having the DNS server itself to make queries to other DNS servers on behalf of the client who made the original request. In essence, the DNS server becomes a DNS client. Some administrators prefer to disable recursion for performance reasons. If recursion is disabled, then the DNS server uses a process called iteration to resolve the name request.

Root Hints

If the DNS server does not know the address of the requested site, then it will forward the request to another DNS server. In order to do so, the DNS server must know of the IP address of another DNS server that it can forward the request to. This is the job of root hints. Root hints provided a list of IP addresses of DNS servers that are considered to be authoritative at the root level of the DNS hierarchy.

The good news is that root hints are preconfigured on Windows Server 2003 DNS servers. The root hints are stored in a file named CACHE.DNS that is located in the \Windows\System32\Dns folder. If you would like to see what the root hints file looks like, you can open it in Notepad. As you can see in Figure A, the root hints file is really nothing more than just a text file that pairs root DNS servers with their IP addresses.

Figure A: The root hints file matches root level DNS servers with their IP addresses

Now that I have talked about what the root hints are and what they do, let’s take a look at the recursion process in action. The diagram shown in Figure B illustrates the example that I am about to walk you through.

Figure B: This is how DNS recursion works

The process begins when the user enters a URL into their Web browser. For the purpose of this example, let’s assume that the user has entered www.contoso.com as the URL. Upon doing so, the request to resolve the Contoso.com domain into an IP address is passed to the workstation’s preferred DNS server. Often times the preferred DNS server will have already cached the requested record, but for the sake of this example, let’s assume that the preferred DNS server has no information related to CONTOSO.COM.

Assuming that DNS recursion is enabled, the DNS server begins acting as a DNS client and launches a series or iterative queries against other DNS servers. I will discuss the difference between iterative and recursive queries later on, but for now just realize that the process as a whole is considered to be recursive because the client only makes one request to the preferred DNS server.

At any rate, the workstation’s preferred DNS server doesn’t know the IP address of the www.contoso.com Web site, and it doesn’t know the IP address of a DNS server that is authoritative for the Contoso.com domain (and would therefore know the IP address of the www.contoso.com Web site). What the DNS server does know is the IP address to a root level DNS server (thanks to the root hints file). Therefore, the preferred DNS server forwards the request to the root DNS server.

The root DNS server doesn’t have a clue as to the IP address of the www.contoso.com Web server. What it does know is the IP address of a DNS server that is responsible for the .COM domain. The root DNS server returns the IP address of the DNS server responsible for the .COM domain to the preferred DNS server. The preferred DNS server then sends the client’s request to the .COM DNS server. The .COM DNS server doesn’t know the IP address of the www.contoso.com Web site, but it does know the IP address of the DNS server that is authoritative for the Contoso.com domain. The .com domain server returns the IP address of the DNS server that is authoritative for the Contoso.com domain. The client’s preferred DNS server then sends the request to the Contoso.com DNS server, which in turn returns the IP address for the requested Web site. This address is then returned to the client who requested it.

There are two things worth noting in this example. First, as I explained earlier, the client only made a single DNS query. It was completely unaware of the DNS server’s iterative queries on its behalf. Second, the DNS server that is authoritative for the CONTOSO.COM domain would not necessarily be owned by Contoso. Typically, this DNS server would be owned by a Web hosting company and would be authoritative for any sites hosted by the company. That’s why the preferred DNS server can’t skip a step and just give the client the address for the DNS server that is authoritative for the domain; at least not in this case.

If a DNS server is configured to not support recursive queries, then clients will perform iterative queries by default.

If you are interested in obtaining the best performance, then you should configure your DNS server to allow recursive queries. The reason is because if clients are forced to use iterative queries, then they could potentially issue three or four queries to the DNS server for every name resolution request. The DNS server will have to perform all these queries whether recursive or iterative queries are being used, but when recursion is used, most of the name resolution requests are handled by your DNS server and are kept off of your network. This reduces the amount of traffic flowing across the network, thereby improving performance.

How To enable remote connection on SQL Server 2008 Express

noreply@blogger.com (mushtaqnaik) — Sat, 04 Dec 2010 14:49:00 +0000

In this Post I will explain you how to connect SQL server Express Edition 2008 Remotely.When we try to connect SQL Remotely we will receive following error messages

“Cannot connect to SQL-Server-Instance-Name
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005 (Same for 2008), this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol) (Microsoft SQL Server)”

“Cannot connect to SQL-Server-Instance-Name
Login failed for user ‘username‘. (Microsoft SQL Server, Error: 18456)

To enable remote connection on SQL Server 2008 Express, see the step below:

Start SQL Server Browser service if it’s not started yet. SQL Server Browser listens for incoming requests for Microsoft SQL Server resources and provides information about SQL Server instances installed on the computer.
Enable TCP/IP protocol for SQL Server 2008 Express to accept remote connection.
(Optional) Change Server Authentication to SQL Server and Windows Authentication. By default, SQL Server 2008 Express allows only Windows Authentication mode so you can connect to the SQL Server with current user log-on credential. If you want to specify user for connect to the SQL Server, you have to change Server Authentication to SQL Server and Windows Authentication.

Note: In SQL Server 2008 Express, there isn’t SQL Server Surface Area Configuration so you have to configure from SQL Server Configuration Manager instead.

Step-by-step

Open SQL Server Configuration Manager. Click Start -> Programs -> Microsoft SQL Server 2008 -> Configuration Tools -> SQL Server Configuration Manager.

On SQL Server Configuration Manager, select SQL Server Services on the left window. If the state on SQL Server Browser is not running, you have to configure and start the service. Otherwise, you can skip to step 6.

Double-click on SQL Server Browser, the Properties window will show up. Set the account for start SQL Server Browser Service. In this example, I set to Local Service account.

On SQL Server Browser Properties, move to Service tab and change Start Mode to Automatic. Therefore, the service will be start automatically when the computer starts.
Click OK to apply changes.

Back to SQL Server Configuration Manager, right-click on SQL Server Bowser on the right window and select Start to start the service.

On the left window, expand SQL Server Network Configuration -> Protocols for SQLEXPRESS. You see that TCP/IP protocol status is disabled.

Right-click on TCP/IP and select Enable to enable the protocol.

There is a pop-up shown up that you have to restart the SQL Service to apply changes.

On the left window, select SQL Server Services. Select SQL Server (SQLEXPRESS) on the right window -> click Restart. The SQL Server service will be restarted.

Open Microsoft SQL Server Management Studio and connect to the SQL Server 2008 Express.

Right-click on the SQL Server Instance and select Properties.

On Server Properties, select Security on the left window. Then, select SQL Server and Windows Authentication mode.

Again, there is a pop-up shown up that you have to restart the SQL Service to apply changes

Right-click on the SQL Server Instance and select Restart

That’s it. Now you should be able to connect to the SQL Server 2008 Express remotely

How to Run a Program in Compatibility Mode in Windows 7

noreply@blogger.com (mushtaqnaik) — Sat, 08 May 2010 16:03:00 +0000

OPTION ONE

________________________________________
Through Properties Page
1. Right click on the program's shortcut, .exe file, or installation program.

2. Click on Properties.

3. Click on the Compatibility tab. (see screenshot below)

4. To Run a Program in Compatibility Mode -
NOTE: Runs the program using settings from a previous version of Windows. Try this setting if you know the program is designed for (or worked in) a specific previous version of Windows.
A) Check the Run this program in compatibility mode for box. (see screenshot below)

B) Click on the drop down menu arrow and select which version of Windows the program was made for. (see screenshot below)
NOTE: Always pick the latest Windows version the program was written for to have a better chance of it running properly in Windows 7.

Warning
MSI files will only have the Previous version of Windowsoption available for it. This option will allow Windows 7 to automatically use the previous version compatibility mode it thinks is best for the MSI file to run properly as. You will not be able to do steps 5 and 6 below.

5. To Change the Settings for a Program -
A) Check or uncheck the settings you want for the program. (see screenshot below)
NOTE: See the table below the screenshot for a description of each setting.

Setting Description
Run in 256 colors Uses a limited set of colors in the program. Some older programs are designed to use fewer colors.
Run in 640 × 480 screen resolution Runs the program in a smaller-sized window. Try this setting if the graphical user interface appears jagged or is rendered improperly.
Disable visual themes Disables themes on the program. Try this setting if you notice problems with the menus or buttons on the title bar of the program.
Disable desktop composition Turns off transparency and other advanced display features. Choose this setting if window movement appears erratic or you notice other display problems.
Disable display scaling on high DPI settings Turns off automatic resizing of programs if large-scale font size (DPI) is in use. Try this setting if large-scale fonts are interfering with the appearance of the program.

6. To Change the Privilege Level of a Program -
NOTE: Runs the program as an administrator. Some programs require administrator privileges to run properly. If you are not currently logged on as an administrator, this option is not available.
A) Check or uncheck the Run this program as an administrator box to enable or disable this option. (see screenshot below)

7. To Change All of These Settings Above for All Users -
NOTE: Lets you choose settings that will apply to all users on this computer.
A) Click on the Change settings for all users button. (See screenshot below)

B) Repeat steps 4, 5, and 6 in this window to apply them to all users on the computer. (see screenshot below)

C) Click on OK.

8. Click on OK to apply the changes.

OPTION TWO
________________________________________
Through Troubleshoot Compatibility

Note
This option is to troubleshoot compatibility of a program by using a wizard to let Windows 7 help decide what is best to try and make the program compatible.
1. Right click on the program's shortcut, .exe file, or installation program, and click onTroublshoot compatibility. (see screenshot below)

NOTE: You will not have the Troublshoot compatibility option available for pinned items in theStart Menu or on the taskbar.

2. You will see this for a moment while Windows 7 is detecting what the issues may be with the program. (see screenshot below)

3. The wizard will now give you a list of choices to choose from. Select the option you would like to try, then follow the rest of the onscreen instructions until you are through troubleshooting the compatibility issue with the program. (see screenshot below)

How To Reset Terminal Sessions Remotely

noreply@blogger.com (mushtaqnaik) — Thu, 29 Apr 2010 06:42:00 +0000

In this Post i am going to show you How to Query and Rest the Terminal Sessions Remotely.
You must be aware that only two users are allowed for Remote Administration, if third one tries to login on the same Machine he/she will receive an error message "Exceeded the number of terminal connections". This may happen if two people are legitimately using the servers or if someone forgot to log off. Now think if your servers are far away from you and you are facing this problem :(
Now no worries, here you will find how to reset the Terminal Sessions Remotely :)

Note:- To use these commands you must have the admin credentials and same username/password that is on the Remote Machine which you want to Reset.

For example, let's say that I can't gain access to a server (with ip:- 192.168.1.10) using Terminal Services because both sessions are used up. I can use another server to check the status of the first one. As long as the logged in user has administrative rights on the non-accessible machine I would run this:

qwinsta /server:192.168.1.10

Where 192.168.1.10 is the IP address or name of the non-accessible machine.

This will display something like this:

Now I know that Naik and Sabu are the two that are logged in. Since Sabu left the office 1 hour ago I know that he forgot to log off and Naik has done same thing forgot to log off. Now i need to reset one of the session then i will be able to login

To disconnect Sabu's session I would type this:

rwinsta /server:192.168.1.10 3

Notice the 3 which is the session ID I found from using qwinsta above.

The qwinsta and qwinsta stands for

qwinsta = Query WINdows STAtion
rwinsta = Reset WINdows STAtion

Microsoft has replaced these two tools with Query but since qwinsta and rwinsta is fully compatible with W2K WinXP and W2K3.

So you can use below Commands as well

To displays information about sessions on a remote terminal server.

query session /server:192.168.1.10 (Same as qwinsta)

Note:- 192.168.1.10 is a remote machine ip.

To reset (delete) a session on a terminal server.

reset session /server:192.168.1.10 3 (Same as rwinsta)

Note:- 3 is a session ID

MIME Types and Role of MIME in IIS 6.0

noreply@blogger.com (mushtaqnaik) — Tue, 27 Apr 2010 17:42:00 +0000

Role of MIME

MIME is short for Multipurpose Internet Mail Extensions, a specification for formatting non-ASCII messages so that they can be sent over the Internet. Many e-mail clients now support MIME, which enables them to send and receive graphics, audio, and video files via the Internet mail system.
There are many predefined MIME types, such as GIF graphics files and PostScript files. It is also possible to define your own MIME types.
In addition to e-mail applications, Web browsers also support various MIME types. This enables the browser to display or output files that are not in HTML format.
MIME was defined in 1992 by the Internet Engineering Task Force (IETF).

File type	MIME type
ai	application/postscript
aif	audio/x-aiff
aifc	audio/x-aiff
aiff	audio/x-aiff
asc	text/plain
atom	application/atom+xml
au	audio/basic
avi	video/x-msvideo
bcpio	application/x-bcpio
bin	application/octet-stream
bmp	image/bmp
cdf	application/x-netcdf
cgm	image/cgm
class	application/octet-stream
cpio	application/x-cpio
cpt	application/mac-compactpro
csh	application/x-csh
css	text/css
dcr	application/x-director
dif	video/x-dv
dir	application/x-director
djv	image/vnd.djvu
djvu	image/vnd.djvu
dll	application/octet-stream
dmg	application/octet-stream
dms	application/octet-stream
doc	application/msword
dtd	application/xml-dtd
dv	video/x-dv
dvi	application/x-dvi
dxr	application/x-director
eps	application/postscript
etx	text/x-setext
exe	application/octet-stream
ez	application/andrew-inset
gif	image/gif
gram	application/srgs
grxml	application/srgs+xml
gtar	application/x-gtar
hdf	application/x-hdf
hqx	application/mac-binhex40
htm	text/html
html	text/html
ice	x-conference/x-cooltalk
ico	image/x-icon
ics	text/calendar
ief	image/ief
ifb	text/calendar
iges	model/iges
igs	model/iges
jnlp	application/x-java-jnlp-file
jp2	image/jp2
jpe	image/jpeg
jpeg	image/jpeg
jpg	image/jpeg
js	application/x-javascript
kar	audio/midi
latex	application/x-latex
lha	application/octet-stream
lzh	application/octet-stream
m3u	audio/x-mpegurl
m4a	audio/mp4a-latm
m4b	audio/mp4a-latm
m4p	audio/mp4a-latm
m4u	video/vnd.mpegurl
m4v	video/x-m4v
mac	image/x-macpaint
man	application/x-troff-man
mathml	application/mathml+xml
me	application/x-troff-me
mesh	model/mesh
mid	audio/midi
midi	audio/midi
mif	application/vnd.mif
mov	video/quicktime
movie	video/x-sgi-movie
mp2	audio/mpeg
mp3	audio/mpeg
mp4	video/mp4
mpe	video/mpeg
mpeg	video/mpeg
mpg	video/mpeg
mpga	audio/mpeg
ms	application/x-troff-ms
msh	model/mesh
mxu	video/vnd.mpegurl
nc	application/x-netcdf
oda	application/oda
ogg	application/ogg
pbm	image/x-portable-bitmap
pct	image/pict
pdb	chemical/x-pdb
pdf	application/pdf
pgm	image/x-portable-graymap
pgn	application/x-chess-pgn
pic	image/pict
pict	image/pict
png	image/png
pnm	image/x-portable-anymap
pnt	image/x-macpaint
pntg	image/x-macpaint
ppm	image/x-portable-pixmap
ppt	application/vnd.ms-powerpoint
ps	application/postscript
qt	video/quicktime
qti	image/x-quicktime
qtif	image/x-quicktime
ra	audio/x-pn-realaudio
ram	audio/x-pn-realaudio
ras	image/x-cmu-raster
rdf	application/rdf+xml
rgb	image/x-rgb
rm	application/vnd.rn-realmedia
roff	application/x-troff
rtf	text/rtf
rtx	text/richtext
sgm	text/sgml
sgml	text/sgml
sh	application/x-sh
shar	application/x-shar
silo	model/mesh
sit	application/x-stuffit
skd	application/x-koan
skm	application/x-koan
skp	application/x-koan
skt	application/x-koan
smi	application/smil
smil	application/smil
snd	audio/basic
so	application/octet-stream
spl	application/x-futuresplash
src	application/x-wais-source
sv4cpio	application/x-sv4cpio
sv4crc	application/x-sv4crc
svg	image/svg+xml
swf	application/x-shockwave-flash
t	application/x-troff
tar	application/x-tar
tcl	application/x-tcl
tex	application/x-tex
texi	application/x-texinfo
texinfo	application/x-texinfo
tif	image/tiff
tiff	image/tiff
tr	application/x-troff
tsv	text/tab-separated-values
txt	text/plain
ustar	application/x-ustar
vcd	application/x-cdlink
vrml	model/vrml
vxml	application/voicexml+xml
wav	audio/x-wav
wbmp	image/vnd.wap.wbmp
wbmxl	application/vnd.wap.wbxml
wml	text/vnd.wap.wml
wmlc	application/vnd.wap.wmlc
wmls	text/vnd.wap.wmlscript
wmlsc	application/vnd.wap.wmlscriptc
wrl	model/vrml
xbm	image/x-xbitmap
xht	application/xhtml+xml
xhtml	application/xhtml+xml
xls	application/vnd.ms-excel
xml	application/xml
xpm	image/x-xpixmap
xsl	application/xml
xslt	application/xslt+xml
xul	application/vnd.mozilla.xul+xml
xwd	image/x-xwindowdump
xyz	chemical/x-xyz
zip	application/zip

Role of MIME in IIS 6.0

IIS 6.0 does not serve unknown MIME types

When you request a file from an IIS 6.0 Web server, and the file has a file name extension that is not a defined MIME type on the Web server, we will receive the following error message:
HTTP Error 404 - File or directory not found.

CAUSE
The earlier versions of IIS include a wildcard character MIME mapping, which permits IIS to serve any file regardless of its extension. IIS 6.0 does not include this wildcard character MIME mapping and does not serve any type of extension that is not defined at the MimeMap node in the IIS metabase.
To Resolve this we need to follow these steps
1. Open the IIS Microsoft Management Console (MMC), right-click the local computer name, and then click Properties.
2. Click MIME Types.
3. Click New.
4. In the Extension box, type the file name extension that you want (for example, .mp4).
5. In the MIME Type box, type .mp4/video/mp4
6. Apply the new settings. Note that we must restart the World Wide Web Publishing Service or wait for the worker process to recycle for the changes to take effect. In this example, IIS now serves files with the .mp4 extension.

If we want to serve all files regardless of the file name extension (for example, if we cannot predict all files that will be served), then need to follow these steps to add a wildcard character mapping:

1. Open the IIS Microsoft Management Console (MMC), right-click the local computer name, and then click Properties.
2. Click MIME Types.
3. Click New.
4. In the Extension box, type an asterisk (*).
5. In the MIME Type box, type application/octet-stream.
6. Apply the new settings. Note that we must restart the World Wide Web Publishing Service or wait for the worker process to recycle for the changes to take effect.

Note:- In addition to making these changes at the global level in IIS, we can add necessary MIME types at lower levels in the metabase. When we do this, we can specify the sites or directories that are permitted to serve content with a specific file name extension instead of globally allowing all sites to serve that extension.

How to Update Your Twitter And FaceBook Status When You Add A New Post On Blogger

noreply@blogger.com (mushtaqnaik) — Thu, 22 Apr 2010 13:01:00 +0000

Hi everybody, today i am going to show you How to update your Twitter and FaceBook Status automatically when you create a new POST in Blogger.
Lets Start, only Four step Process

Step 1: Go to TwitterFeed.com, And click register now. Then fill the form and click Create account.

Step 2: Name Feed & Add Source URL.
You’ll need to enter your
- Feed Name
- RSS Feed URL, your default blog url should be the following. http://yourblogname.blogspot.com/feeds/comments/full
Or you can enter your feedburner url if you are a member of feedburner.

Step 3: Configure Publishing Services.
In this step you will be able to Authenticate your accounts in Twitter, facebook, Laconica, Ping.fm and Hellotxt with your twitterfeed.com account,
For example click on Facebook, on the next page, click Connect with facebook, a new window will be opened, enter your facebook e-mail and password and click connect Then click allow access and click create service

And after you add and Authenticate all your accounts click All Done.

Step 4: Done.
On this step just click Go to dashboard. From your dashboard you can add, edit or remove services from your account.

And now you are done. And this will be updating Every hour.

How to use Sun Virtual Box for Virtualization

noreply@blogger.com (mushtaqnaik) — Tue, 20 Apr 2010 17:47:00 +0000

Today i am going to show you how to use Sun Virtual Box for Virtualization, in my previous post i used VMware and Hyper-v Technology for Virtualization. The VirtualBox Open Source Edition is licensed under the GPL.

How to create a new Virtual Machine (Hyper-V)

noreply@blogger.com (mushtaqnaik) — Fri, 16 Apr 2010 05:04:00 +0000

Hi, in my previous Post i showed you how to Clone a VM in Hyper-V . So in this Post i will show you How to Create a New VM and use existing VHD (Virtual Hard Disk)

Here we go to start:-
To add a new Guest Virtual Machine, Launch Hyper-V Manager from “Administrative Tools” and connect to the server with the Hyper-V Role
In the Actions Menu on the right, click “New“. Click Next on the “Before you begin” wizard introduction window.

In the Specify Name and Location window, Enter the name of the Guest Operating System. If you do not want to save the Virtual Machine in the default location then check the box for “Store the Virtual Machine in a different location” and browse and locate your new location. Once done, click Next.

In the Assign memory window, set the memory for the Guest OS and click Next. Default is 512MB.

In the Configure networking window, Select the Virtual Network (should have been created at the time of enabling the Hyper-V rols or can be done later on). If you choose the connect to the Virtual network later, select “Not connected” and click Next.

In the Connect Virtual Hard Disk window, create a new Virtual Hard disk and set its size. Here again, you can choose to save the disk in a different location than the defaults. Also, if you already have a Virtual Disk and want to use it (So in previous post we have copied a VDH, we can use that VHD here as well), you can do so or choose to attach a Virtual Hard Disk later. Once, Virtual Hard Disk (VHD) is created, click Next.

In the Installation Options window, choose the media to perform the installation. This could be your physica CD/DVD drive or an ISO image on the system or Floppy disk or even from a Network installation server. Choose the installation option and click Next.

In the Summary window, check your options and click Finish if all is good to go. Here you can choose to Start the Virtual Machine immediately after it is created. Default is to keep the VM OFF.

Now, you can see the new VM under the Virtual machines box in the Hyper-V Manager. When you click on it, in the bottom left, you can check the options specific to this virtual machine. The Settings option allows you to change any parameter like memory set at the time of creating the VM. One of the key thins to note is the “Integration Services” found under Management in the left pane. Integration services run under the guest operating system to provide some level of “integration” between the host and the guest OS like time sync, Guest OS backup etc.

Click Start under the VM or right-click and select Start to start the Virtual OS. This starts and runs in the background. Click Connect to actually, open a console session with the Guest OS.Depending on your Host system performance level you can run multiple Guest OSs at any given time.

Server 2008 : How to clone a VM in Hyper-v

noreply@blogger.com (mushtaqnaik) — Thu, 15 Apr 2010 06:31:00 +0000

There are two ways you can clone a VM in Hyper-V.

1. Using the import/export VM feature available in Hyper-V

2. Copying a Virtual Hard Disk and create a new VM using that Hard Disk.

1. Import/Export feature to clone a VM in Hyper-V
This is a simple and easy way to clone a Virtual Machine (VM). But, the only low side of it is that the import of VM will only work on any VM which was exported from a Hyper-V Virtual system.
Export VM
From the Hyper-V Manager, right-click on the VM and select Export. Choose a location where the exported VM will be saved. It is important to note that when you import this VM back from that location, its Virtual machine and virtual Hard Disk location will be set as this location and not the default location.

While exporting a VM, you can choose to export only the VM and not its Virtual hard Disk (VHD). This can be particularly useful when you want to create a new VHD and perform fresh install.

Import VM
To import the Virtual Machine (VM), click “Import Virtual Machine” from the Action menu in the right of the Hyper-V Manager. Browse to the location where the VM was exported to and then click Import.

Again, it is important to note that the location is the exact location to where original VM was exported to and not any of its sub-directories.
Once, the VM is imported, you can change the settings as you would with any other VM. If you bring this VM online in the same Virtual Network as that of the original VM and that the original VM is still live on that network then it would be ideal to disable the network on this newly imported VM and change the hostna,e,IP Address settings from within the VM to avoid any network issues.

2. Copy VHD and Create new VM
This is quick way doing a clone on a VM. Simply make a copy of the VHD from the original VM and use it when creating a new VM instead of creating a new VHD for that VM.

How to create a new VM and use existing VHD, that will be available in next Post

Installing IIS 7 on Windows Server 2008

noreply@blogger.com (mushtaqnaik) — Mon, 12 Apr 2010 17:16:00 +0000

Since the IIS web server is not installed by default, the first thing we have to do is install IIS as a role for the server we are working on.

1. Click on Start -> Administrative Tools -> Server Manager

2. In Server Manager scroll down to Roles Summary, and click on Add Roles

3. The Add Roles Wizard starts at this point and warns you that if you are going to add a role to make sure:

* The administrator account has a strong password
* Network settings, such as static IP, are configured
* The latest security updates from Windows Updates are installed

4. Click Next to go the Add Server Role page. Place a checkmark next to Web Server (IIS) and then click on the button Next

5. The next page will give you some basic information on IIS Web Servers and a few links with extra information if needed. Click on the button Next to continue

6. The next window is the Select Role Services. This very important screen will allow you to add only the modules necessary for your planned installation of IIS.

When you choose a module in this screen in the upper right corner you will get more information about what the module is for. For our example we are going to load the following modules:

* Static Content – Lets the Web server publish static Web file formats, such as HTML pages and image files.

Use Static Content to publish files on your Web server that users can view using a Web browser.

* Default Document – Lets you configure a default file for the Web server to return when users do not specify a file in a URL.

Default Documents make it easier and more convenient for users to reach your Web site.

* HTTP Errors – Allows you to customize the error messages returned to users’ browsers when the Web server detects a fault condition.

Use HTTP Errors to provide users with a better user experience when they run up against an error message. Consider providing users with an e-mail address for staff who can help them resolve the error.

* HTTP Redirection – Provides support to redirect user requests to a specific destination.

Use HTTP redirection whenever you want customers who are using one URL to actually end up at another URL. This is helpful in many situations, from simply renaming your Web site, to overcoming a domain name that is difficult to spell, or forcing clients to use a secure channel.

* HTTP Logging – Provides logging of Web site activity for this server.

When a loggable event, usually an HTTP transaction, occurs, IIS calls the selected logging module, which then writes to one of the logs stored in the files system of the Web server. These logs are in addition to those provided by the operating system.

* Request Filtering – Screens all incoming requests to the server and filters these requests based on rules set by the administrator.
Many malicious attacks share common characteristics, like extremely long requests, or requests for an unusual action. By filtering requests, you can attempt to mitigate the impact of these types of attacks.
* IIS Management Console – Provides infrastructure to manage IIS 7 by using a user interface.
You can use the IIS management console to manage a local or remote Web server that runs IIS 7. To manage SMTP or FTP, you must install and use the IIS 6 Management Console.

7. Click Next to get to the Confirm Installation Selections screen to verify your chosen settings.

8. Click Install and installation will start

9. After installation you should see the Installation Results page. Click Close to finish the process.

10. In the Server Manager window, under Roles Summary, you should now see Web Server (IIS)

11. Let’s go ahead and open IIS Manager by going to Start -> Administrative Tools -> Internet Information Services (IIS) Manager

12. Once IIS Manager opens, expand out the web server and then expand the Sites folder. Right click on sites and then click on Add Web Site

13. In the Add Web Site window we have some basic information to fill out for a static site:
* Site Name – Name of the site, this will be either domain.com or *.domain.com (Where * would represent a sub domain name such as www or blog for example)
* Physical Path – The location on the local server that will hold the files for the website. If you did not set this up beforehand you can create a folder through this interface
* Type – choose either http or https depending on whether your site will use Secure Socket Layer (SSL) certificate or not
* IP Address – From the dropdown you can specify what IP the website should answer on or use the default switch of All Unassigned
* Host Name – If you would like this site to respond to other domain names you can put these here

You have now installed IIS 7 and configured a static website. Just place your html files in the directory you specified when creating the site and you are good to go.

How to Install Mint OS through VMware

noreply@blogger.com (mushtaqnaik) — Sun, 11 Apr 2010 08:17:00 +0000

In this Video I am going to show you how to install Mint OS(Linux Code name :- Heena) through

VMware

Tips To Speed Up your Firefox Browser

noreply@blogger.com (mushtaqnaik) — Sat, 10 Apr 2010 16:01:00 +0000

First open about:config file and do below changes. To open about:config just open a new tab and write about:config, you will land on configuration.Then follow below instructions

1: Speed up Firefox

This hack requires a few steps. Search for pipelining in the filter and you should see:

network.http.pipelining: Change this to true.

network.http.proxy.pipelining: Change this to true.

network.http.pipelining.maxrequests: Change this to 8.

Now search for max-connections and you should see:

network.http.max-connections: Change this to 96.

network.http.max-connections-per-server: Change this to 32.

2: Disable antivirus scanning

This is only for the Windows version. If you're downloading large files, this scanning can seriously slow things down. And since you will most likely scan the downloaded file anyway, you'll probably want to disable this. Of course, if you are uber paranoid (not a bad trait for computing), you might want to leave this entry alone.

To disable antivirus scanning, search for scanWhenDone and you should see:

browser.download.manager.scanWhenDone: Change this to false.

3: Open Javascript popups as tabs

If a popup window lacks the features of a browser window, Firefox will handle it like a popup. If you would prefer to open all windows, including popups, as new tabs, you need to tell Firefox in about:config. Search for newwindow and you will see three entries. Of those three entries, you will want to modify:

browser.link.open_newwindow.restriction: Change this to 0.

4: Spell check in all fields

By default, Firefox checks spelling only in multiple-line text boxes. You can set it to check spelling in all text boxes. Search for spellcheckdefault and you should see:

layout.spellcheckDefault: Change this to 2.

5: Open search bar results in new tab

When you use the search bar, the results display in the current tab. This can be a nuisance because you will navigate out of the page you're currently in. To make sure Firefox always opens search results in a new tab, search for openintab and you should see:

browser.search.openintab: Change this to true.

6: Auto-export bookmarks

In Firefox 3, bookmarks are automatically saved and exported for you. The only problem is that by default, they're saved as places.sqlite instead of the more convenient bookmarks.html. To change this setting so that they can be easily re-imported, search for autoExportHTML and you should see:

browser.bookmarks.autoExportHTML: Change this to true.

7: Disable extension install delay

One of the few gripes I have with Firefox is the silly countdown you must endure every time you want to install an extension. Fortunately, this can be disabled. Search for enable_delay and you should see:

security.dialog_enable_delay: Change this to 0.

8: View source code in an external editor

When you need to view the source of a page, it opens up in browser popup. Most developers would probably like to have that opened in their favorite editor instead of having to cut and paset. To do this, there are two entries to modify. Search for view_source.editor and you will see:

view_source.editor.external: Change this to true.

view_source.editor.path: Change this to the explicit path to your editor of choice.

9: Get more add-on search results

When you do a search in the Add-on window, you'll see just five results. You might find it more efficient to increase this number. Search for getAddons and you should see:

extension.getAddons.maxResults: Change this to 10 (or higher, if you want to see even more).

10: Redefine the Backspace button
Did you know you can configure Firefox to use the backspace button to either go back a page or go up a page? This keeps power users from having to go back and forth from the keyboard to the mouse. Search for backspace and you will see:
browser.backspace_action: Change this to 0 for previous page and 1 for page up.

Important Note:- The Firefox about:config page is not so much a page as it is a somewhat hidden configuration section. It's hidden because it's fairly powerful and not nearly as simple to use as the standard Preferences window. In the about:config page, you have to know what you are doing or you can mess things up a bit. In fact, when you attempt to go to that page for the first time, you have to accept an agreement (which is really just a warning) before you can continue.

If by chance you have done some mistakes in Configuration then to retrive original Configuration you have to follow one of two ways

Make a backup of your prefs.js file before you start editing. Then, if something goes wrong, you can restore it by copying it over the corrupt file.
If you can't restore via a backup prefs.js file, you can exit Firefox and issue the command firefox -safe-mode to bring up the Firefox Safe Mode screen. Then, just select Reset All User Preferences To Firefox Defaults. Note: This will restore all user preferences to their default values.

How to Remove W32.Downadup.B Worm

noreply@blogger.com (mushtaqnaik) — Fri, 09 Apr 2010 19:49:00 +0000

W32.Downadup.B is a worm that tends to replicate itself through networks infecting all the subsidiary nodes and causing severe system trouble for each of the network units. W32.Downadup.B is known to contaminate target systems by exploiting Windows Server Service vulnerability. W32.Downadup.B has an enormous propagation scope – starting from December 2008 up till now, it has infected up to 20 million computers all over the planet. When operating, W32.Downadup.B disables the access to some domains and concurrently triggers the “Network request timed out” alert or some other similar one. W32.Downadup.B also creates a file in all the drives called ‘autorun.inf’, and schedules lot of tasks to run , this file is automatically executed. Once launched, autorun.inf will attempt to spot other machines connected to the infected one, in order to access them illicitly as well. W32.Downadup.B is hard to remove manually or using most spyware removal tools. If you suspect W32.Downadup.B in your system, you should immediately remove the system from network and disable file and printer sharing of infected system and perform a scan with a trusted utility, and if detected, eliminate W32.Downadup.B. And it’s preferable to put your firewall on and disable File and Printer Sharing allow only trusted systems.

How to remove W32.Downadup.B manually:

To perform manual removal of W32.Downadup.B worm, you should do the following:

Delete W32.Downadup.B corrupt files:

    * svchost.exe
    * explorer.exe
    * services.exe
    * %System%\[Random].dll
    * %Program Files%\Internet Explorer\[Random].dll
    * %Program Files%\Movie Maker\[Random].dll
    * %All Users Application Data%\[Random].dll
    * %Temp%\[Random].dll

Remove W32.Downadup.B registry entries:

    * HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\Folder\Hidden\SHO WALLCheckedValue = dword:00000000
    * HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SvcHost, netsvcs = %Previous data% and %Random%
    * HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\[random]\ParametersServiceDll = %MalwarePath%

Please, note that manual removal of W32.Downadup.B worm is a procedure of high complexity and should be performed with extreme caution. Lack of the required skills and even the slightest deviation from the instructions may lead to irreparable system damage. To ensure trouble-free deletion, it is recommended to use the automatic W32.Downadup.B removal tool below:

Click to Download and Get-rid of this Worm

How to Install XP Mode in Windows 7

noreply@blogger.com (mushtaqnaik) — Wed, 07 Apr 2010 17:04:00 +0000

In this Video i am going to show you that how to install XP Mode in Windows 7.

Hyper-V Technology:- Five Easy Steps to install Hyper-V for Virtualization in Server 2008

noreply@blogger.com (mushtaqnaik) — Wed, 07 Apr 2010 08:46:00 +0000

Virtualization refers to the concept of having multiple operating systems (OS) in a single PC. The installed OS can be Linux, Fedora, Windows, Solaris etc.

Hyper-V Technology in Windows Server 2008

HYPER-V is the latest release server role for Virtualization in Windows Server 2008 that allows you to run multiple OS in your single PC. The license for Virtual Server is free if you use Windows Server 2008.

If you are ready for Virtualization then here is the 5 simplest steps to install it.

Installing Hyper-V is very easy and supported by Windows Server 2008. However my recommendation is windows server R2 with service pack 2. Its good for Hyper-V.

Step 1: Goto control panel>>Administrative Tools>>Roles>>Add Roles

Step 2: From Select Server Roles, check on hyper-v.

Step 3: check Network Adapter (this helps you communicate with the virtual machine).

Step4: Next you get to the confirmation Section. You will see a dialogue box similar to this one.

Step 5: Hit the NEXT button and the installation process begins. You must see the following dialogue box

Now that your installation process is complete, you will get the screen display as:

Now the PC is virtualized by HYPER-V and you can start now multiple OS in your single PC. :)

Need To Consider Some Points before going for Virtualization

noreply@blogger.com (mushtaqnaik) — Tue, 06 Apr 2010 19:23:00 +0000

Server virtualization is becoming increasingly popular, and it seems that everyone is in a mad dash to virtualize their datacenter. While there’s no disputing the benefits of server virtualization, there are some questions you should address before you begin to virtualize your servers.

1. virtualization plan include a single point of failure?

I recently did a consulting job for an organization that had virtualized all of their servers. The problem was that they’d placed all of their virtualized domain controllers onto a single host server. If that host had died, it would have taken all the domain controllers with it. It’s important to plan your virtual server deployment so that the failure of a single host server will not have catastrophic consequences.

2. My applications supported in a virtual environment?

Believe it or not, some fairly common applications are not supported on virtual servers. For example, some versions of Exchange Server are supported only on physical servers. Others are supported only on specific virtualization platforms. Before you begin virtualizing your servers, make sure that your applications will be supported in a virtual environment.

3. Do I have any servers that are not good virtualization candidates?

Some servers simply do not make good virtualization candidates. This is especially true of servers that run resource-intensive applications or that require special hardware. For example, some enterprise applications enforce copy protection through the use of a dongle. Dongles are almost never supported in a virtual environment.

4. How will domain controller placement work?

Earlier, I mentioned that you shouldn’t place all of your domain controllers on a single host, but there is more to domain controller planning than that. You have to consider whether you want to virtualize all your domain controllers. If you do virtualize all of them, you will have to decide whether the host servers will be domain members. Making the host servers domain members when all of the domain controllers have been virtualized leads to a “which came first, the chicken or the egg” paradox (although it can be done).

5. What is the most suitable virtualization platform?

Numerous server virtualization products are on the market, and each has its own strengths and weaknesses. Be sure to take some time and figure out which product will work best for your own situation.

6. What is the contingency plan if a host server dies?

While a server failure is never good, its effects are compounded in a virtual environment. A host server failure can take down several virtual servers and cripple your network. Because host server failures can be so disruptive, you need to have a plan that will help minimize the impact of an outage.

7. How many guest machines can each host accommodate?

Probably the single biggest mistake administrators make when virtualizing a datacenter is overloading the host servers. It is critical that you do some capacity planning ahead of time to determine how many guest machines each host server can realistically accommodate. Since every guest machine is different, you need to at least have an idea of where you would like to place each guest machine when you begin the capacity planning process.

8. What software licenses will be required?

Software licensing often works differently in a virtual environment. For example, if you are using Hyper-V, you may not be required to license the Windows operating systems that are running on your guest machines. Things aren’t always so cut and dried, though, because the actual license requirements vary depending on the versions of Windows being used. Make sure that you understand the license requirements for the operating systems and applications that will be run on your guest machines.

9. How will the old server hardware be used?

The virtualization process often results in a number of leftover servers. You might be able to repurpose some of them as virtualization hosts, but you might end up having to retire them. In any case, you should have a plan for your old server hardware.

How to enable remote desktop on windows 7

noreply@blogger.com (mushtaqnaik) — Tue, 06 Apr 2010 18:37:00 +0000

Through this video you will be able to Enable Remote Desktop on Windows 7 and create a user with Remote Desktop Permissions :)

How to Change RDP Port Number

noreply@blogger.com (mushtaqnaik) — Tue, 06 Apr 2010 18:10:00 +0000

In this video you will be able to Change the RDP port number, by default the RDP port number is 3389, so you can change this by watching above video :)