Problem loading catalog data from multi node cluster after changing Vnet IP range in AzureDatabricks

[Flask]

We've changed address range for Vnet and subnet that the Azure Databricks workspace(standard sku) was using, after that when we try to access the catalog data, we're getting socket closed error. This error is only with Multi node cluster, for single node it is working fine. Wondering on how to troubleshoot this issue?

[daniel_sahal]

@Flask 
As it states in the documentation

[Flask]

Yes, it is mentioned that we cannot change the Vnet. I've changed the range in the same vnet but not the Vnet. Is there any troubleshooting that I can do to find this issue. The problem is, I don't want to recreate the workspace. It is a worst case scenario for me and want to explore all the possibilities first.