Getting On-Prem data from SQL Server to Microsoft Fabric using Dataflow (gen2)

[Dhruv_Ranpura]

Hi,
I am trying to get the On-prem data from  SQL Server to fabric using data factory-> Dataflows(gen2). Below are the steps which I am following:
1. Hvae installed Gateway with latest version which is working fine.
2. Created one lakehouse.

3. Creating Dataflows(gen2) ->selected Get Data->SQL server database -> connecting with server and database using credentials->selected one table-> chose lakehouse in data destination -> go with Lakehouse(none) option.(attached in snapshot)

4.In choose destination target pane I am selecting the lakehouse which I have created earlier in step 2. 

And when I click on next I am getting error : Something went wrong while retrieving the list of tables.(atached in snapshot).

So why I am getting this error?  It would be great if you guide.

[Element115]

OK so the DF is able to talk to the DB successfully via the GW, otherwise there wouldn't be any data coming through to the first DF.  So it's when it goes back to the GW and to the data destination that something funky happens with the TLS protocol.  In other words, 

DF2--->GW--->LH

which is weird because it doesn't do that for me, and I use the exact same architecture, which in my case got rid of all these weird errors:

on-prem DB--->GW--->DF1 ---> DF2--->GW--->LH

Also, from what I have seen, there is no real tweaking available at the GW UI for TLS.  Only the firewall rules.  Speaking of which, my sysadmin couldn't get this endpoint to respond: *.dfs.fabric.microsoft.com, as if it were misconfigured.  But ETL still works, so not sure how essential it is to have this endpoint in the firewall rules.

I sure wish Microsoft would provide some in detail and specific guidance on this, if only with a detailed and cleared doc write-up, ie more than just what can be found here:  On-premises data gateway considerations for data destinations in Dataflow Gen2 - Microsoft Fabric | ...  I mean, we are in the weeds here, and if this product is meant for BI or data people but NOT network engineers, well then... we got a problem now, don't we?