Wednesday, November 20, 2013

0x8004010F: Outlook data file cannot be accessed.

Today I moved my .PST files and this is the error I received:
0x8004010F: Outlook data file cannot be accessed.
0x8004010F: The operation failed. An object could not be found.

Most of the forums I found suggest creating a new profile, this was not good news for me because I have 5 different email accounts in outlook. This is what fixed it for me:

1. From Outlook 2010 click File>Account Settings>Account Settings
2. Click Change Folder
3. Click New Outlook Data File (This is just temporary)
4. Give it a name (I used "Test")
5. Click the + to the left of the folder name to expand the subfolders. Click Inbox. Click OK.
6. Then Click Change Folder
7. Click Select the one you want
8. Click the + to the left of the folder name to expand the subfolders. Click Inbox. Click OK.
9. Close Account Settings and click send/receive.

Monday, May 6, 2013

How to Access WAMP Server in LAN or WAN


The WAMP server is very useful and is widely used open source. It works great when you are working in a local machine. But when you want to access the same WAMP server form a different machine on LAN or WAN then it’s not possible.

How to do this

Here are the steps to make WAM enabled on LAN or WAN:

Step 1

First you need to set up the WAMP service on your server and on the required services. And make sure that your WAMP server is online and it’s running on your browser using http://localhot:8081/ (I have given a fixed port number 8081 to my WAMP server).

To run the WAMP Apache server on your specified port, do the following. Go in the \wamp\bin\apache\Apache2.2.11\conf\httpd.conf file and search for “#Listen” and then change the port from 80 to 8081 and in that case, your URL will be http://localhost:8081/


Step 2

Now make the WMAP Server accessible in the LAN or WAN, you have to get \wamp\bin\apache\Apache2.2.11\conf\httpd.conf and open it and find the following code:
<Directory "cgi-bin">
 AllowOverride None Options None Order allow,deny Deny from all </Directory>

And change the above code to:
<Directory "cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory>

Step 3

Now you have to bind the server static IP to the port number (remember we gave done this in the start) so for this you have be on the same file and change “Listen 8081”  to “Listen [IP Address  of Server]:8081”. It will look  like “Listen”.

Step 4

Great! The next step is to open port (8081) of the server such that everyone can access your server. This depends on which OS you are using. Like if you are using Windows Vista, then follow the below steps.
Open Control Panel  >> System and Security >> Windows Firewall then click on “Advance Setting” and then select “Inbound Rules” from the left panel and then click on “Add Rule…”. Select “PORT” as an option from the list and then in the next screen select “TCP” protocol and enter port number “8081” under “Specific local port” then click on the ”Next” button and select “Allow the Connection” and then give the general name and description to this port and click Done.
Now you are done with PORT opening as well.
Next is “Restart All Services” of WAMP and access your machine in LAN or WAN.

After Check the server error throughs

You don't have permission to access / on this server.

Open the phpmyadmin configuration file.


<Directory "c:/wamp/apps/phpmyadmin3.4.5/">
    Options Indexes FollowSymLinks MultiViews
    AllowOverride all
        Order Deny,Allow
        Allow from all
Previously, it was like this:

<Directory "c:/wamp/apps/phpmyadmin3.4.5/"> 
Options Indexes FollowSymLinks MultiViews 
AllowOverride all 
Order Deny,Allow Deny from all 
 Allow from 

Save and restart the wamp services.

Tuesday, July 24, 2012

Ports used by Exchange Server

 What TCP and UDP ports does my Exchange 2000/2003 Server use?

     For purposes of configuring firewalls or for troubleshooting communications issues, it may be useful to know what TCP/UDP ports Exchange 2000 Server and Exchange 2000 Conferencing Server are using. This article is also true for Exchange Server 2003 installations.

Protocol: LDAP
  • Port (TCP/UDP): 389 (TCP)
  • Description: Lightweight Directory Access Protocol (LDAP), used by Active Directory, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory.
Protocol: LDAP/SSL
  • Port (TCP/UDP): 636 (TCP)
  • Description: LDAP over Secure Sockets Layer (SSL). When SSL is enabled, LDAP data that is transmitted and received is encrypted.
  • To enable SSL, you must install a Computer certificate on the domain controller or Exchange Server 5.5 computer.
Protocol: LDAP
  • Port (TCP/UDP): 379 (TCP)
  • Description: The Site Replication Service (SRS) uses TCP port 379.
Protocol: LDAP
  • Port (TCP/UDP): 390 (TCP)
  • Description: While not a standard LDAP port, TCP port 390 is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on a Microsoft Windows 2000 Active Directory domain controller.
Protocol: LDAP
  • Port (TCP/UDP): 3268 (TCP)
  • Description: Global catalog. The Windows 2000 Active Directory global catalog (which is really a domain controller "role") listens on TCP port 3268. When you are troubleshooting issues that may be related to a global catalog, connect to port 3268 in LDP.
Protocol: LDAP/SSL
  • Port (TCP/UDP): 3269 (TCP)
  • Description: Global catalog over SSL. Applications that connect to TCP port 3269 of a global catalog server can transmit and receive SSL encrypted data. To configure a global catalog to support SSL, you must install a Computer certificate on the global catalog.
Protocol: IMAP4
  • Port (TCP/UDP): 143 (TCP)
  • Description: Internet Message Access Protocol version 4, may be used by "standards-based" clients such as Microsoft Outlook Express or Netscape Communicator to access the e-mail server. IMAP4 runs on top of the Microsoft Internet Information Service (IIS) Admin Service (Inetinfo.exe), and enables client access to the Exchange 2000 information store.
Protocol: IMAP4/SSL
  • Port (TCP/UDP): 993 (TCP)
  • Description: IMAP4 over SSL uses TCP port 993. Before an Exchange 2000 server supports IMAP4 (or any other protocol) over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: POP3
  • Port (TCP/UDP): 110 (TCP)
  • Description: Post Office Protocol version 3, enables "standards-based" clients such as Outlook Express or Netscape Communicator to access the e-mail server. As with IMAP4, POP3 runs on top of the IIS Admin Service, and enables client access to the Exchange 2000 information store.
Protocol: POP3/SSL
  • Port (TCP/UDP): 995 (TCP)
  • Description: POP3 over SSL. To enable POP3 over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: NNTP
  • Port (TCP/UDP): 119 (TCP)
  • Description: Network News Transport Protocol, sometimes called Usenet protocol, enables "standards-based" client access to public folders in the information store. As with IMAP4 and POP3, NNTP is dependent on the IIS Admin Service.
Protocol: NNTP/SSL
Port (TCP/UDP): 563 (TCP)
Description: NNTP over SSL. To enable NNTP over SSL, you must install a Computer certificate on the Exchange 2000 Server.
Protocol: HTTP
  • Port (TCP/UDP): 80 (TCP)
  • Description: Hyper-Text Transfer Protocol is the protocol used primarily by Microsoft Outlook Web Access (OWA), but also enables some administrative actions in Exchange System Manager. HTTP is implemented through the World Wide Web Publishing Service (W3Svc), and runs on top of the IIS Admin Service.
Protocol: HTTP/SSL
  • Port (TCP/UDP): 443 (TCP)
  • Description: HTTP over SSL. To enable HTTP over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: SMTP
  • Port (TCP/UDP): 25 (TCP)
  • Description: Simple Mail Transfer Protocol, is the foundation for all e-mail transport in Exchange 2000. The SMTP Service (SMTPSvc) runs on top of the IIS Admin Service. Unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS).
Protocol: SMTP/SSL
  • Port (TCP/UDP): 465 (TCP)
  • Description: SMTP over SSL. TCP port 465 is reserved by common industry practice for secure SMTP communication using the SSL protocol. However, unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS). To enable TLS to work on Exchange 2000, you must install a Computer certificate on the Exchange 2000 server.
Protocol: SMTP/LSA
  • Port (TCP/UDP): 691 (TCP)
  • Description: The Microsoft Exchange Routing Engine (also known as RESvc) listens for routing link state information on TCP port 691. Exchange 2000 uses routing link state information to route messages and the routing table is constantly updated. The Link State Algorithm (LSA) propagates outing status information between Exchange 2000 servers. This algorithm is based on the Open Shortest Path First (OSPF) protocol from networking technology, and transfers link state information between routing groups by using the X-LSA-2 command verb over SMTP and by using a Transmission Control Protocol (TCP) connection to port 691 in a routing group.

Protocol: RVP
  • Port (TCP/UDP): 80 (TCP)
  • Description: RVP is the foundation for Instant Messaging in Exchange 2000. While RVP communication begins with TCP port 80, the server quickly sets up a new connection to the client on an ephemeral TCP port above 1024. Because this port is not known in advance, issues exist when you enable Instant Messaging through a firewall.
Protocol: IRC/IRCX
  • Port (TCP/UDP): 6667 (TCP)
  • Description: Internet Relay Chat (IRC) is the chat protocol. IRCX is the extended version offered by Microsoft. While TCP port 6667 is the most common port for IRC, TCP port 7000 is also very frequently used.
Protocol: IRC/SSL
  • Port (TCP/UDP): 994 (TCP)
  • Description: IRC (or Chat) over SSL. IRC or IRCX over SSL is not supported in Exchange 2000.
Protocol: X.400
  • Port (TCP/UDP): 102 (TCP)
  • Description: ITU-T Recommendation X.400 is really a series of recommendations for what an electronic message handling system (MHS) should look like. TCP port 102 is defined in IETF RFC-1006, which describes OSI communications over a TCP/IP network. In brief, TCP port 102 is the port that the Exchange message transfer agent (MTA) uses to communicate with other X.400-capable MTAs.
Protocol: MS-RPC
  • Port (TCP/UDP): 135 (TCP)
  • Description: Microsoft Remote Procedure Call is a Microsoft implementation of remote procedure calls (RPCs). TCP port 135 is actually only the RPC Locator Service, which is like the registrar for all RPC-enabled services that run on a particular server. In Exchange 2000, the Routing Group Connector uses RPC instead of SMTP when the target bridgehead server is running Exchange 5.5. Also, some administrative operations require RPC. To configure a firewall to enable RPC traffic, many more ports than just 135 must be enabled.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
148732 XADM: Setting TCP/IP Port Numbers for Internet Firewalls
161931 XCON: Configuring MTA TCP/IP Port # for X.400 and RPC Listens

Protocol: T.120
  • Port (TCP/UDP): 1503 (TCP)
  • Description: ITU-T Recommendation T.120 is a series of recommendations that define data conferencing. Data conferencing is implemented on the server side as a Conferencing Technology Provider (CTP) in the Multipoint Control Unit (MCU), which is one component of the Exchange Conferencing Services (ECS). Data conferencing is implemented on the client side as Chat, Application Sharing, Whiteboard, and File Transferring in Microsoft NetMeeting.
Protocol: ULS
  • Port (TCP/UDP): 522 (TCP)
  • Description: User Locator Service is a type of Internet directory service for conferencing clients, such as NetMeeting. Exchange 2000 Server and Exchange 2000 Conferencing Server do not implement a ULS, but rather take advantage of Active Directory for directory services (by TCP port 389).
Protocol: H.323 (Video)
  • Port (TCP/UDP): 1720 (TCP)
  • Description: ITU-T Recommendation H.323 defines multimedia conferencing. TCP port 1720 is the H.323 (video) call setup port. After a client connects, the H.323 server negotiates a new, dynamic UDP port to be used for streaming data.
Protocol: Audio
  • Port (TCP/UDP): 1731 (TCP)
  • Description: Audio conferencing is enabled in much the same way as H.323 video conferencing is enabled in Exchange 2000 Server. After clients connect to TCP port 1731, a new dynamic port is negotiated for further streaming data.
Protocol: DNS
  • Port (TCP/UDP): 53 (TCP)
  • Description: Domain Name System (DNS) is at the heart of all of the services and functions of Windows 2000 Active Directory and Exchange 2000 Server. You cannot underestimate the impact that a DNS issue can have on the system. Therefore, when service issues arise, it is always good to verify proper name resolution.

Configure Exchange E-Mail Server Reverse DNS and MX Records Correctly

If DNS is setup incorrectly, over time your mail server IP will be added to blacklists. Nowadays most E-Mail servers have some kind of spam protection service which in turn means that all your inbound mail will be blocked if you do happen to be listed on a spam blacklist.
In this article I will describe how to correctly configure your MX and reverse DNS records for your mail server. This article is based on an Exchange 2003/2007 server but every other messaging server will follow the same principle.

Assigning an IP address

Starting from the bottom up the first thing you need to do is assign a static external IP address to the internal private address of your mail server. You will need to apply these rules on your firewall to port forward SMTP (port 25) and NAT an external IP address to the internal address of the server.
Something that a lot of administrators forget to do or check is to set the outgoing NAT rule to use the same external IP address created for the inbound rule to the mail server. If this isn't set, Reverse DNS will not match and in turn your mail server will be listed on blacklists. If your firewall rules are setup correctly the IP address listed on this page should be the same IP address you mapped to the internal private IP address of the mail server.

Create the MX records for your mail server

For the purpose of this example, listed below are all the details of my mail server to help you understand what you need to do.

External IP: 120.12.453.22(for example)

E-Mail Domain:

You will need to be an administrative contact for your External DNS provider for your domain to make these changes. In most cases this can be done through an online control panel through your DNS provider. Failing that on the phone or via E-Mail.

1. The first thing we need to do is create an A record to point to the external IP address mapped on your firewall to the mail server. The host A record can be called any thing but is commonly called "mail". In our example we will create "" to point to IP address "120.12.453.22"

2. Next we will create an MX record to point to the newly created A record of our mail server.
Within your DNS control panel select "add MX record". Make sure that the host address is the root domain name in our case ""

Set the FQDN as the A record we just created which in our case is "".
The lowest property is the most preferred but in our example we will set the priority as 10.

Use NSlookup to check DNS and MX records are applied

It can take up to 48 hours for DNS to propagate but in most cases 12-24 hours. To check our DNS entries are applied and correct we can use nslookup.

1. Open a CMD prompt and type nslookup
2. Type set type=mx
3. Type the domain name which in our case is
In our example the output should read as follows if correctly setup:
Non-authoritative answer: MX preference = 10, mail exchanger = internet address = 120.12.453.22

Configure Reverse DNS 

Reverse DNS is used to verify that the mail server is who it says it is. The recipients mail server will do a reverse lookup to make sure that the IP address of the mail A or host record in DNS is the same as the IP address it is communicating with. Only 1 RDNS entry can be present per IP address.
To do this you will need to contact your ISP to make this entry. You will not be able to do this in your DNS control panel unless your ISP also host your DNS and give you the functionality to add your own RDNS records.

In our case we would contact our ISP and advise that we would like to create an RDNS entry for our IP address 120.12.453.22 which would resolve too

Verify Reverse DNS

Again it can take up to 48 hours for DNS to propagate but in most cases 12-24 hours. To verify that the RDNS entries have been added and are correct do the following:

1. Open a CMD prompt.
2. Type Ping -a 120.12.453.22 (This is the external IP address for your mail server. In our case we use our external IP address stated above)
If RDNS is configured correctly the following output will be shown:
C:UsersUser>ping -a 120.12.453.22
Pinging [120.12.453.22] with 32 bytes of data:

SMTP Banner

Every time a mail server establishes a connection with your mail server it shows its SMTP banner. This banner must be resolvable on the internet and best practice is to have it as your mail host/A record.

Configure SMTP banner Exchange 2003

1. Open Exchange system manager.
2. Expand your administrative group ("First administrative group" by default).
3. Expand Servers.
4. Expand YourServerName.
5. Expand Protocals container.
6. Select SMTP container.
7. On the right window, right click the Default SMTP virtual Server (Or the name you set your SMTP Server) and
select Properties.
8. Select the Delivery Tab.
9. Click the Advanced button.
10. Under the Fully-qualified domain name type (The A/Host record you created in DNS for your mail server)
11. Click OK and OK again to accept the changes

Configure SMTP banner Exchange 2007/2010

1. Open the Exchange management console.
2. Select the Organisation Configuration container.
3. Select Hub Transport container.
4. On the right select the Send Connectors tab.
5. Right click your send connector and select properties.
6. On the General tab under the Set the FQDN this connector will... type the A record domain name you created. Which in our case is Click OK.
7. Under the Server Configuration container click the Hub Transport container.
8. In the Right window Select the properties of the Receive Connector under Receive Connectors tab.
9. On the General tab under the Set the FQDN this connector will... type the A record domain name you created. Which in our case is Click OK
To verify these changes we can use telnet to view the output upon establishing a connection on port 25 to our mail server. Use the following steps to do this:
1. Open a CMD prompt
2. Type Telnet 25.
The output you see should look something like this and contain your A record of your mail server:
appliance like a Barracuda the SMTP banner will have to be set on this device/server.
Check to see if your mail server is on spam lists and/or an open relay

Wednesday, July 18, 2012

Mac mail

How to set up your Email with Mac Mail

If you use a Macintosh computer, then you might use the built-in Mail program (also known as Mac Mail) to check your email.  You can also configure Mac Mail to check your email from your hosting with us so that you do not need to learn to use a new email client.  Follow the steps below to set up Mac Mail on your computer to retrieve your email from Web Hosting Hub.
Step 1: First, open up your Mac Mail on your computer, and you will get a screen like the one below.  Fill out the requested information and click Continue.  For the password field, make sure that you use the password for your email address and not the password for your cPanel.
Step 2: In this next screen you will tell Mac Mail how to get your email from our server.
Incoming Mail Server
Account Type Select either POP or IMAP.
Description Enter in anything you want, such as "Bob's Email" for example.
Incoming Mail Server The server name will be
User Name Put in your full email address (not your cPanel username).
Password The password for the email account you are setting up.

Step 3: This screen asks for the same information as the last screen so you will use the same mail server with the same User Name and Password.  Also, check the boxes that say Use Authentication and Use only this server.
Step 4: Once you have filled in the information, the final page will confirm the settings that you just selected.  Click the box for Take account online if it isn't already checked.  If the information is correct hit Create and you will be able to access your email through Mac Mail.

550 Access denied - Invalid HELO name

Our Systems Team has begun implementing the requirement of SMTP authentication on our servers that may affect customers using an email client such as Thunderbird, Outlook or Mac Mail. If you are receiving "550 Access denied - Invalid HELO name" (or a similar error message) in your email client, please check your settings as follows:

Microsoft Outlook

  1. From the Menu Bar, Click Tools then Click E-mail Accounts
  2. Select "View or change existing e-mail accounts" then Click "Next"
  3. Select your Email account then Click "Change"
  4. Click "More settings"
  5. Select "Outgoing Server" tab
  6. Select the box beside "My outgoing server (SMTP) requires authentication"
  7. Select "Use same settings as my incoming email server"
  8. Click "Ok"
  9. Click "Next"
  10. Click "Finish"



  1. From the Menu Bar, Click Tools, then Account Settings
  2. This will bring up the Account Settings window where you can click on Outgoing Server (SMTP) at the bottom of the list in on the left side of the window.
  3. Back in the middle of the window, select the appropriate outgoing server and click the "Edit" button.
  4. Make sure "Authentication method" is set to "Normal password"
  5. Click OK to close the SMTP edit window and again on the Account Settings window.


Mac Mail

  1. From within Mac Mail Click Mail, Preferences, then Accounts
  2. Near the bottom of the window, look for Outgoing Mail Server (SMTP), click the drop down arrow and select "Edit SMTP Server List..."
  3. Click the Advanced button in the middle of the window and make sure Authentication is set to "Password."
  4. Click OK to close the edit window

Wednesday, July 4, 2012

System Administrator

What is system administrator ?

           A system administrator, IT systems administrator, systems administrator is a person employed to maintain and operate a computer system and/or network.

        The duties of a system administrator are wide-ranging, and vary widely from one organization to another. Sysadmins are usually charged with installing, supporting and maintaining servers or other computer systems, and planning for and responding to service outages and other problems. Other duties may include scripting or light programming, project management for systems-related projects, supervising or training computer operators, and being the consultant for computer problems beyond the knowledge of technical support staff. To perform his or her job well, a system administrator must demonstrate a blend of technical skills and responsibility.

System Administrator Fields

  • A database administrator (DBA) maintains a database system, and is responsible for the integrity of the data and the efficiency and performance of the system.
  • A network administrator maintains network infrastructure such as switches and routers, and diagnoses problems with these or with the behavior of network-attached computers.
  • A security administrator is a specialist in computer and network security, including the administration of security devices such as firewalls, as well as consulting on general security measures.
  • A web administrator maintains web server services (such as Apache or IIS) that allow for internal or external access to web sites. Tasks include managing multiple sites, administering security, and configuring necessary components and software. Responsibilities may also include software change management.
  • Technical support staff respond to individual users' difficulties with computer systems, provide instructions and sometimes training, and diagnose and solve common problems.
  • A computer operator performs routine maintenance and upkeep, such as changing backup tapes or replacing failed drives in a RAID. Such tasks usually require physical presence in the room with the computer; and while less skilled than sysadmin tasks require a similar level of trust, since the operator has access to possibly sensitive data.
  • A postmaster is the administrator of a mail server.
Duties of a system administrator

A system administrator's responsibilities might include:
  • Analyzing system logs and identifying potential issues with computer systems.
  • Introducing and integrating new technologies into existing data center environments.
  • Performing routine audits of systems and software.
  • Performing backups.
  • Applying operating system updates, patches, and configuration changes.
  • Installing and configuring new hardware and software.
  • Adding, removing, or updating user account information, resetting passwords, etc.
  • Answering technical queries and dealing with often frustrated users.
  • Responsibility for security.
  • Responsibility for documenting the configuration of the system.
  • Troubleshooting any reported problems.
  • System performance tuning.
  • Ensuring that the network infrastructure is up and running.
In smaller organizations, the system administrator can also perform any number of duties elsewhere associated with other fields:

System Administrator privileges

The term "system administrator" may also be used to describe a security privilege which is assigned to a user or users of a specific computer, server, network or other IT System.

The Administrator level of system access permits that user to gain access to, and perform high level configuration features of the system.

This user privilege level is more commonly referred to within a computer or IT system as "administrator" (without the epithet "system"). It may also be called superuser or root.

For example a computer may have a user named "Administrator" or "Root" which has a security level sufficient to install software, or give other users access to the system. Alternatively a user of a system may be assigned to an "Administrators" group, membership of which grants them the same privilege as the Administrator user. These users may be referred to as System Administrators, referring only to the system privilege level, rather than the job function.

For security reasons, the name of an Administrator user or Administrators security group is often changed locally so that it is less easy to guess, in order to reduce system vulnerability to access by hackers.

Find us on Google+