[RESOLVED] Netware / Word Saving Probs

Printable View

January 23rd, 2001, 05:45 AM
imoore

Netware / Word Saving Probs

Can anybdoy please help, this problem has happened a few times on a few different PCs -we've tried ms kb but with little success.
Windows 98 with Office 97 using Novell Netware Client 3.2. When trying to save to a mapped network drive in WORD you get network or file permission error - network connection may be lost OR check drive to make sure door is closed to ensure is contain the correct disk or CD. You cannot then save form Word to that drive BUT you can from Excel. The same file on another PC works fine and saves okay. The netware permission are correct.

MS say to copy of your local hard drive and then copy back!!!!!! We do not want to do this.

Any help?
Please let me know if this should be posted somehere else.
Thanks,
Ian.
January 23rd, 2001, 06:26 PM
cyberhh

1. Does the user have erase rights to the network location? (I will assume yes as it works in Excel)

2. What is the drive mapping? Try enabling/disabling MAP ROOT / remapping to the volume instead of the volume and subdirectory.

3. Keep me updated.

------------------
Death is lighter than a feather - duty heavier than a mountian.
January 23rd, 2001, 06:33 PM
StevePorter

Are you running a "networked" version of Word, or a "single user" version? Novell can get picky about the user rights under networked versions... https://forums.windrivers.com/

------------------
You want the right answer?!? You must be asleep, 'cuz you're dreamin'... https://forums.windrivers.com/
January 24th, 2001, 02:25 AM
imoore

cyberhh
1. Yes user does have correct permissions.
2. Need to try and modify MAP/ROOT command (Will keep you updated on this one)
---------------------------------------------
StevePorter
-----------------------------------
All installations of Office are local to hard drive - Netware server used only for file and print sharing.

Thanks for the advice - you get back to you ASAP.
January 24th, 2001, 10:04 AM
iamtheman

Unfortunately I don't have alot of time right now to look for my old info. But I have come across this before and it does have something to do with the MAP Root command. There are actually a couple things that could cause this, they were listed in a tech support doc on either Novell or Microsoft's site. If I can find it I will post a link.

------------------
Born to Network