1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Take Command will not release network drive

Discussion in 'Support' started by rawood11, Nov 4, 2008.

  1. rawood11

    Joined:
    Oct 2, 2008
    Messages:
    19
    Likes Received:
    0
    I am using the following commands in a script:

    net use v: /d
    net use v: \\192.168.10.50\issm50_m
    ... commands
    delay 5

    net use v: /d
    net use v: \\192.168.10.30\issm30_m

    The second /d command is refused with a message that the drive is being used by another process. I do not have this problem in 4nt.exe. What am I doing wrong?
     
  2. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,304
    Likes Received:
    39
    Works for me, using one of our servers in place of \\192.168.10.50 and DIR V: as "commands". I'm guessing that the problem is in the part you haven't given us. Changing the current drive to V:, perhaps?
     
  3. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    rawood11 wrote:

    > is being used by another process. I do not have this problem in
    > 4nt.exe. What am I doing wrong?

    Take Command and TCC / 4NT do not (cannot!) have anything to do with the
    behavior of net.exe (which is a Microsoft external app).

    Can you reproduce this with *only* the "net" commands (i.e., removing
    all of the commands referenced by your "... commands"?

    Rex Conn
    JP Software
     

Share This Page