Topic: Win7 client on sme8 workgroup

[uwe]

Which win7*.reg files are required if using sme 8 as a workgroup server?

Thanks in advance.

[idp_qbn]

If you are only using a Workgroup (as in Windows Workgroup"  then you need to have the username/Password on the PC the same as the one on the SME server. Or get the wWin7 box to conect to the network drive using another identity. (It's a microsoft thing - you should know how to do that.)

If you are going the full Windows Domain path, then look at http://wiki.contribs.org/Windows_7_Support

Good luck
Ian

[uwe]

Thanks Ian.

I know some of those .reg files are specifically for sme as a domain controller but I was wondering if any were applicable in a workgroup environment.

We are seeing some strange behaviour with a commercial application running on windows 7 clients to a workgroup share on sme. The application provider is always saying to reboot the server whenever some error occurs.  I know it's not sme or samba so I am looking at the workstations and hence the .reg file question.

Uwe.

[idp_qbn]

Perhaps there is a file-locking problem with the application. eg two or more users at the same time may want write access to a shared file.

Using a shared folder in Windows workgroup with SME is pretty simply a matter of creating an Ibay for the data and making sure the users concerned have group read access (and if necessary,write access) to that share.

Without knowing the details of the application you are using (and I emphasis I am not a guru on that) it feels like a problem with the application. The developer should not be telling you to reboot a server as a routine way of solving a problem. Server= shared environment : not good for rebooting.

I don't know how to tell if a file is locked by the system in Linux or even in Windows.
BUT -  A common thing I have seen in the past is the developer gets the application to create a lock-file when access is required, then delete it afterwards. Sometimes these can be left behind. I have seen them as lock.txt, lock.dat, xyz.lck etc  This method is a bit kludgy and a well-written application should not need to use it, but they do.....

A reboot will clear system locked files, but that's a bit like using a steam-roller to kill cockroaches.

Sorry that is probably not much help.

Cheers
Ian

[janet]

uwe

I know some of those .reg files are specifically for sme as a domain controller but I was wondering if any were applicable in a workgroup environment.

AFAIK they are only required to be used on workstations that wish to join a sme server Domain.

We are seeing some strange behaviour with a commercial application running on windows 7 clients to a workgroup share on sme.

If you want useful answers from here, then you need to tell us what that commercial application is & describe that strange behaviour.
It is quite possible that some other user has already experienced your issue.

I know of "commercial accounting/database applications" that are not supported on Linux, purportedly due to "timing" issues (maybe "race" conditions) & the software authors advise that it is only supported to work on Windows based servers.

Try running the software across the network from an install on a Windows workstation share, & see whether you still have problems or not.
You may need to setup another Windows server or run Windows in a virtual environment on your sme server. If you only have a few (less than 10) users accessing it, then you can use Windows workstation software rather than a full blown version of Windows server software.

[purvis]

UWE.
Reboot the server?  That is just plum unacceptable of an answer to me. Sounds like the developer knows little about networking and does want to study networking either. Why do these people write what might be called multiuser software when a lot of the time it is not.

Go safe.
Use only SMB version 1. Disabled opportunity file locking on the workstations.
Try that first if your files are being corrupted..

2nd
Learn about  veto oplocks in samba if you are using multiuser database software.