SQL2008R2: Cannot open the required dialog box. Possibly AD/Firewall issue ?

  • Hi, I'm new so apologies if there's a better place to post this but basically my problem is such:


    It's a new lab setup so I'll have probably got a setting or configuration wrong somewhere. It works fine with SSMS locally but if I try and add a new login from a different server I get the above error. The server doing the connecting is 2016 and the server on which the search for login fails is a 2008r2.

    Not sure if it's some kind of firewall or policy or AD issue, as ssms can connect I wouldn't have thought it was the firewall but I'm very new to all this.
    Any help appreciated, James.

  • squaffle - Thursday, March 16, 2017 7:56 AM

    Hi, I'm new so apologies if there's a better place to post this but basically my problem is such:


    It's a new lab setup so I'll have probably got a setting or configuration wrong somewhere. It works fine with SSMS locally but if I try and add a new login from a different server I get the above error. The server doing the connecting is 2016 and the server on which the search for login fails is a 2008r2.

    Not sure if it's some kind of firewall or policy or AD issue, as ssms can connect I wouldn't have thought it was the firewall but I'm very new to all this.
    Any help appreciated, James.

    You should probably go through and check all the DNS configurations for that server. 
    What happens if you try nslookup from the command prompt? Does it display the DNS Server for that server?

    Sue

  • Hey, thanks for the reply.
    Now that you mention it I do get some slightly strange results. The 2008r2 server has two virtual network interfaces, one is connected to the domain with a 33.0.0 address and the other is (at the moment) connected to my router to give internet access for windows updates (192.168 etc).
    When I run nslookup <2008r2ServerName> on the 2008r2 server I get a reply from my isp dns saying unknown, if I disable that second adapter I get a reply from my domain controller with a correct ip address. I suppose that means it's using the second adapter's dns settings by default. .
    Sadly disabling the second adapter on the 2016 server and the 2008 server gives a correct nslookup address but I still get the error within ssms.

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

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