gillis
IS-IT--Management
- Mar 4, 2001
- 196
Hello,
An odd situation developed after my technician brought a PC in for Windows update and for other routine maint. issues. We returned the PC to user and she noticed that the previously mapped network drive N:Accounting is now identified in Explorer as Local Disk(N. It stills points to the correct network location however.
Troubleshooting - since the system login script assigns drive mapping, we "disconnected" all mappings and rebooted but it comes back. Further tests show the problem is on her PC - i.e., it doesn't travel with her login on another PC - and - anyone logging in on that PC gets same result.
We updated 8 other terminals in same way and no other exhibited this anomaly.
Any ideas?
Thanks, JGiles
An odd situation developed after my technician brought a PC in for Windows update and for other routine maint. issues. We returned the PC to user and she noticed that the previously mapped network drive N:Accounting is now identified in Explorer as Local Disk(N. It stills points to the correct network location however.
Troubleshooting - since the system login script assigns drive mapping, we "disconnected" all mappings and rebooted but it comes back. Further tests show the problem is on her PC - i.e., it doesn't travel with her login on another PC - and - anyone logging in on that PC gets same result.
We updated 8 other terminals in same way and no other exhibited this anomaly.
Any ideas?
Thanks, JGiles