Mapped Drive Disconnects

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • raredesign
    New Member
    • Aug 2007
    • 4

    Mapped Drive Disconnects

    I have a mapped drive of a Windows Server 2k system that keeps disconnecting after a while. I have already checked/tried the following:

    registry edits of holdon, keepAlive, keepAliveInterv al, autodisconnect, etc....none made a difference.

    Deleted map and turned persistent off, bounced, and then remapped. No resolve.

    Used Ethereal to capture packets, but I did not come up with anything obvious.

    Note that the system that is the file server is also the Domain Controller.

    When the map is disconnected, there are a few things that happen.
    1) net use shows it is disconnected, but windows does not show an X on it, so it looks connected.
    2) When I try to access the share, the system hangs
    3) I eventually get:
    "An error occurred while reconnecting L: to \\[server ip]\share
    Microsoft Windows Network: The local device name is already in use.
    This connect has not been restored."

    This was an error mentioned on microsoft's knowledge base as a conflict from McAfee, but it has to do with a different engine version than I am running, so it should not be a problem.

    4) If I do delete the map and try to add it again without rebooting, I get a message the the name I am attempting to use is the name I used to log on with...so it fails.

    5) Help!
  • sicarie
    Recognized Expert Specialist
    • Nov 2006
    • 4677

    #2
    I Googled your error message and found:

    http://www.smartcomputing.com/techsu...&ErrorID=22012 and
    Sandhills Global’s industry-leading solutions connect buyers and sellers of new and used equipment worldwide.

    Comment

    • raredesign
      New Member
      • Aug 2007
      • 4

      #3
      Originally posted by sicarie
      The problem is that it is not just failed to restore connection, it is saying it is already in use.
      When I receive the error trying to re-establish the connection to [ip]\share, and I just try to access \\[ip] ....then I am prompted to connect via entering credentials. When I enter my username and password, I receive the following:
      "Logon unsuccessful:
      The user name you typed is the same
      as the user name you logged in with.
      that user name has already been
      tried. A domain controller cannot be
      found to verify that user name."

      My internet connect, and everything still works...and I can ping the ip that the share is to.
      Remember, the DC is also the file server.

      Comment

      • raredesign
        New Member
        • Aug 2007
        • 4

        #4
        Originally posted by raredesign
        The problem is that it is not just failed to restore connection, it is saying it is already in use.
        When I receive the error trying to re-establish the connection to [ip]\share, and I just try to access \\[ip] ....then I am prompted to connect via entering credentials. When I enter my username and password, I receive the following:
        "Logon unsuccessful:
        The user name you typed is the same
        as the user name you logged in with.
        that user name has already been
        tried. A domain controller cannot be
        found to verify that user name."

        My internet connect, and everything still works...and I can ping the ip that the share is to.
        Remember, the DC is also the file server.
        Thanks dude...the problem was DNS.

        Comment

        • raredesign
          New Member
          • Aug 2007
          • 4

          #5
          I was wrong...it was not DNS....don't think DNS would do that since I am mapping to an IP.
          I have tried many things...even disabled McAfee Antivirus. wins is not used...

          Comment

          • Bob McKee
            New Member
            • Aug 2007
            • 1

            #6
            I found the information in http://support.microso ft.com/kb/297684 very helpful. Apply KeepCon, AutoDisconnect values to registry and run net config... to the server.

            Originally posted by raredesign
            I have a mapped drive of a Windows Server 2k system that keeps disconnecting after a while. I have already checked/tried the following:

            registry edits of holdon, keepAlive, keepAliveInterv al, autodisconnect, etc....none made a difference.

            Deleted map and turned persistent off, bounced, and then remapped. No resolve.

            Used Ethereal to capture packets, but I did not come up with anything obvious.

            Note that the system that is the file server is also the Domain Controller.

            When the map is disconnected, there are a few things that happen.
            1) net use shows it is disconnected, but windows does not show an X on it, so it looks connected.
            2) When I try to access the share, the system hangs
            3) I eventually get:
            "An error occurred while reconnecting L: to \\[server ip]\share
            Microsoft Windows Network: The local device name is already in use.
            This connect has not been restored."

            This was an error mentioned on microsoft's knowledge base as a conflict from McAfee, but it has to do with a different engine version than I am running, so it should not be a problem.

            4) If I do delete the map and try to add it again without rebooting, I get a message the the name I am attempting to use is the name I used to log on with...so it fails.

            5) Help!

            Comment

            Working...