In the left pane, click My Computer. In the right pane, double-click the network drive icon with the red "X" displayed on it. In the Password field type the password, and then click OK. With this feature users can connect to servers with user names and passwords that are different from those that are used to log on.
The user can store these user names and passwords for later reuse. NET Passport credentials. I am trying to find the FIX for the problem, not a workaround. I stated that I could manually disconnect and reconnect get by the problem. However, we have about 8 mapped drives, and manually remapping those on each boot is not practical. I'll assume that your logon script specifies that when workstations log to map a particular share located on some computer on the network as a network drive.
When workstations log on and the script runs, the share can't be found. Look at your script. Look at DHCP. Depends on how you have DHCP configured. It works both ways. I will check the TTL. The drive mappings completely successfully in the login script, but when looked at through explorer, they register as "Disconnected Network Drive F: " or whatever drive letter should be assigned.
When one of these "Disconnected" drives is selected in explorer, it shows the contents and seems to be fine. The biggest problem is when a few programs attempt to access information on one of these, and immediately fail because it is registered as disconnected.
I have flushed DNS on the server, and all of the workstations in question, and still the same results on reboot. After you install or upgrade to Symantec AntiVirus However, you can still access the contents of the mapped drive. Additionally, when you try to remove the mapped drive in Windows Explorer, you receive the following error message:.
This problem occurs because of an issue in Symantec AntiVirus This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.
Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. I have searched all over the Web for an answer to this question but was unable to find any method to activate the "disconnected" share using scripts or commands.
I did however find a utility that does solve the problem. If you found another solution I would like to here about it. Reply to author.
Report message as abuse. Show original message. Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message. Hello, Probably anyone who read the title already knows what the problem is. Hi Bret, Did you ever find a fix for this problem? Angie, this same topic is also being duscussed in the following thread -- no one has found a solution.
John John - MVP. You might try setting the autodisconnect value to 0xffffffff. Theorectically this should keep the drives connected for approximately 8, years Hi, This worked for me First, you need have a "Shared Folder" on your hard drive.
If you haven't got one already, create a new folder on your hard drive called "Shared", then right-click it and select properties. Click the Sharing tab and tick the "Share this folder" box.
0コメント