Content-Type: text/html; charset="us-ascii" Received: from BN0PR16MB4526.namprd16.prod.outlook.com (2603:10b6:408:15c::13) by BL0PR16MB2612.namprd16.prod.outlook.com with HTTPS; Tue, 7 Dec 2021 16:57:41 +0000 Received: from BN0PR16MB4397.namprd16.prod.outlook.com (2603:10b6:408:150::18) by BN0PR16MB4526.namprd16.prod.outlook.com (2603:10b6:408:15c::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4713.24; Tue, 7 Dec 2021 16:57:41 +0000 Received: from BN0PR16MB4397.namprd16.prod.outlook.com ([fe80::9c45:eb84:fdd4:e8f]) by BN0PR16MB4397.namprd16.prod.outlook.com ([fe80::9c45:eb84:fdd4:e8f%8]) with mapi id 15.20.4778.012; Tue, 7 Dec 2021 16:57:41 +0000 From: Rickie George To: Microix Support Subject: How to check DMZ server connection with internal SQL Server Thread-Topic: How to check DMZ server connection with internal SQL Server Thread-Index: Adfri4sR0NX7EuwER7uN03ETHMHMxg== Date: Tue, 7 Dec 2021 11:57:41 -0500 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 04 X-MS-Exchange-Organization-AuthSource: BN0PR16MB4397.namprd16.prod.outlook.com X-MS-Has-Attach: yes X-MS-Exchange-Organization-Network-Message-Id: f83e43d6-7c41-4870-bcfb-08d9b9a2ae83 X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 x-ms-publictraffictype: Email authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=microix.net; x-ms-office365-filtering-correlation-id: f83e43d6-7c41-4870-bcfb-08d9b9a2ae83 x-ms-traffictypediagnostic: BN0PR16MB4526:EE_ x-ms-oob-tlc-oobclassifiers: OLM:7219; x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:-1;SRV:;IPV:NLI;SFV:SKI;H:BN0PR16MB4397.namprd16.prod.outlook.com;PTR:;CAT:NONE;SFS:;DIR:INB; x-microsoft-antispam: BCL:0; x-ms-exchange-crosstenant-network-message-id: f83e43d6-7c41-4870-bcfb-08d9b9a2ae83 x-ms-exchange-crosstenant-originalarrivaltime: 07 Dec 2021 16:57:41.1463 (UTC) x-ms-exchange-crosstenant-fromentityheader: Hosted x-ms-exchange-crosstenant-id: 047ca1d7-5314-4422-8db2-9017a42a0ba4 x-ms-exchange-crosstenant-mailboxtype: HOSTED x-ms-exchange-crosstenant-userprincipalname: 8+Bxw04eUeLmsrYPw6XucNjV7A6qbS5LA1n55E1tBPlTOZVllDLlE+HnCQ9IB+OKqvtnZj5iS6N03hPJvrSeBQ== x-ms-exchange-transport-crosstenantheadersstamped: BN0PR16MB4526 x-ms-exchange-crosstenant-authsource: BN0PR16MB4397.namprd16.prod.outlook.com x-ms-exchange-crosstenant-authas: Internal x-ms-exchange-transport-endtoendlatency: 00:00:00.8057270 x-ms-exchange-processed-by-bccfoldering: 15.20.4755.022 X-Microsoft-Antispam-Mailbox-Delivery: ucf:0;jmr:0;auth:0;dest:I;ENG:(910001)(944506458)(944626604)(920097)(425001)(930097); X-Microsoft-Antispam-Message-Info: Q0a1Zx78JktZJrk7YqVpZ45N0VvfHWouKkidQn4sxcewkB4xYd8g4ex8N944hAipozyHfk44121RsYkRRAvJDQQ1t6CHpPH6JAmsYhUcuwQ8MrHP5+yIYBAuVf98hHbAjVuSG5bWhnV61ldJikF0IXzwxUcD0P72chJcHzAt91JQdlwkAZfTDMoMblIwidZzZMVWSbAg1KlB824KjrShKxopi89o5lObu2wlrLZ9o64AIptF57nkpi3DDaEAlkJ4itHvngbeMJYRKl+DoMQIXcnLiLbCNUpvwn1UuKqxcfet8pEc0Otxry2k4vDrL1bGJ+koTBbemn43BTTd0ZyPWfPA7BMKCpFmnLXd9ovPME1OAhyBAQl+LgvTq93t4wzpsuvYLn/kWGPkmHgqsSd4mMmhpxo0+nEd2ppwv9YT60JubR48uK8jllkmSM+UgXCjc81vIHP3wyznoNJTucNC/Hj+Fovfc6X4qt+KhZckfrnuy/P1IflbRyfRw1usTnr6xZc2NhsIBUuVqMwTvmSvjHIBnfa+NSD+709Ne74uVNte1picI9S1N2UbGmkFEtTguYk0b6FnW4tPilB2Epd9jS/7Wd4qgGdDunSdUe2u/4QzkexXKWtK2y3xjdh5Q71LuydH6Y6C2B6FY2+3EHeYQ3sT+HAJLM7xTOaF85G1OfTwJIQ14m0yaWdt69NJhiC+zJjG3RbUQgNKKw3tslalZ33jIPIf62xS8P3o8r8riJNrNdLyJ0HfQ56rYvySj/BK MIME-Version: 1.0

Deploying Microix Cloud Companion and HTML applications on a DMZ server requires the DMZ server to have access to the internal SQL Server via the standard SQL port 1433.  Use the following setups below to confirm the DMZ server has access to the  SQL server. If any of the steps fail, most likely your firewall access from DMZ to the internal SQL server remains and issue and may need to seek assistance from your firewall vendor.

 

Additional Resources: Configure Windows Firewall - SQL Server | Microsoft Docs

 

 

  1. Navigate to Control Panel>Administrator Tools>ODBC Data Source

 

 

 

 

  1. Click the ADD button and select  SQL Server

 

 

 

  1. Select your SQL Server Name form the list or enter the IP address and instance name if applicable

 

 

 

  1. Enter SQL server SA account information

 

 

  1. If connection was successful, a list of databases will be displayed when clicking on the database list