Shared file access

[dallascisco]

I have a friend whom I just set up s network for. He runs a cafeteria business and has 5 machines that are all windows 7. I twas quite an upgrade since he was previously using windows 98 and quickbooks 98. Now he has windows 7 and quickbooks 2010 with 3 printers that are shared off of machines. All machines are connected wired via a central 10/100 hub.

I got all of the machines to see each other and print. The issue is with file access. One of the machines is a "server" or at least a place where other machines can access data. The employees at the cafeteria access the central shared folder stored there to get recipes and such. The day I set it up we went to each machine and accessed the share, edited a file and saved without issue. Now he is telling me that 2 of the machines can't do this any longer but one can. Also, he says that the machines that can't don't let go of the file once closed and he has to reboot the server to allow access to the files again. Did I miss something?

 

[zigzag3143]

I have a friend whom I just set up s network for. He runs a cafeteria business and has 5 machines that are all windows 7. I twas quite an upgrade since he was previously using windows 98 and quickbooks 98. Now he has windows 7 and quickbooks 2010 with 3 printers that are shared off of machines. All machines are connected wired via a central 10/100 hub.

I got all of the machines to see each other and print. The issue is with file access. One of the machines is a "server" or at least a place where other machines can access data. The employees at the cafeteria access the central shared folder stored there to get recipes and such. The day I set it up we went to each machine and accessed the share, edited a file and saved without issue. Now he is telling me that 2 of the machines can't do this any longer but one can. Also, he says that the machines that can't don't let go of the file once closed and he has to reboot the server to allow access to the files again. Did I miss something?

Unfortunately Unlike a true server, file sharing can be problematic. If a file is open on one it is by nature unavailable to the others until it is closed.

I wonder if the sharing problem is being caused by using "homegroup" Are You?

ken

 

[dallascisco]

No, I'm using classic file shares.

I understand that if one machine has a file open others can't access it. The problem is that when one machine closes it nobody else can open it until the "server" is rebooted.

 

[CommonTater]

No, I'm using classic file shares.

I understand that if one machine has a file open others can't access it. The problem is that when one machine closes it nobody else can open it until the "server" is rebooted.

This could actually be a software problem... What software is being used to access these files?

What happens when software opens a file (local or remote) is that it places a lock on that file, saying "Don't mess with this" but then it doesn't release the lock when the file is saved... A common programmer's error, actually... I've made it myself.

Rather than rebooting the server next time this happens, go around to each machine and see if the program used to access the files is still running on one of them... close the program and see what happens....

If I'm right, it's not a networking problem at all.

 

[zigzag3143]

No, I'm using classic file shares.

I understand that if one machine has a file open others can't access it. The problem is that when one machine closes it nobody else can open it until the "server" is rebooted.

I understand that. Desktop/client machines often dont "release" files till rebooted. I have seen that in other win 7 installs. Is there any way you can run true server software on that machine?

Ken

 

[dallascisco]

commontater-

The software being used is MS office. I'll see if they are still running next time.

Zigzag-

If it were my call he would.

 

[WindowsStar]

What version of MS Office? I have seen issues with MS Office 2007 locking files, even in a true server/client environment.

 

[dallascisco]

Office 2007 is what he is using.

What version of MS Office? I have seen issues with MS Office 2007 locking files, even in a true server/client environment.

 

[zigzag3143]

commontater-

The software being used is MS office. I'll see if they are still running next time.

Zigzag-

If it were my call he would.

Figured. Office does allow access but I am not sure if that will fix the problem

Ken

 

[WindowsStar]

commontater-

The software being used is MS office. I'll see if they are still running next time.

Zigzag-

If it were my call he would.

Figured. Office does allow access but I am not sure if that will fix the problem

Ken

We have not figured out a work around. Once the file is locked typically a reboot is the only way to fix it. We only have one server that is used this way and we have is scheduled to reboot each night. Everything else has been converted to a true server/client database.

 

[CommonTater]

commontater-

The software being used is MS office. I'll see if they are still running next time.

Zigzag-

If it were my call he would.

Figured. Office does allow access but I am not sure if that will fix the problem

Ken

We have not figured out a work around. Once the file is locked typically a reboot is the only way to fix it. We only have one server that is used this way and we have is scheduled to reboot each night. Everything else has been converted to a true server/client database.

I'm thinking that a simple change in strategy might be all that's needed... It depends on how they operate... If they're all connecting to the database each morning and staying hooked up all day, this could be a real nightmare. On the other hand if they're just loading files in Word the fix might simply be to close word when they're done...

 

[dallascisco]

They are closing the application, that's the problem. It doesn't make any sense. The other thing that doesn't add up is why 3 machines can edit the files on the share folder but not the other 2.

The people who access the files are workers in the cafeteria. They open files to update flyers and edit recipes so it's important that they all be able to access the shared folder to update these files.

Figured. Office does allow access but I am not sure if that will fix the problem

Ken

We have not figured out a work around. Once the file is locked typically a reboot is the only way to fix it. We only have one server that is used this way and we have is scheduled to reboot each night. Everything else has been converted to a true server/client database.

I'm thinking that a simple change in strategy might be all that's needed... It depends on how they operate... If they're all connecting to the database each morning and staying hooked up all day, this could be a real nightmare. On the other hand if they're just loading files in Word the fix might simply be to close word when they're done...

 

[CommonTater]

They are closing the application, that's the problem. It doesn't make any sense. The other thing that doesn't add up is why 3 machines can edit the files on the share folder but not the other 2.

The 3 but not 2 might be permissions based.

I'm still puzzling over why the files become locked and stay that way...

 

[dallascisco]

The permissions to the share are set to change for the everyone group.

They are closing the application, that's the problem. It doesn't make any sense. The other thing that doesn't add up is why 3 machines can edit the files on the share folder but not the other 2.

The 3 but not 2 might be permissions based.

I'm still puzzling over why the files become locked and stay that way...

 

[CommonTater]

The permissions to the share are set to change for the everyone group.

Ok... one more thing to try before I step back and ask the other to take a stab at this...

In your network adaptors properties... Highlight TCPIP v4, then click properties, then advanced, then Wins... in that page, select "enable NetBios" and then turn off LMHosts lookup... Ok your way out...

Also in that same area, you may want to uncheck the "Internet protocal version 6" there are still a lot of routers and switches around that do not like IPv6.


Does that make a difference?

 

[dallascisco]

This ended up being a simple permissions issue. Funny how a non-tech user morphs it.