WINS really oughta be put to bed...
... and legacy software that relies on it for name resolution should be dragged out into the street and shot.
The problem is with WINS resolution cache update latency across WANs.
I've run into situations where the following command connects to one machine:
-- C:\>mstsc /v:MYMACHINE
and this command connects to a different machine:
-- C:\>mstsc /v:MYMACHINE.domain.tld
If WINS is enabled in the environment, the first version will use WINS/NetBIOS name resolution, while the second will use DNS. If WINS table updates don't track with DNS, it can cause a lot of "phantom" issues that pop-up, only to "fix themselves" a couple minutes/hours later when WINS resolution table updates finally make it across the WAN to your local site.
Right pain in the arse, it is...