what does the red x mean on a network share?

  • Thread starter Thread starter Will K
  • Start date Start date
W

Will K

Hi

I am networking an XP PC with a 98 PC. I have noticed on the XP PC that the share to the 98 box has a red x. But when I double click on that share (all seen under my computer) it opens up right away.

The reason I ask is that I have a database shared out on the 98 box and when I update that database from the XP box it seems to fail a lot unless I access the share first from my computer.

Is there a way to keep the share from becoming inactive or make sure its active? Does this indicate a network problem?
 
Wow. This seems to be an epidemic. I posted a similar
question this morning and have seen many others like it.
There does not seem to be an answer except for this
Knowledge Base article: (283492) which applies ONLY to
drives that require credentials to log on.

To answer your question, the red "X" normally means the
drive isn't connected. However, in my case if I right
click on the drive that has the red "x" one of the menu
choices I get is to DISCONNECT (implying it's already
connected). If I do nothing after right clicking (escape
out) the red "X" suddenly goes away. Despite the fact
that it appears as if the drive is connected, other
applications cannot access it unless you manually click on
it (as you, and many others, have found).

The drive, if "reconnect at logon" is selected should
reconnect at logon and stay that way. My Win98 machines
do this just fine, the XP machines do not. Again, no word
from Microsoft on why.

I have Dell working on it, too, so if I get an answer I'll
post back.
-----Original Message-----
Hi

I am networking an XP PC with a 98 PC. I have noticed on
the XP PC that the share to the 98 box has a red x. But
when I double click on that share (all seen under my
computer) it opens up right away.
The reason I ask is that I have a database shared out on
the 98 box and when I update that database from the XP box
it seems to fail a lot unless I access the share first
from my computer.
Is there a way to keep the share from becoming inactive
or make sure its active? Does this indicate a network
problem?
 
You Experience Slow File Server Performance and Delays Occur When You
WGID:491
ID: 822219.KB.EN-US CREATED: 2003-06-02 MODIFIED: 2003-08-08


Public | kbAudITPRO kbAudEndUser


============================================================================
===
----------------------------------------------------------------------------
---
The information in this article applies to:

- Microsoft Windows XP Professional
- Microsoft Windows XP Tablet PC Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
- Microsoft Windows NT Server 4.0 (Version: 4.0)
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Server, Enterprise Edition
- Microsoft Windows NT Workstation 4.0 (Version: 4.0)

----------------------------------------------------------------------------
---



Important This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

KBLink:256986.KB.[LN]: Description of the Microsoft Windows Registry






SYMPTOMS
========

You may experience one or more of the following symptoms when you work with
files over the network:

- A Windows-based file server that is configured as a file and print
server stops responding and file and print server functionality
temporarily stops.

- You experience an unexpectedly long delay when you open, save, close,
delete, or print files that are located on a shared resource.

- You experience a temporary decrease in performance when you use a
program over the network. Performance typically slows down for
approximately 40 to 45 seconds. However, some delays may last up to 5
minutes.

- You experience a delay when you perform file copy or backup
operations.

- Windows Explorer stops responding when you connect to a shared
resource or you see a red X on the connected network drive in Windows
Explorer.

- When you log on to the file server, after you type your name and
password in the "Log On to Windows" dialog box, a blank screen appears.
The desktop does not appear.

- A program that uses remote procedure call (RPC) or uses named pipes
to connect to a file server stops responding.

- The server temporarily stops responding and one or more event ID messages
similar to the following messages appear in the system log on the file
server:




Event ID: 2022

Source: Srv

Type: Error

Description:
Server was unable to find a free connection <number> times in the last
<number> seconds.


Event ID: 2021

Source: Srv

Type: Error

Description:
Server was unable to create a work item <number> times in the last
<number> seconds.


Event ID: 2020

Source: Srv

Type: Error

Description:
The server was unable to allocate from the system paged pool because the
pool was empty.




Event ID: 2019

Source: Srv

Type: Error

Description:
The server was unable to allocate from the system nonpaged pool because
the pool was empty.



Event ID: 2510
Source: Server
Event Type: Error


Description:

The server service was unable to map error code 1722.


1722 = RPC_S_SERVER_UNAVAILABLE = RPC Service is unavailable.
Additionally, the following event appears in the system log on the client
computer:


Event ID: 3013

Event Type: Error

Event Source: MrxSmb / Rdr

Description:
The redirector has timed out a request to <ComputerName>.

- You receive an error message similar to one of the following messages when
you try to connect to a shared resource:

System error 53. The network path was not found.

-or-

System error 64. The specified network name is no longer available.

- You are intermittently disconnected from network resources, and you
cannot reconnect to the network resources on the file server. However,
you can ping the server, and you can use a Terminal Services session to
connect to the server.

- If multiple users try to access Microsoft Office documents on the
server, the "File is locked for editing" dialog box does not always
appear when the second user opens the file.

- A network trace indicates a 30 to 40 second delay between an SMB
Service client command and a response from the file server.


CAUSE
=====

This issue may occur if a non-Microsoft program that is installed on your
computer uses an outdated kernel-mode filter driver. The kernel-mode
filter driver may be outdated if the following conditions are true:

- One of the following programs is installed on the computer:

- ARCserve Backup Agent for Open Files or ARCserve Open File Agent
from Computer Associates International, Inc. is installed on your computer,
and the Ofant.sys driver for the program is outdated.

- Open Transaction Manager is installed on your computer, and the
Otman.sys driver for the program is outdated.

Note Open Transaction Manager is included with certain programs from
VERITAS Software Corporation, but it can also be installed separately from
the VERITAS program. For example, Open Transaction Manager may be included
with Open File Option. This program may be included with VERITAS Backup
Exec.

- A VERITAS program that uses the Otman4.sys or Otman5.sys driver (such as
Open File Option) is installed on your computer, and the Otman4.sys or
Otman5.sys driver for the program is outdated.

- The driver for the program is incompatible with the filter driver
that is installed on the computer by a non-Microsoft antivirus program.
As a result, the filter driver on the server may return an incorrect
status code to the Server service. For example, the filter driver may
return a STATUS_SUCCESS code instead of a
STATUS_OPLOCK_BREAK_IN_PROGRESS code.




RESOLUTION
==========

To resolve this issue, contact the manufacturer of the program to inquire
about the availability of a filter driver update. For more information about
how to contact Computer Associates to obtain the latest update for the
Ofant.sys driver, visit the following Computer Associates Web site:

http://support.ca.com/

If you installed Open Transaction Manager separately, contact Columbia Data
Products, Inc. to inquire about the availability of an update that may
resolve this issue. To contact Columbia Data Products, visit the following
Columbia Data Products Web site:





http://www.cdp.com/

For more information about how to contact VERITAS, visit the following
VERITAS Web site:

http://support.veritas.com/

Microsoft provides third-party contact information to help you find
technical support. This contact information may change without notice.
Microsoft does not guarantee the accuracy of this third-party contact
information.


MORE INFORMATION
================

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.

To temporarily work around this issue, restart the Server services on the
server. To restart the Server services, follow these steps:

1. Click "Start", and then click "Run".

2. In the "Open" box, type "cmd" (without the quotation marks), and
then click "OK".

3. At the command prompt, type the following lines, and press ENTER after
each line:


"net stop server
net start server" (without the quotation marks)


To troubleshoot this issue, use any of the following methods:

- Use Performance Logs and Alerts to monitor the"Avg. Disk Queue
Length" counter of the "PhysicalDisk" performance object. Under
ordinary conditions, the number of waiting input/output (I/O) requests
is typically no more than 1.5 to 2 times the number of spindles that
the physical disk has. Most disks have one spindle, although redundant
array of independent disks (RAID) devices typically have more than one
spindle. When a program runs small successive I/O operations, you see a
spike in the "Current Disk Queue Length" counter when I/O-bound
operations are queued. You may also see an increase in the "Context
Switches/sec" counter of the "System" performance object.

- Disable opportunistic locking on either the client or on the server. To
disable opportunistic locking on the client, set the following registry
value to 1:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\O
plocksDisabledTo disable opportunistic locking on the server, set the
following registry value to 0:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parame
ters\EnableOplocks


For additional information about how to disable opportunistic locking, click
the following article number to view the article in the Microsoft Knowledge
Base:



KBLink:296264.KB.[LN]: Configuring Opportunistic Locking in Windows 2000

- Use the Microsoft Configuration Capture Utility (MPS_REPORTS) to determine
the version of the filter driver that is installed on your computer.



For additional information about the Microsoft Configuration Capture
Utility, click the following article number to view the article in the
Microsoft Knowledge Base:



KBLink:818742.KB.[LN]: Overview of the Microsoft Configuration Capture
Utility (MPS_REPORTS)

- Edit the registry to temporarily deactivate the filter driver.



For additional information about how to temporarily deactivate the
kernel-mode filter driver, click the following article number to view the
article in the Microsoft Knowledge Base:



KBLink:816071.KB.[LN]: How to Temporarily Deactivate the Kernel Mode
Filter DriverThe registry key that stores information for the Ofant.sys
driver is

Ofadriver.





REFERENCES
==========



For additional information, click the following article numbers to view the
articles in the Microsoft Knowledge Base:



KBLink:814112.KB.[LN]: Files on Network Shares Open Slowly or Read-Only
or You Receive an Error Message


KBLink:275555.KB.[LN]: ARCserveIT Open File Manager (Ofant.sys) May
Affect SQL Server 7.0


KBLink:821246.KB.[LN]: Office Files Are Slow to Open, Close, Save, or
Print from a Network


KBLink:816071.KB.[LN]: How to Temporarily Deactivate the Kernel Mode
Filter Driver


KBLink:252332.KB.[LN]: Event ID 3013 When You Copy Files to a Server
That Is Under Disk Stress


The third-party products that this article discusses are manufactured by
companies that are independent of Microsoft. Microsoft makes no warranty,
implied or otherwise, regarding the performance or reliability of these
products.





QUERY WORDS
===========

oplocks ofant ArcServ ARCserve ARCserveIT BrightStor performance degradation
slow intermittent sporadically srv.sys lanmanserver
freeze hangs hanging OFANT.EXE ofant.sys QAFilter.sys ofadriver CA Inoculan
McAfee NetShield 4.5 McShield Norton, OTMAN.sys OTMAN5.SYS Open Transaction
Manager, Veritas BackupExec, Gigabit
Word Excel PowerPoint Outlook Exchange MS-Office
<<\** Database Link: Type = "SolutionObject" Database = "None" Value =
"SOX030220700019" **/>>

<<\** Database Link: Type = "SolutionObject" Database = "None" Value =
"SOX030206700031" **/>>

<<\** Database Link: Type = "SolutionObject" Database = "None" Value =
"SOX030128700047" **/>>

<<\** Database Link: Type = "SolutionObject" Database = "None" Value =
"SOX020614700029" **/>>

<<\** Database Link: Type = "SolutionObject" Database = "None" Value =
"SOX000427700133" **/>>

<<\** Database Link: Type = "SolutionObject" Database = "None" Value =
"SRQ030503600120" **/>>




============================================================================
===


Publishing Keywords : kbNTTermServ400 kbNTTermServSearch kbwin2000AdvServ
kbwin2000AdvServSearch kbwin2000Pro kbwin2000ProSearch kbwin2000Search
kbwin2000Serv kbwin2000ServSearch kbWinAdvServSearch kbWinNT400search
kbWinNTS400 kbWinNTS400search kbWinNTsearch kbWinNTSEntSearch kbWinNTSsearch
kbWinNTW400 kbWinNTW400search kbWinNTWsearch kbWinXPPro kbWinXPProSearch
kbWinXPSearch kbWinXPTabPC
Keywords : kbwinservperf kbprb kbEntireNet
Revision Type : Major
Workgroup : Server - (EntireNet) Windows 2000 [491]
Billing Product : Windows Svr 2000 EN [98927]
Original Language : EN-US
Source Language : EN-US
============================================================================
===



--
Thank you,

Brennan Crowe
Microsoft corporation

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

Thanks for the info.

I saw that article. On this particular drive we don't require any credentials to connect. Its set to connect reconnect at login. The funny thing is sometimes the update works. Mostly it does not but I know none of the users ever check that share, they just stay in the program all day.

We are also on a Dell in this case. I have not contacted them. Please do post back or email me if you find out anything. I setup an Icon for the share on the desktop and told the users to double click it before they do the udpate but they are not happy with that solution.

Thanks again for your information.
Wow. This seems to be an epidemic. I posted a similar
question this morning and have seen many others like it.
There does not seem to be an answer except for this
Knowledge Base article: (283492) which applies ONLY to
drives that require credentials to log on.

To answer your question, the red "X" normally means the
drive isn't connected. However, in my case if I right
click on the drive that has the red "x" one of the menu
choices I get is to DISCONNECT (implying it's already
connected). If I do nothing after right clicking (escape
out) the red "X" suddenly goes away. Despite the fact
that it appears as if the drive is connected, other
applications cannot access it unless you manually click on
it (as you, and many others, have found).

The drive, if "reconnect at logon" is selected should
reconnect at logon and stay that way. My Win98 machines
do this just fine, the XP machines do not. Again, no word
from Microsoft on why.

I have Dell working on it, too, so if I get an answer I'll
post back.
-----Original Message-----
Hi

I am networking an XP PC with a 98 PC. I have noticed on
the XP PC that the share to the 98 box has a red x. But
when I double click on that share (all seen under my
computer) it opens up right away.
The reason I ask is that I have a database shared out on
the 98 box and when I update that database from the XP box
it seems to fail a lot unless I access the share first
from my computer.
Is there a way to keep the share from becoming inactive
or make sure its active? Does this indicate a network
problem?
 
Well, Dell told me to take a hike. After exchanging a few
e-mails with 2 different techs they finally told me that
their responsibility is hardware and the hardware is
working. Thank you for choosing Dell. Have a nice life.
They did send me some nifty links after pulling some
keywords out of my e-mails. None even remotely addressed
the problem.

Microsoft, however, tells me it's Dell's responsibility to
support my software problems per their licensing
arrangement. Otherwise I have to pay $100 for support.

The proverbial rock and a hard place.

I'm thinking of sending my new Dell Inspirion 8500 back
and sticking with my old IBM/Win98 machines.....they're
slow but they work.

Jim
-----Original Message-----
Hey,

Thanks for the info.

I saw that article. On this particular drive we don't
require any credentials to connect. Its set to connect
reconnect at login. The funny thing is sometimes the
update works. Mostly it does not but I know none of the
users ever check that share, they just stay in the program
all day.
We are also on a Dell in this case. I have not contacted
them. Please do post back or email me if you find out
anything. I setup an Icon for the share on the desktop and
told the users to double click it before they do the
udpate but they are not happy with that solution.
 
Hi,

The red x is by design to save resources. The network drives are not
connected until they need to be used. Some applications cannot handle the
delay in reconnecting. If your application is having an issue, you may
consider disabling autodisconnect per the intructions below. Sometime
network drives still get disconnected even with autodisconnect disabled.
Usually this is caused by third party software or drivers (a/v software,
network card agents, etc).




IF you are using applications that cannot automatically reconnect network
drives, you can disable the autodisconnect behavior on either the server or
client side by changing the following registry keys:

On the server


-
HKLM\System\CCS\Services\LanManServer\Parameters\Autodisconnect=0x0000FF
FF


Note: The preceding entry must be located on the computer that
offers the share or shares.
The valid value range if you edit the LAN
Autodisconnect parameter in the registry is 0 to 4294967295
(0xffffffff). - For
a Windows 2000 Server in a Domain, running either as a domain
controller or as
a server, the maximum value is 65,535 (0xffff). Values set above this
will be
returned to 0xffff after policy refresh. Windows 2000 Servers in a
workgroup
may be set to any value as indicated.

On the client


- HKLM\System\CCS\Services\LanManWorkstation\Parameters\KeepConn=65535

Value : KeepConn REG_DWORD 1 to 65535 seconds
Default
: 600 (10 minutes)
The value of KeepConn specifies the maximum amount of
time that a connection can be left dormant.

Note:
Windows 2000 processes the KEEPCONN registry key differently than Microsoft
Windows NT 4.0, and permits the connection to the target server to time
out.

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Date: Wed, 15 Oct 2003 12:14:14 -0600
References: <#[email protected]>
<[email protected]>
X-Newsreader: Groupwise 6.0.1
From: Will K<[email protected]>
Subject: Re: what does the red x mean on a network share?
Message-ID: <[email protected]>
Newsgroups: microsoft.public.windowsxp.network_web
NNTP-Posting-Host: 24.123.84.238
Lines: 1
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.windowsxp.network_web:140393
X-Tomcat-NG: microsoft.public.windowsxp.network_web

Hey,

Thanks for the info.

I saw that article. On this particular drive we don't require any
credentials to connect. Its set to connect reconnect at login. The funny
thing is sometimes the update works. Mostly it does not but I know none of
the users ever check that share, they just stay in the program all day.
We are also on a Dell in this case. I have not contacted them. Please do
post back or email me if you find out anything. I setup an Icon for the
share on the desktop and told the users to double click it before they do
the udpate but they are not happy with that solution.
 
Hello ,
Does this apply to XP Pro as well. I am spending the money with Microsoft to
keep the mapped drives on reboot connected. So far 8 hours today and money
out it still does not work. I am woundering if it is possible to remove the
credentials from a mapped drive to login correctly on reboot.
I have been working on this for a week now. This news group is the nearest I
have come to a soultion. Thanks
 
It's normal. A connection to a network share automatically
disconnects after a predetermined duration, unless your computer is
keeping files open on the network share.

As soon as you access the share, it automatically reconnects.

I would not worry about it.
 
Back
Top