Microsoft
For those of you still experiencing this issue, I can assure you the error does not relate to a name conflict within your network, but with netbios, as stated within the error itself.
A workaround that has completely fixed this error for me involved disabling hyper-v services as well as windows sandbox. I found that the error kept pointing back to the virtual network adapters created by said virtualization services, and would occur even with said VM's being inactive and shut down. Since there is no easy way to directly disable the netbios feature on these virtual adapters apart from registry changes (that then revert themselves come restart) this is seemingly the only option for the time being. Disabling netbios outright likely hasn't worked in the past before because of some 'inactive' adapter that was still using it.
It is unknown to me why this occurs, it could be that the host and virtual adapters share some sort of identifiable field used within netbios, but I cannot confirm this, as I know nothing of the service.
Obviously, this isn't a permanent solution, as not being able to use the features that you paid for in an OS kinda stinks, but at least I'm not getting booted off my network at random for an unknown reason.
In conclusion, make sure netbios is disabled on all adapters, even on hidden and ones that aren't in use.
(Tip: You can easily find any hidden adapters as well as any active adapters using netbios by running the 'ipconfig /all' command within the command prompt)
I can't promise this will fix your specific cause of 2505 entries, but hopefully this can at least help a few, best of luck to all.