Windows Forum

Ask something
Discussion Locked

Word won't write to network drive.

0 helpful
5 replies

by superbat 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a network of various flavors of Windows (95, 98, NT4.0) all accessing an exported disk on a Unix machine (SGI Indy). All 95/98 use NetManage Interdrive to mount the big disk. All works swell(!) except on some of the 95 boxes, Word 97 (sp2)will not write to the network. It errors out, thinks it lost the connection. If, however, I save to the local drive, I can then copy the document to the network drive outside of word with no problems at all. Avoiding Office 2000, (for oh, so many reasons!!!) I haven't been able to find a reason or a fix for this behavior. I find Word97, in Win 95 has a lot of network problems that no other programs have. These problems don't exist in NT. Am I alone here? Any ideas?

5 replies

by techrepublic

You don't mention how you have your drives mapped however, check them to verify WORD is actually finding the network path to the Drive letter you assigned. I have noticed WORD having fits sometimes when trying to save to a valid network location when a drive mapping does not exist. If you can copy from local to network drives without a problem, then saving from Word to a drive letter should work as well. I hope this is helpful!

by superbat

WOW! That's like saying my car wont start 'cause I didn't put the key in the Ignition. Or, my feet hurt cause I'm walking on broken glass... Anyway, I did say how I mounted (mapped) the drive in the second sentence. Anyway, thanks for trying...

by Member 30576776

I have experienced the same problems with NetManage's InterDrive, particularly with its LPR services. Their tech support acknowledged that they cut corners on the ViewNow 1.0.1 version that we run. NFS and LPR may experience problems on some networks we documented. NetManage promised us a new release this quarter. It is possible that Win98 may avoid these problems because it handles network providers differently: consider upgrading. If you feel lucky, you could let the SGI box provide ftp and use Office's ftp handler. Also, discuss timing and latency with your network engineers to determine if there is a way to reduce network delays that InterDrive is so sensitive to. Your only other option is to see if NetManage will fix the problem or get off of InterDrive entirely. WRQ has a nice product line. Sorry to be long winded, your problem brought back bad memories. hhp

by superbat

Nice! I was thinking I was alone out here. Good to here from someone who knows what I'm talking about. I was not aware that NetManage had a problem, as I don't see it in any other software. I am my network engineer, and I do have timing problems that I have proposed fixes for. I simply need management approval, & that is always delayed untill the last minute when people start quitting in protest...
Anyway, thanks for the information.

This discussion is closed to new replies.