A community share accessed by a drive letter task turns into unresponsive regardless of indicating exercise in Home windows Server 2003. This state of affairs suggests a communication breakdown between the consumer machine and the server internet hosting the shared useful resource, though the connection seems to be energetic. As an illustration, a consumer would possibly try to open a file situated on the mapped drive and obtain an error message, but observe community site visitors associated to the drive.
Resolving this subject is vital for enterprise continuity, because it immediately impacts entry to shared sources and information. In a Home windows Server 2003 setting, mapped drives typically function the first methodology for accessing essential recordsdata, functions, and information storage. Troubleshooting this downside prevents productiveness loss and ensures clean operation throughout the community infrastructure. Moreover, understanding this particular downside within the context of Home windows Server 2003 provides worthwhile insights into the challenges of community administration in older working programs, highlighting the evolution of community applied sciences and troubleshooting methodologies.
This text will discover potential causes, together with community connectivity points, server-side issues, client-side configuration errors, and compatibility considerations. It would additionally present sensible troubleshooting steps and options to revive performance and stop future occurrences. Lastly, greatest practices for managing mapped drives in a Home windows Server 2003 setting will probably be mentioned.
1. Community Connectivity
Community connectivity performs a vital function within the performance of mapped drives. When a mapped drive shows as busy however stays unresponsive in a Home windows Server 2003 setting, community connectivity issues typically lie on the core of the problem. Analyzing the varied aspects of community connectivity helps pinpoint the supply of the malfunction.
-
Bodily Layer
The bodily layer encompasses the cabling and {hardware} elements that transmit information between the consumer machine and the server. A defective community cable, a malfunctioning community interface card (NIC), or an issue with the server’s community {hardware} can disrupt communication, resulting in an unresponsive mapped drive. For instance, a broken cable would possibly intermittently transmit information, leading to a drive showing busy however failing to reply constantly.
-
Community Protocols
Community protocols govern how information is transmitted and obtained throughout the community. In Home windows Server 2003 environments, TCP/IP is the first protocol used for community communication. Incorrect TCP/IP configuration on the consumer or server, corresponding to an invalid IP deal with or subnet masks, can impede communication with mapped drives. Equally, issues with DNS decision can stop the consumer from finding the server internet hosting the shared useful resource.
-
Firewall Configuration
Firewalls act as safety obstacles, controlling community site visitors. A restrictive firewall configuration on the consumer, server, or any intervening community gadget can block the mandatory ports and protocols required for accessing mapped drives. For instance, if the firewall blocks port 445, generally used for file sharing in Home windows Server 2003, the mapped drive would possibly seem busy whereas entry stays blocked.
-
Community Congestion
Community congestion happens when community bandwidth is inadequate to deal with the amount of knowledge being transmitted. This could result in delays and dropped packets, impacting the responsiveness of mapped drives. Excessive community utilization as a result of giant file transfers or streaming media can create congestion, making mapped drives seem busy however perform slowly or turn into unresponsive.
Troubleshooting community connectivity requires a scientific strategy, beginning with verifying the bodily layer and progressing by protocol configuration, firewall guidelines, and community load. Resolving community connectivity points typically restores the performance of mapped drives, guaranteeing seamless entry to shared sources in a Home windows Server 2003 setting.
2. Server Efficiency
Server efficiency considerably influences the accessibility of mapped drives. A Home windows Server 2003 system experiencing efficiency bottlenecks can exhibit signs just like community connectivity points, manifesting as unresponsive or gradual mapped drives. Analyzing key efficiency indicators helps decide whether or not server limitations contribute to the issue.
-
CPU Utilization
Excessive CPU utilization on the server can result in delays in processing consumer requests, together with these associated to mapped drives. If the server’s CPU is constantly working close to its most capability, accessing recordsdata or directories on a mapped drive would possibly turn into gradual or unresponsive. As an illustration, a server operating a number of resource-intensive functions would possibly wrestle to deal with further requests from shoppers trying to entry mapped drives.
-
Reminiscence Availability
Inadequate reminiscence (RAM) can drive the server to rely closely on digital reminiscence (paging file), considerably impacting efficiency. Frequent disk entry for paging operations slows down general system responsiveness, together with entry to mapped drives. A server with restricted RAM trying to deal with quite a few concurrent consumer connections would possibly turn into unresponsive when customers entry mapped drives.
-
Disk I/O
Disk I/O efficiency immediately impacts the pace at which recordsdata and directories are accessed on mapped drives. Gradual disk learn/write speeds, typically brought on by fragmented recordsdata, failing onerous drives, or insufficient disk controller efficiency, can result in delays and unresponsiveness. A server with a failing onerous drive internet hosting the shared folder would possibly exhibit gradual or unresponsive mapped drive entry.
-
Community Throughput
Whereas primarily a community concern, community throughput on the server facet also can affect mapped drive efficiency. If the server’s community interface is saturated, or if there are bottlenecks throughout the server’s community stack, shoppers would possibly expertise gradual or unresponsive mapped drives. A server with a 100 Mbps community interface would possibly wrestle to deal with quite a few shoppers concurrently accessing giant recordsdata on mapped drives.
Evaluating these server efficiency features is crucial in diagnosing the foundation reason behind unresponsive mapped drives. Addressing server bottlenecks by {hardware} upgrades, software program optimization, or load balancing can enhance mapped drive accessibility and general system stability in a Home windows Server 2003 setting.
3. Consumer Configuration
Consumer configuration performs a vital function within the correct functioning of mapped drives. Incorrect or outdated client-side settings can result in the “mapped drive is busy however not working” state of affairs in Home windows Server 2003 environments. A number of features of consumer configuration can contribute to this downside, making a disconnect between the consumer machine and the shared useful resource on the server.
One frequent trigger is an incorrectly configured drive mapping. If the drive letter is assigned to an invalid server path or share identify, the consumer might understand the drive as busy whereas trying to ascertain a connection, however in the end fails to entry the useful resource. Equally, cached credentials may cause points if the consumer’s password on the server has modified. The consumer might try to attach with outdated credentials, leading to an obvious connection (and busy standing) with out precise entry. Outdated or corrupt community drivers on the consumer machine also can disrupt communication with the server. Incompatible drivers may cause intermittent connection drops or stop the consumer from accurately deciphering server responses, resulting in the busy but unresponsive state. For instance, an older community driver won’t accurately deal with communication with a server that has undergone current updates.
One other vital issue is the consumer’s community configuration. Incorrect TCP/IP settings, corresponding to an invalid IP deal with, subnet masks, or default gateway, can stop the consumer from reaching the server internet hosting the share. DNS decision issues on the consumer facet also can hinder entry to the server. If the consumer can not resolve the server’s identify to its IP deal with, the mapped drive will seem unresponsive regardless of showing busy as a result of connection makes an attempt. Moreover, native safety software program or firewall settings on the consumer machine would possibly block the mandatory ports or protocols for community file sharing. This could stop entry to the mapped drive even when the server and community connectivity are in any other case functioning accurately. As an illustration, a private firewall would possibly block port 445, stopping entry to shared recordsdata and folders on the server.
Addressing consumer configuration issues requires a scientific evaluate of drive mappings, community settings, driver variations, and safety software program configurations. Making certain correct and up-to-date client-side configurations is essential for sustaining dependable entry to mapped drives in a Home windows Server 2003 setting. Overlooking these features can result in persistent connectivity points, hindering productiveness and information entry.
4. Safety Permissions
Safety permissions play a significant function in controlling entry to shared sources in a Home windows Server 2003 setting. When a mapped drive seems busy however stays unresponsive, inadequate or incorrectly configured safety permissions typically contribute to the issue. Understanding the affect of safety permissions on mapped drive accessibility is essential for efficient troubleshooting.
The “mapped drive is busy however not working” state of affairs can come up when a consumer lacks the mandatory permissions to entry the shared folder or particular recordsdata throughout the folder. Home windows Server 2003 makes use of entry management lists (ACLs) to handle permissions for customers and teams. If a consumer makes an attempt to entry a mapped drive however their account lacks the suitable “Learn” permission, the connection try would possibly seem energetic (busy) whereas entry stays blocked. Moreover, particular permissions, corresponding to “Write” or “Modify,” are required for performing actions past easy file entry, corresponding to saving adjustments or creating new recordsdata. Making an attempt an motion with out the mandatory permissions would possibly lead to an error message or an unresponsive mapped drive showing busy.
For instance, a consumer may be granted “Learn” entry to a shared folder however lack “Write” entry. Making an attempt to save lots of a file to the mapped drive would fail, doubtlessly leading to an unresponsive drive showing busy whereas the system makes an attempt and fails to finish the operation. Equally, share permissions and NTFS permissions work together to find out general entry. A consumer might need applicable share permissions however lack corresponding NTFS permissions, resulting in entry denial regardless of a seemingly energetic connection. Inheritance of permissions additionally performs a job. If a subfolder inside a shared listing has explicitly denied permissions for a selected consumer, that consumer may be unable to entry the subfolder even when they’ve entry to the dad or mum folder.
Analyzing safety permissions includes verifying consumer and group memberships, checking share permissions, and analyzing NTFS permissions on the server. Utilizing the safety tab within the properties of the shared folder and particular person recordsdata permits directors to evaluate and modify permissions. Resolving permission points typically restores performance to unresponsive mapped drives, granting customers the mandatory entry whereas sustaining a safe community setting. This understanding of safety permissions in Home windows Server 2003 is essential for directors troubleshooting mapped drive points and sustaining a safe and environment friendly community infrastructure.
5. Antivirus Software program
Antivirus software program, whereas important for system safety, can inadvertently intervene with community operations, generally manifesting as a “mapped drive is busy however not working” state of affairs in Home windows Server 2003 environments. Actual-time scanning, specifically, can introduce delays or block entry to recordsdata and folders on mapped drives, even when no precise menace exists. Understanding the potential affect of antivirus software program on community shares is vital for troubleshooting and sustaining a balanced safety posture.
-
Actual-time Scanning
Actual-time scanning elements of antivirus software program monitor file entry and modifications, introducing a possible bottleneck. When a consumer accesses a file on a mapped drive, the antivirus software program would possibly quickly lock the file for scanning, inflicting delays or stopping different customers from accessing it concurrently. This could result in the notion of a busy drive, whereas entry stays blocked pending scan completion. For instance, accessing a big file on a mapped drive would possibly set off a prolonged scan, making the drive seem unresponsive to different customers.
-
Community Site visitors Inspection
Some antivirus merchandise examine community site visitors for malicious exercise. This inspection course of can introduce latency and intervene with the graceful circulate of knowledge between the consumer and the server internet hosting the mapped drive. Extreme site visitors inspection would possibly trigger delays in accessing recordsdata or directories, mimicking the signs of a busy however unresponsive drive. In a Home windows Server 2003 setting, this may exacerbate present efficiency limitations.
-
Software program Conflicts
Conflicts between antivirus software program and different functions, together with community drivers or file-sharing companies, can disrupt community operations. Incompatible software program variations or conflicting useful resource utilization can result in instability and intervene with mapped drive entry. As an illustration, an outdated antivirus product would possibly battle with a more moderen community driver, resulting in intermittent connectivity points with mapped drives.
-
False Positives
Antivirus software program can sometimes flag reputable recordsdata or community actions as malicious, resulting in false positives. These false positives may end up in the blocking of entry to recordsdata or folders on mapped drives, even when no precise menace exists. A false optimistic would possibly stop customers from accessing vital recordsdata on a mapped drive, hindering productiveness and inflicting frustration.
Troubleshooting unresponsive mapped drives in a Home windows Server 2003 setting requires consideration of the potential affect of antivirus software program. Briefly disabling real-time scanning or excluding particular community shares from antivirus scans can assist decide whether or not the software program contributes to the problem. Nonetheless, disabling safety features needs to be achieved cautiously and just for diagnostic functions. Finally, configuring antivirus software program to reduce interference with reputable community actions whereas sustaining satisfactory safety is crucial for a steady and productive community setting.
6. File Locking
File locking mechanisms, whereas essential for information integrity in shared environments, can contribute to the “mapped drive is busy however not working” phenomenon in Home windows Server 2003. When a number of customers entry recordsdata on a shared community drive concurrently, file locking prevents information corruption by granting unique entry to 1 consumer at a time. Nonetheless, improper dealing with of file locks or surprising system habits can result in extended lock durations, successfully rendering the mapped drive unresponsive to different customers, even when it seems busy.
-
Unique Locks
Unique locks grant sole entry to a file for modification, stopping different customers from opening or altering the file whereas locked. This mechanism ensures information consistency throughout enhancing however may cause delays if a consumer locks a file for an prolonged interval or if a lock persists as a result of a system error. As an illustration, if a consumer opens a file on a mapped drive and their software crashes with out releasing the lock, different customers trying to entry the identical file will encounter a busy however unresponsive drive.
-
Share Locks
Share locks allow a number of customers to learn a file concurrently however stop any consumer from writing to the file. The sort of lock is much less restrictive than an unique lock however can nonetheless contribute to delays if quite a few customers entry a file concurrently, consuming server sources and doubtlessly making the mapped drive seem busy however gradual to reply. In a Home windows Server 2003 setting with restricted sources, this may be significantly problematic.
-
Opportunistic Locking
Opportunistic locking, frequent in functions like Microsoft Workplace, includes briefly locking a file throughout save operations. Whereas typically environment friendly, opportunistic locking may cause intermittent delays or entry denial if a number of customers try to save lots of adjustments to the identical file concurrently. This could result in a short lived “busy” standing on the mapped drive whereas the system makes an attempt to resolve the lock competition. On older programs like Home windows Server 2003, this may exacerbate efficiency points.
-
Persistent Locks As a result of System Errors
System crashes, software malfunctions, or improper community disconnections can generally depart file locks in place even after the consumer who initially acquired the lock is now not actively utilizing the file. These persistent or “orphaned” locks can block entry for different customers, leading to a mapped drive that seems busy however stays inaccessible. Figuring out and resolving such orphaned locks typically requires administrative intervention on the server.
Understanding the varied aspects of file locking and their potential affect on mapped drive accessibility is vital for efficient troubleshooting in Home windows Server 2003 environments. Investigating lock standing, figuring out locked recordsdata, and resolving persistent locks can restore performance to unresponsive mapped drives and enhance general community efficiency. Failure to deal with file locking points can result in important productiveness losses and information entry disruptions, significantly in shared work environments.
7. Driver Compatibility
Driver compatibility is a vital issue influencing the steadiness and efficiency of mapped drives in Home windows Server 2003 environments. Incompatible or outdated drivers can disrupt communication between the consumer machine and the server, resulting in a “mapped drive is busy however not working” state of affairs. This part explores the vital features of driver compatibility that contribute to this subject.
-
Community Interface Card (NIC) Drivers
The NIC driver facilitates communication between the working system and the bodily community adapter. Outdated or incorrectly put in NIC drivers on the consumer machine can stop correct communication with the server internet hosting the mapped drive. This could manifest as intermittent connectivity points, gradual switch speeds, or the lack to entry the drive altogether, even when it seems busy. For instance, a consumer utilizing an older NIC driver would possibly expertise compatibility points with a server that has obtained current updates, resulting in the “busy however not working” state of affairs.
-
File System Drivers
File system drivers handle information storage and retrieval on the consumer machine. Incompatibilities between the consumer’s file system driver and the server’s file sharing protocol can hinder entry to mapped drives. This could happen if the consumer is utilizing an older model of a file system driver that doesn’t absolutely assist the options or safety mechanisms of the server’s file sharing service. This incompatibility would possibly lead to entry denial or gradual efficiency when accessing recordsdata on the mapped drive.
-
Redirector Drivers
Redirector drivers, often known as community redirector, deal with client-side community communication for file and print sharing. Outdated or corrupt redirector drivers can disrupt the institution and upkeep of connections to mapped drives. A defective redirector would possibly stop the consumer from authenticating with the server or accurately deciphering server responses, resulting in a perceived “busy” state with out precise entry to the shared sources. This subject is especially related in Home windows Server 2003 environments, the place older redirector variations won’t absolutely assist newer community protocols or safety mechanisms.
-
Filter Drivers
Filter drivers intercept and modify community communication, typically for safety or efficiency optimization. Conflicts between filter drivers, corresponding to these put in by firewalls or antivirus software program, can intervene with mapped drive entry. A filter driver would possibly inadvertently block or modify community packets crucial for communication with the server, resulting in an unresponsive mapped drive. Figuring out and resolving such conflicts is essential for restoring correct performance.
Making certain driver compatibility on consumer machines is paramount for sustaining dependable entry to mapped drives in a Home windows Server 2003 setting. Commonly updating drivers to their newest variations, verifying driver compatibility with the server’s working system and file sharing companies, and resolving driver conflicts are important steps in stopping and resolving the “mapped drive is busy however not working” downside. Failure to deal with driver compatibility points can result in persistent connectivity issues, hindering productiveness and information accessibility throughout the community.
8. Server Assets
Server useful resource availability immediately impacts the accessibility and responsiveness of mapped drives in a Home windows Server 2003 setting. Inadequate sources can result in the “mapped drive is busy however not working” state of affairs, the place shoppers understand exercise however can not entry the shared sources. This connection stems from the server’s function in dealing with consumer requests, file operations, and information switch for mapped drives. When server sources are depleted, these operations are hampered, leading to delays, errors, or full unresponsiveness.
A number of key server sources affect mapped drive efficiency. Accessible RAM performs a vital function in caching often accessed information and facilitating clean file operations. When RAM is inadequate, the server resorts to utilizing the onerous drive as digital reminiscence (paging file), considerably slowing down processes. This could result in sluggish response instances or full unresponsiveness when accessing mapped drives, particularly when a number of shoppers entry the server concurrently. Equally, processor utilization impacts the server’s potential to deal with consumer requests and course of file operations. Excessive CPU utilization, typically brought on by resource-intensive functions or extreme consumer load, can bottleneck mapped drive entry, making drives seem busy however perform poorly. Disk I/O efficiency additionally contributes to mapped drive responsiveness. Gradual disk learn/write speeds, doubtlessly brought on by disk fragmentation, failing onerous drives, or insufficient disk controllers, can considerably delay file entry and switch operations, impacting mapped drive efficiency. Community bandwidth on the server facet is one other essential issue. If the server’s community connection is saturated or experiencing bottlenecks, information switch to and from mapped drives turns into gradual or stalls fully. This could create the impression of a busy however non-functional mapped drive.
For instance, a server internet hosting a big shared folder accessed by quite a few shoppers would possibly expertise useful resource exhaustion if its RAM capability is inadequate to deal with the concurrent file entry requests. This might result in in depth paging file utilization, slowing down your complete system and making mapped drives seem busy however unresponsive. Equally, a server operating a resource-intensive database software would possibly expertise excessive CPU utilization, delaying or blocking entry to mapped drives for different shoppers. In such eventualities, upgrading server {hardware}, optimizing server-side functions, or implementing load balancing options can alleviate useful resource constraints and enhance mapped drive accessibility.
Understanding the vital function of server sources in sustaining mapped drive performance is crucial for efficient troubleshooting and administration in a Home windows Server 2003 setting. Monitoring server useful resource utilization, figuring out bottlenecks, and implementing applicable mitigation methods are essential for stopping and resolving the “mapped drive is busy however not working” subject. Ignoring server useful resource limitations can result in persistent efficiency issues, information entry disruptions, and decreased productiveness throughout the community.
Steadily Requested Questions
This part addresses frequent inquiries concerning unresponsive mapped drives in Home windows Server 2003 environments.
Query 1: How can one differentiate between community connectivity issues and server efficiency points when a mapped drive is unresponsive?
Community connectivity points sometimes manifest as full incapability to connect with the server or intermittent connection drops. Server efficiency bottlenecks, then again, would possibly lead to gradual entry, delayed file operations, or intermittent unresponsiveness whereas the connection stays established.
Query 2: What are the frequent client-side misconfigurations that may result in mapped drive entry issues?
Frequent client-side points embody incorrect drive mapping paths, outdated or corrupt community drivers, incorrect TCP/IP settings, and conflicts with native safety software program or firewall configurations.
Query 3: How do safety permissions have an effect on mapped drive accessibility, and the way can permission-related points be resolved?
Inadequate or incorrect NTFS and share permissions can stop entry to mapped drives. Directors can use the safety tab in file/folder properties to evaluate and modify permissions, guaranteeing customers have applicable entry rights.
Query 4: Can antivirus software program intervene with mapped drive entry, and the way can this interference be mitigated?
Actual-time scanning and community site visitors inspection by antivirus software program can delay or block entry to mapped drives. Briefly disabling real-time safety or excluding particular community shares from scans can assist diagnose such interference. Nonetheless, sustained disabling of safety features is discouraged.
Query 5: How do file locks have an effect on mapped drive entry, and what steps will be taken to deal with file locking points?
File locks, whereas crucial for information integrity, can block entry if held for prolonged durations or if orphaned as a result of system errors. Investigating lock standing, figuring out locked recordsdata, and resolving persistent locks can restore entry.
Query 6: What’s the significance of driver compatibility in guaranteeing correct mapped drive perform, and the way can driver-related points be addressed?
Incompatible or outdated NIC drivers, file system drivers, redirector drivers, and filter drivers can disrupt mapped drive communication. Updating drivers to their newest variations and guaranteeing compatibility with the server setting can resolve these points.
Addressing these frequent points typically resolves mapped drive entry issues in Home windows Server 2003 environments. A scientific strategy contemplating community connectivity, server efficiency, consumer configuration, safety permissions, antivirus software program, file locking, and driver compatibility is essential for efficient troubleshooting.
The next part supplies additional steerage on greatest practices and extra sources for managing mapped drives in Home windows Server 2003.
Troubleshooting Ideas for Unresponsive Mapped Drives in Home windows Server 2003
This part provides sensible ideas for resolving the “mapped drive is busy however not working” subject in Home windows Server 2003, specializing in systematic troubleshooting and preventative measures.
Tip 1: Confirm Community Connectivity: Start by checking bodily community connections, guaranteeing cables are securely plugged in and community gadgets are functioning accurately. Use the ping command to check connectivity between the consumer and server. Handle any recognized community points earlier than continuing.
Tip 2: Test Server Efficiency: Monitor server CPU utilization, reminiscence availability, and disk I/O. Excessive useful resource utilization can result in unresponsive mapped drives. Think about upgrading server {hardware} or optimizing operating functions if bottlenecks are recognized.
Tip 3: Evaluation Consumer Configuration: Confirm the accuracy of mapped drive paths and guarantee cached credentials are updated. Replace community drivers to their newest variations and examine native firewall settings for blocked ports.
Tip 4: Look at Safety Permissions: Guarantee customers have applicable NTFS and share permissions to entry the mapped drive. Evaluation and modify permissions by the safety tab in file/folder properties as wanted.
Tip 5: Examine Antivirus Software program: Briefly disable real-time scanning or exclude the mapped drive from scans to find out if antivirus software program is interfering with entry. If conflicts are recognized, take into account adjusting antivirus settings or upgrading to a appropriate model.
Tip 6: Handle File Locking: Establish and resolve file locks that could be stopping entry to the mapped drive. Test for orphaned locks ensuing from system crashes or improper software closures. Think about implementing greatest practices for file dealing with to reduce lock competition.
Tip 7: Guarantee Driver Compatibility: Confirm compatibility of community interface card (NIC) drivers, file system drivers, and redirector drivers on consumer machines. Replace drivers to their newest variations to resolve compatibility points and enhance efficiency.
Tip 8: Optimize Server Assets: Handle server useful resource utilization by closing pointless functions and companies. Think about upgrading server {hardware} or implementing load balancing to distribute the workload and enhance responsiveness.
Following the following tips supplies a structured strategy to troubleshooting unresponsive mapped drives, selling environment friendly downside decision and a steady community setting in Home windows Server 2003.
The following part concludes the dialogue and supplies further sources for additional exploration.
Conclusion
Unresponsive mapped drives current a major problem in Home windows Server 2003 environments, impacting productiveness and information accessibility. This exploration has highlighted the multifaceted nature of this subject, encompassing community connectivity, server efficiency limitations, client-side misconfigurations, safety permissions, antivirus software program interference, file locking conflicts, driver compatibility points, and server useful resource constraints. Every of those components can contribute to the “mapped drive is busy however not working” state of affairs, requiring a scientific strategy to analysis and remediation. Understanding the interaction of those components is essential for efficient troubleshooting.
Directors managing Home windows Server 2003 networks should prioritize proactive measures to mitigate these challenges. Implementing sturdy community monitoring, optimizing server efficiency, guaranteeing consumer configuration consistency, managing safety permissions successfully, configuring antivirus software program thoughtfully, addressing file locking conflicts promptly, sustaining driver compatibility, and balancing server useful resource utilization are important steps towards a steady and productive community setting. Whereas Home windows Server 2003 is now an older working system, understanding these troubleshooting ideas stays related for managing legacy programs and supplies a basis for addressing related challenges in newer environments. Diligence in these areas ensures enterprise continuity and minimizes disruptions associated to mapped drive entry.
