Problem writing a file to a remote location with RTC

colneech

Hi all,

We are trying to use the RTC to write a file to a remote server. The CIFS service on this server has been deligated to the service account running the NAV server but when we try to run the process that writes the file for the first time, it will return an error.

If the RTC is closed and then opened again, the file can be written to the location fine.

The problem will reoccur if the client machine is shutdown and started again.

Has anyone else had this problem or have any idea's to resolve this so the file will write striaght away without the client needing to be opened and then closed?

Thanks,

Colin

colneech

Hi,

The error returned by the RTC is 'Either the caller does not have the required permission or the specified path is read-only'

On the server that the files will be written to, the security event log shows a logon from 'NT AUTHORITY\ANONYMOUS LOGON' using NTLM from the server running the NAV Server service.

If I then close the RTC on the client and open it again, run the same process to write the file it will work correcty using Kerberos and the service account running the Nav server.

Anyone have any idea's? ](*,)

Thanks

jflynn

Having the same issue. Running 2009 r2 hotfix version 32228. Let me know if you get a resolve.
Thanks,

fufikk

Hi,

they seem to have found solution here: http://www.mibuso.com/forum/viewtopic.php?f=32&t=37458

jflynn

That solution did not work either. User gets error, closes NAV, goes back in and does same thing, and it works perfectly. Does not make sense.

dave_c

Just adding my name to the list of people experiencing this issue.

sh

Hi guys,

just wanted to share our experience with this issue. In our case the 3-Tier setup runs on three different machines plus a fourth machine for the CIFS service. RTC runs fine (Kerberos enabled) but we had trouble with delegation towards CIFS. After we did plenty of troubleshooting ourselves, we decided to involve MS and Mr. Lohndorf-Larsen came up with a solution.

MS recently found a problem in SMB2. If both of your machines (NAV Server and CIFS) are running on Windows Server 2008, they will use SMB2 and therefore it might affect you too. The only known work around so far is to disable SMB2 (going back to SMB1) by setting the following registry key:

Create a REG_DWORD-key in registry called Smb2 under this key:
HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

and then set this key value to 0.

You have to set this only at the machine which provides the share.
In our case it took a while to take effect (even after a reboot) so be patient.