Troubleshooting inability of clients to locate DC, and
dcdiag returns "An net use or Lsapolicy operation failed
with error 67, the network name cannot be found" on
NETLOGONS,MACHINEACCOUNT, SERVICES, and FRSSYSVOL. Any
ideas?

This is usually caused by a MiRC trojan or other virus that prevents the
sharing of the Administrative shares, IPC$, C$, ADMIN$.
--------------------

>
>Troubleshooting inability of clients to locate DC, and
>dcdiag returns "An net use or Lsapolicy operation failed
>with error 67, the network name cannot be found" on
>NETLOGONS,MACHINEACCOUNT, SERVICES, and FRSSYSVOL. Any
>ideas?
>

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!

Thanks- all the AV stuff is up to date now, but this is a
client I just inherited, so I will go check everything
thoroughly. This has been driving me totally crazy- thanks!
>-----Original Message-----
>This is usually caused by a MiRC trojan or other virus
that prevents the
>sharing of the Administrative shares, IPC$, C$, ADMIN$.
>--------------------
>
>>
>>Troubleshooting inability of clients to locate DC, and
>>dcdiag returns "An net use or Lsapolicy operation failed
>>with error 67, the network name cannot be found" on
>>NETLOGONS,MACHINEACCOUNT, SERVICES, and FRSSYSVOL. Any
>>ideas?
>>
>
>__
>Danny Slye
>Microsoft Support Professional
>MCSE
>
>This posting is provided "AS IS" with no warranties and
confers no rights.
>Please reply to the newsgroup so that others may
benefit. Thanks!
>
>.
>