asked on

the drive could not be mapped because no network was found.

I have a client that has a 2003 server and had 2 users that use Remote Desktop. Last night the server was rebooted and when the users logged in, there was a message baloon from the Systray that said not all network drives were connected.

I removed the drives and tried to recreate them and when I try to map the drive, I get the message"the drive could not be mapped because no network was found."

What may have changed to cause this?

NJComputerNetworks

Sounds like a basic networking problem. I don't know what may have caused this all of the sudden. Maybe someone turned off the computer that held the remote shares? Maybe the shares are no longer shared?

I would check to make sure that you can ping the server that holds the share. Also see if you can do this START --> RUN --> \\remoteservername This should bring up a window showing you the available shares on the remote server.

You can also check your event log to see if there are any errors on boot.

-hope some of this helps..

btmtech

ASKER

I am able to sign on to the server using Remote Desktop. I am able to see the shares by typing \\servername in the Run... command and I can even setup shortcuts to the shared resources and edit a file by double clicking on the file.

I cannot, however, map the resources to a letter, which is needed for an application that is referring to the S: drive.

Anything that might cause this?

ASKER CERTIFIED SOLUTION

NJComputerNetworks

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

btmtech

ASKER

After trying net use, I created a login script. After that, I was able to map drives again.

Thanks a million (or at least 500).