>Thank you Ed again.
>The affected NT Server regained its name yesterday night,when probably the suspicious machine's owner turned the machine off, I guess the assumption two machine share the same NetBIOS Name would be right.(Maybe he must have found the error message as soon as turn on his PC this morning.)
>
>Anyway our entriprise Network(NT) speread all over the country including four major site as hundreds Kilometers as away . I want to pick up the trouble-making PC by all means. Is it possible ? (;All employees are strongly recommended to follow the naming convention configuring his NetBIOS NAME. But he probably disobeyed)
>

Short of turning on each system and checking which one gets an error message, or checking to see how WINS resolved the name before the server retook it, not that I can think of. If you have a unified WINS server, it should be able to log attempts to use a name already assigned to an active station. If you aren't using static IP addresses, it may be tough to pin down exactly which machine is at fault.

>And regarding your suggestion to use IP address, would you give me an example?
>That is to say ,if the original name is FirstName and Service name is SERVE users would do like this \\FirstName\SERVE to use its resource. I don't know what to do first if the NetBIOS Conflict accur again.

NT and Win2K can resolve a UNC in the form \\IP address\sharename; eg if MyServer has the IP address 10.0.0.1, another NT or Win2K ssytem can address the share \\MyServer\Myshare as \\10.0.0.1\MyShare, however, Win9x systems require a NetBIOS name for the UNC, either as provided by a WINS server, or translated via LMHOSTS. Obviously you need static IP addresses to make this work.