Drive mapping issue

I have 3 computers on my home network - workstation, media server, and laptop - all in a peer to peer network and all running WinXP.

Recently the main media drive in the server disconnected and i can't get either the workstation or laptop to reconnect. I can still use all the other mapped drives on the server. I've tried remapping, unsharing the drive/sharing/remapping, and changing drive letter.

Any ideas why this one drive will not map?

The only unusual thing about this drive compared to the others is that it is a RAID5 array under the onboard nVidia chipset running through software, if it could be a factor.

Clients don't know, don't care, and are not affected by what type of partition/volume is on the other end.

With that said, don't expect much of a response with such little information given. For instance, you said you couldn't get the nodes to connect. How so? Errors? Events in event viewer? Ping by name? by IP? How are you trying to map? OS? Not just XP. Various versions of XP. Simple file sharing enabled? Etc, etc.......

Put some effort into your questioning/post and you will likely get assistance more quickly.

On the machine not connecting, run "net use * /delete", then reboot. Once it comes back up, try to map the drive again. Also, you might try rebooting the server as well before you re-map the drive.

MorfiusX said:

On the machine not connecting, run "net use * /delete", then reboot. Once it comes back up, try to map the drive again. Also, you might try rebooting the server as well before you re-map the drive.

Click to expand...

Tried this to no avail.

Ok, I see that I was a little thin on info given. Somehow I thought I had posted more. /brainfart

However, I did give the ol' MS KB a try before posting here!

Server = MCE (has shared drives D, M, P, Q, and added T recently)
Workstation = XP Pro (connects to all shared drives except M:, rebuilt entire system recently )
Laptop = Home (connects to all shared drives except M: )

M: is the main media drive and is a RAID 5 array (onboard controller on MSI K8NGM2-FID board), all others are single disks. I did add T: recently, and I can't say for certain if the M: drive issue happened when this was added. I hadn't connected to the M: drive from the workstation or laptop for a few days (and a couple boot-ups each). Server is on 24/7, but others on only when used.

Comcast cable => Linksys WRT54GS => ABS gigabit switch => to pc's (see sig for specs)

For sharing the drives on the Server I right-click on the drive in Explorer, Sharing, click on the "If you understand the risk...", again click on the "If you understand the risk...", "Just Enable File Sharing", check "Share this folder.." and "Allow Network Users..." with Share name of "Media".

For mapping I go into Explorer, Tools, Map Network Drive. Choose a drive letter, for Folder I hit the Browse button and go to My Network Places, Entire network, Microsoft Windows Network, [workgroup name], Server, and I can see all the shared drives including M. So I choose "Media (M)", hit Finish and takes a few seconds of "Attempting to connect to \\Server\Media (M)" and then the error message appears "The mapped network drive could not be created because the following error has occurred: Not enough server storage is available to process this command." Every shared and non-shared drive on all 3 computers has at least 15% free space (all my drives are at least 250gb except the workstation's 150gb Raptor).

Browsing from Explorer over the network to the \\Server\Media (M)\ it goes to the hourglass and times out with the error message "\\Server\Media (M) is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Not enough server storage is available to process this command."

kywebb - I looked in the Event Viewer (I'm not very familiar with this) and the most recent message is this 'Userenv' 1517 event:

Windows saved user WORKSTATION\Administrator registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Click to expand...

This level of networking stuff is over my head.

TMI?