RE: Server shared drives inaccessible

Hi Terence,

I have found some new information about this problem.

The network disconnections are happening on ALL workstations. They are also
losing access to network printers and other shared drives.

I asked that all workstations get restarted at the beginning of the workday.
The network disconnections typically occur approx 8hrs later. It seems to be
scheduled.

Our individual workstations do not have anti-virus protection. We have a
sonic wall tz170 that has global network anti-virus protection. I've been
told by Sonic Wall that there is nothing in their device or software that
would cause automatic network disconnections.

I made the registry editor change you specified in your previous message. It
did not resolve the issue. The original value in the autodisconnect field was
"f". I don't know if that gives the same result as the "ffffffff" you had me
enter.

Thanks for helping me with this issue. It's getting very frustrating for
everyone as they've been "coping" with it for quite a while.


--Laura


"Terence Liu [MSFT]" wrote:

Hello Laura,

Thank you for posting here.

According to your description, I understand that a couple of workstations
regularly lose their ability to access a shared drive on the SBS. If I have
misunderstood the problem, please don't hesitate to let me know.

Based on my research, his problem may occur due to multiple factors. I
would suggest that we perform some tests to narrow down the issue first.

1. What error you get when the problematic client can not access the share
folder on SBS? Please capture screenshots on the error messages and send
the pictures to me at v-terliu@xxxxxxxxxxxxx

2. Can the problematic client access other internal client's share folder
when it can not access the share folder on SBS?

3. Can the SBS access the problematic client's share folder when the
problematic client can not access the share folder on SBS?

4. Can the problematic client access the Internet when it can not access
the share folder on SBS?

5. Try to logon the problematic client with another domain account, does
the issue reoccur?

Then, I suggest we try the following steps to see if we can resolve this
issue:

I. Please ensure the problematic client is joining in SBS domain and logon
with domain user account.

II. The issue may be caused by an anti-virus application which is scanning
Network Drive. If there is anti-virus application installed, please check
the application to prevent it from scanning network drive.

III. This problem can be caused if the autodisconnect on idle time is
configured. To workaround the issue, you can change the default time-out
period for the autodisconnect feature.

WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Click Start, click Run, type regedit (Windows 2000 or Windows Server
2003) or type regedt32 (Windows NT 4.0), and then click OK.
2. Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
3. In the right pane, click the autodisconnect value, and then on the Edit
menu, click Modify. If the autodisconnect value does not exist, follow
these steps:
a. On the Edit menu, point to New, and then click REG_DWORD.
b. Type autodisconnect, and then press ENTER.
4. Click Hexadecimal.
5. In the Value data box, type ffffffff, and then click OK.

For additional information, please see:
297684 Mapped Drive Connection to Network Share May Be Lost
http://support.microsoft.com/?id=297684

VI. Please do clean boot on the problematic client to narrow down this
issue:

To clean boot the problematic computer, please use the steps below:
a. Click Start, click Run, and then in the Open box, type "MSCONFIG"
(without the quotation marks). Click OK.

b. In the System Configuration Utility (MSConfig) window, click to select
the Selective Startup button.

c. Click to clear the check mark from the "Load startup items" below
Selective Startup.

d. Click the Services tab, click to check the "Hide All Microsoft Services"
box, and remove all the check marks from the remained Non-Microsoft
Services.

e. Click OK to close the MSConfig window. Click Yes when you are asked to
restart your computer in order to enable the changes.

f. After restarting, please check whether this issue will reoccur.

g. If there are no more problems, please use the above steps to enable
services and startup items one by one in order to figure out the root cause
of this issue.

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Server shared drives inaccessible
| thread-index: AceWV5AFBJjhv2XrRDiDYGL4//eeNw==
| X-WBNR-Posting-Host: 207.46.192.207
| From: =?Utf-8?B?TGF1cmE=?= <Laura@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Server shared drives inaccessible
| Date: Mon, 14 May 2007 11:42:02 -0700
| Lines: 7
| Message-ID: <06BA7E47-3BE7-4903-BFB4-293590960E4D@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:36577
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| We regularly have trouble with a couple of workstations losing their
ability
| to access a shared drive on the server. It seems that a reboot of the
| machine is the only thing to get it reconnected.
|
| The inactivity disconnects are set to "never".
|
| Any ideas?
|


.

Loading