Re: Network shares issue

Todd,

Thanks. You've given me a lot to look at on Monday.

--
Al Reid

"Todd J Heron" <todd_heron(delete)@hotmail.com> wrote in message
news:%23Su2MtM7FHA.3876@xxxxxxxxxxxxxxxxxxxxxxx
> Possible causes/Solutions (in order of likelihood):
>
> #1 Mapped Drive Connection to Network Share May Be Lost:
> http://support.microsoft.com/?kbid=297684
>
> Windows clients may lose their network connection to a domain Server if
> the computer is idle for 15 minutes (the default timeout). For no client
> disconnect, follow the below instructions:
>
> 1) Open the registry editor
> 2) Navigate to
> HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
> 3) Set the Reg_DWord hex value of "autodisconnect"=ffffffff
> Note: If "autodisconnect" doesn't exist, add it.
>
> Alternative solution to registry edit:
> Open a command prompt on the workstation and run:
>
> net config server /autodisconnect: -1
>
> Note: Setting this from the command line will turn off auto tuning for
> the server service. Editing the registry is the generally recommended
> solution. The command: net config server /autodisconnect:-1 must be run on
> the server with the shares on it, not the client accessing the shares.
> Windows NT and Windows 2000+ use two different Autodisconnect parameters;
> one for disconnecting Remote Access Service (RAS) connections and another
> for disconnecting LAN connections. The RAS Autodisconnect parameter is
> documented in the Microsoft Knowledge Base article Q153944, but the LAN
> version is undocumented. The only published reference to this
> Autodisconnect is in the Windows NT Resource Kit NT Registry Entries help
> file, in an overview of entries for the LanmanServer Parameters section.
>
> How Autodisconnect Works in Windows NT and Windows 2000:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;138365
>
> Server Service Configuration and Tuning (2000):
> http://support.microsoft.com/Default.aspx?kbid=128167
>
> Server Service Configuration and Tuning (XP):
> http://support.microsoft.com/kb/314498/EN-US/
>
> REG: Server Service Entries, PART 1
> http://support.microsoft.com/kb/102967/EN-US/
>
> REG: Server Service Entries, PART 2
> http://support.microsoft.com/kb/102969/EN-US/
>
> -----------------------------------------------------------------------------------------
> #2 Check the NIC properties on the server to make sure that there are no
> power saving settings or "Allow this computer to turn off power to the
> NIC" type settings.
>
> #3 Update the drivers for the network card.
>
> -or-
>
> #4 The problem may be SMB signing or LAN Manager authentication level. In
> Windows 2003, default server policy forces all SMB traffic to be digitally
> signed which seems to cause a problem in some configurations of XP Pro.
> In Local Security Policy (Start > Run > secpol.msc > OK) navigate to
> security options (Security settings > Local policies > Security) and try
> disabling the option for Microsoft network server:digitally sign
> communications(always). Ensure you do this on all machines involved (such
> as via a GPO for an OU). Run gpupdate /force on the server after making
> the change and do the same on the client machine afterwards.
>
> Security settings that can cause a problem with downlevel client access:
> http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;811497
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823659
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
> "Al Reid" <areidjr@xxxxxxxxxxxxxxxx> wrote in message
> news:eiTx98D7FHA.3976@xxxxxxxxxxxxxxxxxxxxxxx
>> Todd,
>>
>> Thanks for the info. I will check out your suggestions.
>>
>> You stated that " I'm not sure you should attempt to alter this initial
>> delay." That delay of up to two minutes is the crux of the
>> user complaints. It seems that the database connections stay alive and
>> responsive, however, any time a file needs to be accessed,
>> there is a delay. This is driving the users and their management crazy
>> and causing me a lot of grief. Since my application is the
>> only one running under this scenario, they are blaming the application
>> (and subsequently the developer). Is there any way to
>> increase the timeout (if that is what it is) and thus reduce the impact?
>> It seems that 15 to 20 minutes between file access
>> attempts is enough to introduce the long delay.
>>
>> BTW, on one user machine I installed a small app that copies a 20 byte
>> file every couple of minutes and the problem is masked. I
>> don't see this as a solution, however.
>


.

Relevant Pages

  • MaxConnectionsPerServer
    ... In Windows, there is a registry key named "MaxConnectionsPerServer" allowing you to specify how many concurrent connections per client to a server are allowed. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: multi-threaded server
    ... A client doesn't need anything fancy. ... alternatives to selectyou'd likely prefer in Windows: ... Microsoft MVP, MCSD ... throughput if the number of simultaneous connections were limited to ...
    (microsoft.public.win32.programmer.networks)
  • Re: Multiple machines connected to one windows server 2003 for development
    ... OS that is not Windows :-) -- just be careful what client you chose for RDP ... allow 2 simultaneous connections. ... So if you have 1 user working on server, ...
    (microsoft.public.windows.server.general)
  • Re: why need a server version?
    ... and SSH/SCP is available on any windows ... Raw network connections are not limited in any way prior ... >> Bottom line is that server licensing is a $ making exercise. ... that are not available on the client version of the OS. ...
    (microsoft.public.windows.server.general)
  • Re: maximum connections to shared folder
    ... client and the server service. ... If you type net use you will see all of your ... You can not have more than ten concurrent connections at any one time. ...
    (microsoft.public.windows.server.active_directory)