We solved the problem by doing the following:

1) Checked the FilterRunType of the NDIS driver in :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318}\{72891E7B-0A3D-4541-BDCB-3DA62E25B6A8}\Ndi

FilterRunType was set to 1 ---> Changed the value to 2;

2) Checked to see if "DefaultGateway" registry was in HKLM\System\CCS\Services\TCPIP\Parameters\Interfaces\<Our interface>

---> It was missing. So we added a new Multi-String value, called it "DefaultGateway", and added our default gateway (10.32.8.1).

            In case you have multiple interfaces, please do the following:

            Run the following Powershell script:

>>   gwmi Win32_NetworkAdapter | ?{$_.PhysicalAdapter -eq "True" -and $_.NetEnabled -eq $True}

            Note the DeviceID value of the adapter we are interested in;

            Then, go to the following registry value:

            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\<DeviceID>\Linkage

                        Note the GUID under the RootDevice value;

            Then go back to HKLM\System\CCS\Services\TCPIP\Parameters\Interfaces\<GUID> , and add the default gateway as instructed above.

3) Browsed to HKLM\System\CurrentControlSet\Control\network,

----> Deleted the "Config" registry value, after backing up the 'network' key

We rebooted the server: The issue was fixed, we added a static IP, subnet mask, Default GW, and primary and Secondary DNS TCP/IP info in the properties of the adapter, and they stuck.

We rebooted the server and tested several times.

We then made these changes on the other affected servers, and everything is back in order.