Cannot generate SSPI context error, but not if SPN server Name is specified





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I'm facing this error when connecting to a remote SQL Server via VPN.



The issue here is that I'm do able to connect only if the SPN Name is specified on the string connection, ie: "Server SPN = MSSQLSvcMyServer.foo.bar"




  • I've reviewed the infamous KB811889

  • I've run the Kerberos Troubleshooting Tool

  • I've checked DNS resolution names and reverse resolution

  • I've checked SPN server name with setspn -l


What's difference between specify the SPN name or not?










share|improve this question





























    0















    I'm facing this error when connecting to a remote SQL Server via VPN.



    The issue here is that I'm do able to connect only if the SPN Name is specified on the string connection, ie: "Server SPN = MSSQLSvcMyServer.foo.bar"




    • I've reviewed the infamous KB811889

    • I've run the Kerberos Troubleshooting Tool

    • I've checked DNS resolution names and reverse resolution

    • I've checked SPN server name with setspn -l


    What's difference between specify the SPN name or not?










    share|improve this question

























      0












      0








      0








      I'm facing this error when connecting to a remote SQL Server via VPN.



      The issue here is that I'm do able to connect only if the SPN Name is specified on the string connection, ie: "Server SPN = MSSQLSvcMyServer.foo.bar"




      • I've reviewed the infamous KB811889

      • I've run the Kerberos Troubleshooting Tool

      • I've checked DNS resolution names and reverse resolution

      • I've checked SPN server name with setspn -l


      What's difference between specify the SPN name or not?










      share|improve this question














      I'm facing this error when connecting to a remote SQL Server via VPN.



      The issue here is that I'm do able to connect only if the SPN Name is specified on the string connection, ie: "Server SPN = MSSQLSvcMyServer.foo.bar"




      • I've reviewed the infamous KB811889

      • I've run the Kerberos Troubleshooting Tool

      • I've checked DNS resolution names and reverse resolution

      • I've checked SPN server name with setspn -l


      What's difference between specify the SPN name or not?







      sql-server kerberos spn






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 20:59









      RobertoRoberto

      3518




      3518
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Have you checked your SQL Server is really listening on the IPs that you have registered with setspn -l? I remember a case some time ago where the registered name was another and the connection was made with a virtual servername.



          If you have tried all of that and is still not working maybe you should go with SQL Server authentication (if possible) that should avoid this error.






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53452878%2fcannot-generate-sspi-context-error-but-not-if-spn-server-name-is-specified%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Have you checked your SQL Server is really listening on the IPs that you have registered with setspn -l? I remember a case some time ago where the registered name was another and the connection was made with a virtual servername.



            If you have tried all of that and is still not working maybe you should go with SQL Server authentication (if possible) that should avoid this error.






            share|improve this answer




























              0














              Have you checked your SQL Server is really listening on the IPs that you have registered with setspn -l? I remember a case some time ago where the registered name was another and the connection was made with a virtual servername.



              If you have tried all of that and is still not working maybe you should go with SQL Server authentication (if possible) that should avoid this error.






              share|improve this answer


























                0












                0








                0







                Have you checked your SQL Server is really listening on the IPs that you have registered with setspn -l? I remember a case some time ago where the registered name was another and the connection was made with a virtual servername.



                If you have tried all of that and is still not working maybe you should go with SQL Server authentication (if possible) that should avoid this error.






                share|improve this answer













                Have you checked your SQL Server is really listening on the IPs that you have registered with setspn -l? I remember a case some time ago where the registered name was another and the connection was made with a virtual servername.



                If you have tried all of that and is still not working maybe you should go with SQL Server authentication (if possible) that should avoid this error.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 23 '18 at 21:52









                dbamexdbamex

                614




                614
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53452878%2fcannot-generate-sspi-context-error-but-not-if-spn-server-name-is-specified%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    Xamarin.form Move up view when keyboard appear

                    Post-Redirect-Get with Spring WebFlux and Thymeleaf

                    Anylogic : not able to use stopDelay()