Announcement

Collapse
No announcement yet.

Windows 2003 Server not mapping drives

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows 2003 Server not mapping drives

    I am in a situation where I am running Windows 2003 on a virtual machine (VMWare). The VMs are small and their only purpose in life is to house one of our customer’s VPN clients and a 5250 emulator if necessary. I have a new requirement from 2 of our customers to map a drive on a server in their network. I am able to connect to the customer’s network and can access their AS/400 with the emulator so I know I am in the network. I can ping the server where the shared drive is and I can run a tracert with no problem. Here is the testing and errors I am getting.

    · I am able to load the VPN client on a standalone laptop, connect to the client and map the drive. The profile I sign on to the laptop with is different from the profile the customer assigned to me, as a result when I map I have to provide my credentials at the time I map but I connect with no problems.

    · When I started I would try to map the drive the original error was, “The mapped network drive could not be created because the following error has occurred: The network location cannot be reached…”

    · I read several strings on this web site and found a solution where installing File and printer sharing for MS Networks. I installed it and got the same error, ”The network location cannot be reached…”.

    · I found a Client on the network component, Client services for Netware. The description for this is “A client provides access to computers and files on the network you are connecting to.” I installed it and the error changed to “The drive could not be mapped because no network was found.”
    I know Windows Server 2003, SP 2, should be able to map drives. I am able to install the VPN on my Vista laptop and map to the drives with no problem, so the issue is not on my customers side or the VPN client. Also the credentials I use to sign on to my laptop are different from the ones I sign on to the VPN and map the drive to. When I map the drive I assign the letter, enter the server and provide the needed credentials under “Connect using a different user name.”

    Any suggestions would be fantastic.

    Thanks in advance
    KS

  • #2
    Re: Windows 2003 Server not mapping drives

    Couple of quick thoughts:

    Mapped drives are profile-specific. If you map a drive using your own profile, nobody logging in differently will be able to see it.

    The "network location cannot be reached" error has to do with permissions, not connection. You're trying to map a drive you don't inherently have permission to use.

    Netware is a protocol for use with Novell operating systems; it doesn't do anything for an exclusively Windows environment.

    Your best bet would be to use a script to map the drive. Here's an example of how to do so via WSF.

    <package>
    <job id="vbs">
    <script language = "VBScript">

    On Error Resume Next
    Set WshNetwork = WScript.CreateObject("WScript.Network")

    WshNetwork.MapNetworkDrive "X:", "\\servername\sharename"

    </script>
    </job>
    </package>


    Just replace the drive letter and other names accordingly, copy to Notepad with the extention .wsf and set it to run when the user logs in.

    Comment


    • #3
      Re: Windows 2003 Server not mapping drives

      Originally posted by Bertmax View Post
      Couple of quick thoughts:

      Mapped drives are profile-specific. If you map a drive using your own profile, nobody logging in differently will be able to see it.

      The "network location cannot be reached" error has to do with permissions, not connection. You're trying to map a drive you don't inherently have permission to use.

      Netware is a protocol for use with Novell operating systems; it doesn't do anything for an exclusively Windows environment.

      Your best bet would be to use a script to map the drive. Here's an example of how to do so via WSF.

      <package>
      <job id="vbs">
      <script language = "VBScript">
      On Error Resume Next
      Set WshNetwork = WScript.CreateObject("WScript.Network")

      WshNetwork.MapNetworkDrive

      </script>
      </job>
      </package>

      Just replace the drive letter and other names accordingly, copy to Notepad with the extention .wsf and set it to run when the user logs in.
      Bertmax, thank you for your suggestions. Here is what happened.

      I uninstalled the Client Services for Netware, so now I am back to the “Network cannot be reached” error. I copied your script, changing out the drive letter and the location. I saved it as MapDriveF.wsf. When I try to launch (double click on it) it appears it does not do anything. Unfortunately, I cannot follow the suggestion “set it to run when the user logs in” because I have to start the VPN connection, then map to the drive.

      My question at this point centers around the comment; “You're trying to map a drive you don't inherently have permission to use.” When I follow the procedure to run this on a laptop with Vista, I sign on to the laptop as ProfileA/Password, start the VPN connection, map the drive, click “Connect using a different user name”, enter Domain/ProfileB/Password, click ok, click on Finish and the drive connects. This tells me I have the proper credentials and authority to map the drive.

      When I follow the same steps on the VM with Windows 2003 Server SP2, I sign on to the VM as ProfileA/Password, start the VPN connection, map the drive, click “Connect using a different user name”, enter Domain/ProfileB/Password, click ok, click on Finish and the drive does not connect. At this point I am not understanding why my credentials no longer have the proper authority.

      Again, any comments or thoughts, and suggestions are appreciated.

      KS

      Comment

      Working...
      X