The local device name is already in use

From Helpful

This article/section is a stub — probably a pile of half-sorted notes and assertions some of which may well be wrong, and not verified as a whole. Feel free to add or refine.

Windows (XP, 2003, and likely most others) networking may give this for shares under, apparently, a few different conditions, including:

  • There is already a mapping to a specific UNC path (possibly some persistent mapping conflicting with manual maps)
  • The drive letter is already used for a mapping(verify)
  • Network name does not resolve (anymore)
  • Server not reachable (right now/anymore) for reasons such as
    • because of a change in server configuration
    • because firewalls are blocking it

(verify):

  • The server may have forgotten your credentials while your client is trying to reconnect assuming they are still valid. May happen in cases like:
    • you are reconnecting from a different IP(verify)
    • your side disconnected, e.g. because of a network timeout, e.g. because the computer revived from hibernation(verify)



[edit]

See also

Retrieved from "http://helpful.knobs-dials.com/index.php/The_local_device_name_is_already_in_use"