Windows Forum

Ask something
Discussion Locked

Mapping to a network drive

0 helpful
2 replies

by lbarker

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have two Compaq iPaq?s that are running Windows 2000 Pro, w/W2k SP1. Our networks are NT 4.0. I have no problems connecting to the network or domain. I can?t manage to get the ?U? drive properly mapped. Under ?My Computer? or through Windows Explorer the ?U? drive is mapped as ?Network Drive (U)?, but is unaccessible (red ?X?ed). The U drive is normally mapped via our logon script.
When I go to access the Mapped U drive, I get: ?U:\ is not accessible. The filename, directory name or volume label syntax is incorrect?. I tried to modify the label "Network Drive" via the U:\ | PROPERTIES, but it made no difference.
I?m a local/network administrator. I am logged onto the domain, and I can see and access other mapped drives.
When I attempt to disconnect the drive, I get: ?The network connection could not be found.?
When I go through the TOOLS tab, and attempt to ?MAP NETWORK DRIVE?, the U:\ drive doesn?t appear as an available drive and it doesn?t register as being mapped either!
And, when I again go through the TOOLS tab, and attempt to ?DISCONNECT NETWORK DRIVE?, the drive again doesn?t appear.
I have to deleted the mapped ?U:\? by using the command prompt SUBST U: /d command. But when I reboot and log in again, the logon script (that applies to all users) re-maps the drive, but it?s still inaccessible.
When I go through CONTROL PANEL | ADMIN. TOOLS | COMP. MGMT | LOGICAL DRIVES | U:\ | PROP?s | SECURITY (tab) I get a message:
?You only have permission to view the current security information on Unavailable (U:)? I have tried to give myself permission's to this drive, but that option is not available to me.
We use the U: drive for the users private folder. I'm looking for a real fix, or suggestions that might lead to a real fix, not just work-arounds. I'm already using shortcuts to get the user access to her files, but I'd prefer to get to the root of the problem.

2 replies

by kdrungilas

I am using W2K and have mapped network drives. Using the SUBST command does not list any of my mapped drives. Have you tried the NET USE /persistant command?

Check out a couple of Microsoft Articles, Q265193 and Q165575. The first states that,"If you create a drive using the subst command, when you open My Computer, the drive is displayed as a disconnected network drive (the icon contains a red "X")." and then states resolution is, "Even though the drive icon contains a red "X", you are still able to access the drive." I have found this to be true several times--even tho my connections to the drive show a red X, I can still connect.

Permissions from a W2K machine to a NT 4 domain are goofy, I'm not surprised that you are gettingpermissions errors...but are you connecting using your admin priviledges or the user's? A separate issue I think from the drive connection.

by lbarker

The Xs are not as big of an issue as not being abl eto get to the U:\ drive. It does not matter if I am logged in as the user or as admin All the other mapped drives coming from the login script work with no problem. Thanks for your input but, I still need more.

This discussion is closed to new replies.