<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Error on accessing Microsoft Access File from Samba in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-accessing-microsoft-access-file-from-samba/m-p/2755170#M71164</link>
    <description>Tamilvanan,&lt;BR /&gt;&lt;BR /&gt;I've heard about this problem in the past and I think is due to the way that M$ Access locks the database files.  This even occurs on native NT shares, so it's not really a samba problem, but it can be fixed from the samba side.&lt;BR /&gt;&lt;BR /&gt;M$ Access has a weird way of locking the .mdb file when accessing any network share.  This means that if the network share, in this case a samba share is showing up as a mapped drive on the client, but takes an actual refresh (for example smb_trans2_request), then Access pukes and gives you the sort of error your seeing.&lt;BR /&gt;&lt;BR /&gt;To resolve this problem, I would start by playing around with your smb.conf to enable the following paramters:&lt;BR /&gt;&lt;BR /&gt;socket options = TCP_NODELAY SO_KEEPALIVE&lt;BR /&gt;&lt;BR /&gt;This should keep the shares active from the client side and hopefully do away with the error message your seeing.&lt;BR /&gt;&lt;BR /&gt;Of course this is a trial and error type thing.  You may want to even check M$ support for a knowledge base article on this as it may be of some assistance as well.&lt;BR /&gt;&lt;BR /&gt;Hope that helps.&lt;BR /&gt;&lt;BR /&gt;-Mike</description>
    <pubDate>Mon, 01 Jul 2002 02:20:23 GMT</pubDate>
    <dc:creator>Mike Hassell</dc:creator>
    <dc:date>2002-07-01T02:20:23Z</dc:date>
    <item>
      <title>Error on accessing Microsoft Access File from Samba</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-accessing-microsoft-access-file-from-samba/m-p/2755169#M71163</link>
      <description>Hi all,&lt;BR /&gt;  I have a system running HP-UX 11.0 with Samba Server Version 2.0.9. In my samba share there are some Microsoft Access database files. When I map from WinNT/Win2k I could able to see all the file. But I am unable to open the Microsoft Access Files.My NT system throws Disk/Network Error.&lt;BR /&gt;  Can somebody throw some light on this issue.&lt;BR /&gt;Thanx &amp;amp; Regards,&lt;BR /&gt;V.Tamilvanan</description>
      <pubDate>Mon, 01 Jul 2002 01:13:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-accessing-microsoft-access-file-from-samba/m-p/2755169#M71163</guid>
      <dc:creator>TAMILVANAN</dc:creator>
      <dc:date>2002-07-01T01:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: Error on accessing Microsoft Access File from Samba</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-accessing-microsoft-access-file-from-samba/m-p/2755170#M71164</link>
      <description>Tamilvanan,&lt;BR /&gt;&lt;BR /&gt;I've heard about this problem in the past and I think is due to the way that M$ Access locks the database files.  This even occurs on native NT shares, so it's not really a samba problem, but it can be fixed from the samba side.&lt;BR /&gt;&lt;BR /&gt;M$ Access has a weird way of locking the .mdb file when accessing any network share.  This means that if the network share, in this case a samba share is showing up as a mapped drive on the client, but takes an actual refresh (for example smb_trans2_request), then Access pukes and gives you the sort of error your seeing.&lt;BR /&gt;&lt;BR /&gt;To resolve this problem, I would start by playing around with your smb.conf to enable the following paramters:&lt;BR /&gt;&lt;BR /&gt;socket options = TCP_NODELAY SO_KEEPALIVE&lt;BR /&gt;&lt;BR /&gt;This should keep the shares active from the client side and hopefully do away with the error message your seeing.&lt;BR /&gt;&lt;BR /&gt;Of course this is a trial and error type thing.  You may want to even check M$ support for a knowledge base article on this as it may be of some assistance as well.&lt;BR /&gt;&lt;BR /&gt;Hope that helps.&lt;BR /&gt;&lt;BR /&gt;-Mike</description>
      <pubDate>Mon, 01 Jul 2002 02:20:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-accessing-microsoft-access-file-from-samba/m-p/2755170#M71164</guid>
      <dc:creator>Mike Hassell</dc:creator>
      <dc:date>2002-07-01T02:20:23Z</dc:date>
    </item>
    <item>
      <title>Re: Error on accessing Microsoft Access File from Samba</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-accessing-microsoft-access-file-from-samba/m-p/2755171#M71165</link>
      <description>Hi All,&lt;BR /&gt;Thank you very much for Mike who sent a  detailed description and cause for the problem.&lt;BR /&gt; The same M$ Access file is working fine with the Samba Version 2.0.3 on HP-UX 10.20. But I am finding problem with Samba Version 2.0.9 on HP-UX 11.0. If I see the smb.conf configuration of both the server.It looks same. &lt;BR /&gt; Moreover the system which is having this M$ Access Problem is so critical one and I cannot restart the Samba unless I have a concrete solution for the problem.&lt;BR /&gt;  Can some one send me there smb.conf file where theey don't have problem in accessing MS Access which is running on above said version.&lt;BR /&gt;Thanx &amp;amp; regards,&lt;BR /&gt;V.Tamilvanan.</description>
      <pubDate>Mon, 01 Jul 2002 04:13:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-accessing-microsoft-access-file-from-samba/m-p/2755171#M71165</guid>
      <dc:creator>TAMILVANAN</dc:creator>
      <dc:date>2002-07-01T04:13:21Z</dc:date>
    </item>
  </channel>
</rss>

