SQL SERVER – Fix : Error 1418 – Microsoft SQL Server – The server network address can not be reached

Error 1418 – Microsoft SQL Server – The server network address cannot be reached or does not exist. Check the network address name and reissue the command

The server network endpoint did not respond because the specified server network address cannot be reached or does not exist.


Step 1) Your system Firewall should not block SQL Server port.

Step 2) Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Network Configuration
Enable TCP/IP protocol. Make sure that SQL SERVER port is by Default 1433.

Just to make sure follow one more step which may or may not be necessary.

Step 3) Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Client Configuration
Enable TCP/IP protocol.

Well, this blog about error 1418 is pretty straight forward. Do let me know if you find it easy to solve this problem. Though this blog post was written to the SQL Server 2005 it is still true and it is applicable to the latest version of SQL Server as well.

If you find any similar errors in your environment, please let me know and I will be happy to write about them on this blog.

Reference: Pinal Dave (https://blog.sqlauthority.com)

, , , ,
Previous Post
SQL SERVER – 64 bit Architecture and White Paper
Next Post

Related Posts

112 Comments. Leave new

  • Working solution.

    1. Start MSSQLSERVER Services with Domain user credentials (instead of Local System Account) on principal database Server and Mirror Database Server.

    Note: To switch from “Local System Account” to Domain User credentials do the following (a).

    a) On Windows (XP or Server): Start -> Control Panel -> Administrative tools -> Services. Then right click on SQL Server (MSSQLSERVER). Then click on properties. And then click on tab “Log On”. And then choose radio button “this account”. Then provide the Domain user name and password.

    If you want repeat (a) for all SQLSERVER related Services.

    2. And then try the mirroring process in MS SQL Server Management Studio.

    • Awesome. Your solution worked for me. I just made sure that all the sql server services of different instances use the same windows login account that I use to log into my computer.

  • Hi Sureshhumar,

    I have same mirroring problem using SQL Server 2008.

    Can you send your document please (error 1418) ?


  • Hi Suresh,

    I have the same problem configuring SQL server 2008 mirrroing, can you send me the document ?



  • thanks regard.

    i want to document

    (how to ms-sql 1418 error solve )

    please a solve document

    help me…


  • I had the same issue and my two servers are on the same domain with no local or physical firewalls in between. Nothing to do with ports in my case. It was simply that I had not used the correct Domain accounts. I also ensured the two accounts used were local admin on both boxes (not sure if this is necessary). Worked fine after that. Im mirroring from a cluster by the way. Lets see how it looks in a week.

  • I’ve tried all this but still got the error 1418
    Check if your sql user has sysadmin rights under login in SQL Management Console. My account was setup with only public rights. It did work once I added sysadmin rights on the domain user running the SQL service. Hope that helps

  • I had the exact same problem. Was already using the same domain account to run SQL Service on both principal and mirror. Already had the firewalls open on both.

    I was able to set partner on mirror with principal as target, but I would get the above mentioned error 1418 when trying to set partner on principal with mirror as target.

    What fixed it for me was adding the SQL service domain account to the local admins group on both the principal and the mirror.


  • Hi Suresh,

    I have the same erro, can you pls send me the document.


  • Hi Suresh,

    I have the same problem configuring SQL server 2008 R2 mirrroing, can you send me the document ?

    Error: “The server network address “TCP://servername:5022″ can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418)”


  • Hi,

    I have also met this issue when I configure the mirroring.

    could you sent the doc to me?

    Thanks in advance!

  • kindly mail me the document
    i have same issue with mirroring on sql 2008 server and my system runs windows 7

  • Seems like some people were able to fix this problem. but, ’till this date nobody was able to post a how to on this page.

    A little how to about 10 lines or so would benefit all feature readers.


  • I’ve read every post in this thread, and it is still failing for me.
    – Put both computers in a domain.
    – Put a domain user in the local admin group of both computers.
    – Booted under that domain user.
    – Run all SQL services under that domain user.
    – Created a SQL user in SSMS of that domain user, and granted sysadmin rights.
    – Attempt to configure mirroring; still get error 1418.

  • I got the same error when I set a mirroring with certificates between two untrusted domain can you please send the those too.

    Thank you

  • HI to all,
    I have configured like,
    -two computers in same domain
    – started all the mssqlserver and agent services(principle and mirror) under same domain account
    created the mssqlserver security logins with sysadmin privs
    followed the backup and steps restore steps properly
    Attempt to configure mirroring; still getting same error 1418.

    Hi suresh,

    Please send database mirror document to my mail id


  • Arash Moradabadi
    September 5, 2011 3:46 pm


    Just take a look at URL below and follow the instruction.

    Sure it works

    JUST REMEMBER TO create the mirror endpoint first

  • Mohamed Mubeeth
    October 10, 2011 9:25 pm

    I have setup everything accordingly but still receiing the error. I have this error with database mirroring. The account I use is an domain admin account with full privileges on each server.

  • I used the default accounts in SQL 2012 install which presumably is the network account. Both computers are in the same domain. I then used the two machine accounts on both computers:


    That resolved the error for me.

  • If your machines are not in a domain, take a look at this it worked just fine for me.

    For this case cenario seems to exist another simpler solution explained here but i did not manage to put it to work using that solution.

    Best regards :)

  • Hi Anyone help me to get solve this issue? 1418 …

    Same domain, full access ( sysadmin) for the domain users who has priv on both servers. fire walls off… END point are set.. still same problem..


Leave a Reply Cancel reply

Exit mobile version