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

**ps3cheats** · 15-Mar-2007, 02:49 AM

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?

**ps3cheats** · 15-Mar-2007, 02:49 AM

Can you map the drive as a different letter...just as a test? How about running Net Use from a command prompt to see what you mappings are... Does the S: drive already appear?

15-Mar-2007, 02:49 AM	#1 (permalink)
ps3cheats Fixed Error! Posts: 1,497 Join Date: Mar 2007 Rep Power: 3 IM:	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?

15-Mar-2007, 02:49 AM	#2 (permalink)
ps3cheats Fixed Error! Posts: 1,497 Join Date: Mar 2007 Rep Power: 3 IM:	Re: the drive could not be mapped because no network was found. Can you map the drive as a different letter...just as a test? How about running Net Use from a command prompt to see what you mappings are... Does the S: drive already appear?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)