Recently on our workstations some of our drives are showing up as “diconnected”. If a user clicks on a drive they can see the contents and now the drive shows up connected in My Computer until the next boot. This not only happens for some Novell network drives, but also on NT drives as well. This is a Novell/AD environment and this issue just cropped up in the past few weeks. In most cases it is not a critical issue because like I said a user only has to click on the drive mapping to connect it and gain access to the share, BUT in some cases we have applications, mainly Access databases, that unfortunately don’t use the unc path in the code and that look for certain drive mappings and do not work unless the user clicks on the drive to connect it first. Any suggestions would be appreciated.