Connecting to SQL Server through a firewall to a virtual server by IP/Port

  • They recently started virtualizing or databases servers here. I have some applications on of web site that live outside the firewall, that I connect to the SQL Server instance via IP Address and Port. This worked fine until we virtualized the box, now I am getting the following error:

    "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)"

    The connect string is in the form:

    "Data Source=##.##.##.###,####;" & _

    "Network Library=DBMSSOCN;Database=MyDatabase;" & _

    "User ID=sa;Password=mypassword;"

    Anybody have any experience doing this? I feel like the issue is with the trying to connect by IP and port to a virtual server, but I don't really have to much knowledge in the area and it's new to the network guys as well.

  • Along with virtual servers come virtual ethernet adapters, virtual switches, virtual ports, etc. If enabled there can be an entirely separate virtual networking structure. Your virtual host may be inaccessible from outside the firewall even though previously the same IP on hardware was accessible.

    Your traditional networking guys need to talk to the virtual server team.

    Your connect string references the sa account, you really should be using an account with the minimal permissions necessary for the application to work.

  • Go to SQL Server Configuration Manager then check all protocol are enabled on the instance side as well as native client side as mention in the figure

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • Turns out I had to remove and recreate my TCP/IP connection in SQL Server in case anybody else runs into this issue. Thanks for the help.

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

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