Hey TechMassey
No the VM‘s which lost their network connection in windows explorer have no 169. Ip. E.G. The User works and want to open a file or save one, then it tells him the network connection is not avaiable.
You can Ping all the servers which are marked as disconnected in windows explorer (Only Vmware View Clients have this Problems), there is no Error Message in Vmware.log of the VM or in the windows events.
No Receiving errors on the VDS Switch and so on. I talked to some manufacture of softwares which are also infected and we traced the error – The Software Manufactor said that their is a KeepAlvie Timeout and the server closed the connection
To the Client. Thats why we changed nearly everything New Core Switch / 1G to 10G (to avoid cabeling errors) / New LoadBalancer for View (Citrix Netscaler) / Wireshark on Esxi Host / Switch and so on…. / a lot of money
I have two thoughts:
Time Error (to avoid time error we changed the Time Source to One physical Machine, but that doesn’t help) or DHCP Error
DHCP: I have changed the lease time to 10 Min – i will report you
Yesterday I investigated time for the DHCP Adresses error where we have not much Adresses free.
I made a DHCP Cleanup of the VDI Scope >>> after that i saw some strange Ghost leases with MACS like: 31302e302e39302e31353200 (Hex Code) and the same Lease Expire Time.
I deleted them and until now they came not back (after google research this error is known, i will wireshark the dhcp server for UDP 67/68 and look which device sends this shit…,)
Here a picture:
One Question about Recompose: Do you use „Use Existing Active Directory Accounts“ --- We have Pools with it marked and without (but the errror is on both )
Thx
Best Regard Michael