|
|
 |
|
|
Pages: 1
Network and physical drive conflict on MS systems
(Click here to view the original thread with full colors/images)
Posted by: miha
Ok here's the problem:
A accounting company we manage has two network servers and about 30 clients on their network. All users log into a domain and mostly have roaming profiles. Now this is where the problem shows up. When a user logs in there is a login script that sets up the network drives and some other things. Most of the client computers have c drive(harddrive), d drive(CDROM), e drive(network drive), h drive(also network) and some other network drives. But the problem that they still use a very old reliable DOS software for accounting that was originally setup on one of their first computers and ran on the drive E. The software works fine if it is on a network drive E or on a physical drive E but if you change the drive letter or move it to another drive it stopes working. So the only way to get it working on the network was to set up a network drive E and it works perfectly for multiple clients on the network. Now the software has no setting to change the drive letter where it runs and I even used a hex editor to find if it contains any record of drive E. The software was custom made for the company and there is now source code and no support anymore and changing the software is a big no no. Anyway when people plug in their USB drives the workstations install them and give them the drive letter E same as the network dive E. So people have to manually change the drive letter to something else every time they plug in any USB devices. The problem is that some people don't have trouble fixing this but other just keep calling us for help all the time. Now first there is the security problem of giving users the permission to change the system setting so that they can fix this problem but can also do a lot of damage to the system.
So does anyone know of any ways how to fix this problem. I've been googleing for months now with no luck and even contacted MS and was told that they are aware of the problem and are addressing it. But this problem exists since Win98 and is still present on Win2k3 server edition.
Any ideas?
Thanks for your help
Posted by: teraside
Take a look at this, it says it's for WinXp, but maybe you can use it for w2k3 server
The site where I found it:
http://www.tek-tips.com/viewthread....=1224902&page=1
The link to the program:
http://www.uwe-sieber.de/usbdlm_e.html
|
|
|
|
|
