rhardie
March 17th, 2008, 09:36 PM
Problem:
We are unable to open a Word .docx file on a laptop connected to the server and we ARE able to open the same file from a second laptop.
We suspect it is a file rights issue but I don't know what to change.
This happened "suddenly", I am told.
Scenario:
Lap top A creates word document and stores on Linux server. Laptop B can not open the file BUT it can see the file in the folder AND it can "edit" the file. Double clicking to open the file results in an error that says "pathnam/file can not be found"
Laptop A is able to open the file.
Laptop B can create a Word.docx file in the exact same folder but when the file is closed and Laptop B attempts to open the file it just created, then it gets the same error as described above.
Exel files within the same folder behave normally and are accessable by laptop B.
All hardware and software on the network appears to work normally except this problem.
Configuration:
Server: Ubuntu 7.10 LAMP with GUI; SAMBA
Network: Ethernet; shared public folders and private folders on the Linux server
Laptops: Windows Vista; MS Office 2008
Notes:
User has no access to Linux server or server log in to modify folder settings.
User noted the server went to backup power (UPS) earlier in the day but didn't appear to experience power inturruptions to the server.
Thanks for any assistance. :-)
We are unable to open a Word .docx file on a laptop connected to the server and we ARE able to open the same file from a second laptop.
We suspect it is a file rights issue but I don't know what to change.
This happened "suddenly", I am told.
Scenario:
Lap top A creates word document and stores on Linux server. Laptop B can not open the file BUT it can see the file in the folder AND it can "edit" the file. Double clicking to open the file results in an error that says "pathnam/file can not be found"
Laptop A is able to open the file.
Laptop B can create a Word.docx file in the exact same folder but when the file is closed and Laptop B attempts to open the file it just created, then it gets the same error as described above.
Exel files within the same folder behave normally and are accessable by laptop B.
All hardware and software on the network appears to work normally except this problem.
Configuration:
Server: Ubuntu 7.10 LAMP with GUI; SAMBA
Network: Ethernet; shared public folders and private folders on the Linux server
Laptops: Windows Vista; MS Office 2008
Notes:
User has no access to Linux server or server log in to modify folder settings.
User noted the server went to backup power (UPS) earlier in the day but didn't appear to experience power inturruptions to the server.
Thanks for any assistance. :-)