I wonder if your assumptions are correct. They are probably just using gethostbyname() / getaddrinfo() to find the IP and then it's the OS (Windows) that is responsible for the behavior you're seeing.
As I'm sure you know those function are part of socket programming functions of the OS. Based on BSD originally but Microsoft must have added code to deal with netbios, wins and whatever they've been doing since the days of Wfw.
Linux by comparison only deals with name resolution by DNS and manual hosts files. I can't think of anything else right now at least.
No where in here is there proof that anyone, above the support tech at the vendor, has been made aware of anything.
At this point there is nothing but an unsubstantiated claim by @CCWTech the vendor knows what the support tech said. Yes, absolutely, if it is known and not corrected, this would be shit, but no one, in this thread, knows this.
Is this a shit ass vendor with a bad product? Maybe, hell probably even. But I won't take the word of anyone the just comes on here and rants without any proof.
This is working on several machines now. But @romo reports that it is still hit or miss, it's not a reliable or permanent fix, but it more reliable than other attempts. It remains, as MS has stated, somewhat random.
If we look at net use, the table is clear and empty. But if we try to mount the AviMark share from the command line we get a 1219 error telling us that the share is already mounted with other credentials. So waiting for clearance to reboot, looks like the net use table is corrupted.
So we don't have an answer yet, might take a while. But what we found that Active Directory was disconnecting because of a bad manual DNS entry. We've fixed that and are waiting to see if the issue recurs.
Do we assume there was DRM that was failing? lol
I'm not aware of any DRM. Is there something pointing to that that makes you assume that?
No - it was a simple guess as to what the program would want/need DNS for, assuming DNS is reason it was failing.
I assume it needs DNS for AD and it needs AD for SMB and needs SMB for the system files.
I just looked this stuff up - it's Vet software - for some reason I thought it was video editing software.