Why can I NOT connect to a SQL Server using an alias from my application server, but am able to use the alias when logged into the actual SQL Server ?

  • I created an alias (32 and 64 bit) for a named instance (Server1\Instance1) and named it Larry on Server 1.
    When I open up SSMS on Server1, and connect via name 'Larry'...I connect fine.
    I now want to connect from an application server (that does not have SQL Server on it) via an application configuration page that asks me the server name. When I put the name "Larry" in, its not able to find it on the network. Of course I cannot ping 'Larry' from the app server as well. The reason I don't use Server1\Instance1 on the application server for configuration, is because the application does not like named instances for configuration, so I thought I would get around this problem by creating Larry as an alias.

    How can I make this work ?

    Ive tried a lot of troubleshooting here are some;
    SQL browser is running on Server1
    TCP/IP is enabled, actually all protocols are enabled
    allow remote connections is checked on Server 1
    Firewall is off

    Why can I NOT connect via the alias name from the application server ?

    THANK YOU!

  • My first question is can you connect to Larry from SSMS running on a different system.

  • Yes, I can connect via my laptop, after setting up Larry alias on my laptop. I have configuration manager and SSMS on my laptop.

    But how can I have an app server connect to Larry ?

  • koln - Tuesday, March 6, 2018 2:26 PM

    I created an alias (32 and 64 bit) for a named instance (Server1\Instance1) and named it Larry on Server 1.
    When I open up SSMS on Server1, and connect via name 'Larry'...I connect fine.
    I now want to connect from an application server (that does not have SQL Server on it) via an application configuration page that asks me the server name. When I put the name "Larry" in, its not able to find it on the network. Of course I cannot ping 'Larry' from the app server as well. The reason I don't use Server1\Instance1 on the application server for configuration, is because the application does not like named instances for configuration, so I thought I would get around this problem by creating Larry as an alias.

    How can I make this work ?

    Ive tried a lot of troubleshooting here are some;
    SQL browser is running on Server1
    TCP/IP is enabled, actually all protocols are enabled
    allow remote connections is checked on Server 1
    Firewall is off

    Why can I NOT connect via the alias name from the application server ?

    THANK YOU!

    You need to create it on the client - on you laptop, on your app server, etc. You can use CliConfig.exe if the clients don't have Configuration Manager.
    This post walks through the process:
    Create SQL Server Alias – CliConfg.exe

    Sue

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply