![]() No reboot is required after making these changes. In left pane of Registry Editor window, navigate to following registry key: HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem 3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order - ProviderOrder -ĭefault entries: RDPNP, LanmanWorkstation, web client More information Press + R and type regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here ). Make sure the Network Providers entry has at least the default entries: ![]() Network Providers value for RDP might be missing in the registry. On the client Machine: Start - Run - MSTSC - Options - Local Resource - Make sure Disk Drives is selected.Ĭheck Resultant Set of Policy on the machine: Terminal Services Group Policies, under Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Client/Server data redirection - Don't allow drive redirection: shouldn't be enabled. On the Server: Terminal Services Configuration - Connections - RDP-Tcp - Properties - Client Settings: Under Connections - Connect Client Drives at logon is selected. Most of the time something happens, dont know what, and all of the other folders, including the one for the LOB app appear again. On the Server: Terminal Services Configuration - Connections - RDP-Tcp - Properties - Client Settings: Make sure Drive Mapping option is unchecked under Disable the Following. Sometimes if you just click on one of the other mapped drives and go back to the F: mapped drive all of the folders now appear. There are no events in the Event Viewer pertaining to the failure to redirect drives.To do this, create two script files, and then use one of the workarounds, as appropriate. Other devices and resources may be properly redirected. Currently, you can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device. ![]() Local drives aren't redirected in the RDP Session.Changing the location of the company file without updating the location in the database server manager can also cause this error. You may notice the following symptoms when connecting via Remote Desktop Protocol (RDP) to a Windows Server 2003 or Windows Server 2003 R2 Terminal Server: In most cases, the Quickbooks mapped drive is not visible because the connection between QuickBooks and windows is being blocked by a security software such as windows firewall. This article provides a solution to an issue where local drive redirection isn't working in RDP Session.Īpplies to: Windows Server 2003 Original KB number: 2436104 Symptoms
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |