Network drive technology still in Stoneages?

  • Thread starter Thread starter George Hester
  • Start date Start date
G

George Hester

Windiows 2000 Advanced Server SP3 Windows 2000 Server Client SP4.
I am having a dickens of a time trying to keep these Network drives functional. They fail sporadically and the issue is NOT DNS. For example. Booted the Server and the mapped Network drive showed red although it is supposed to reconnect at logon. Access the drive hoping the red will vanish. Sometimes it does you know. But sometimes it doesn't. Network drive still unavailable. So I will disconnect and reconnect it. That always works. Then I am back in business. For a bit.

This issue occurs over and over again. Is there a hotfix for an issue such as this or any other suggestion in Windows 2000.? I can tell it has nothing to do with my configuration but that it is because Network drive mapping as implemented by Microsoft seems to be a technology that has not gotten out of the Stoneage. Thanks.
 
You are quite correct. Drive mapping is old-school. Applications should be
configured to use UNC paths instead. If you use UNC instead of mappings do
you have the same problems?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Windiows 2000 Advanced Server SP3 Windows 2000 Server Client SP4.
I am having a dickens of a time trying to keep these Network drives
functional. They fail sporadically and the issue is NOT DNS. For example.
Booted the Server and the mapped Network drive showed red although it is
supposed to reconnect at logon. Access the drive hoping the red will
vanish. Sometimes it does you know. But sometimes it doesn't. Network
drive still unavailable. So I will disconnect and reconnect it. That
always works. Then I am back in business. For a bit.

This issue occurs over and over again. Is there a hotfix for an issue such
as this or any other suggestion in Windows 2000.? I can tell it has nothing
to do with my configuration but that it is because Network drive mapping as
implemented by Microsoft seems to be a technology that has not gotten out of
the Stoneage. Thanks.
 
Yes when I use Windows Explorer to Tools | Map Network Drive... the connection is set to
\\MachineName\(drive)$ That is a UNC path is it not? This is where the issue always occur. Of course I can set it up differently using New Network Connection (no issue here) but apps in the Server need to see the domain controller's drives as drives not Namespaces.
 
Richard said:
You are quite correct. Drive mapping is old-school. Applications
should be configured to use UNC paths instead. If you use UNC
instead of mappings do you have the same problems?
Click to expand...

Respectfully disagree - UNC paths mean, whenever you move data, you have to
change the path the client points to. Drive mapping/variables makes life
easier.
--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Windiows 2000 Advanced Server SP3 Windows 2000 Server Client SP4.
I am having a dickens of a time trying to keep these Network drives
functional. They fail sporadically and the issue is NOT DNS. For
example. Booted the Server and the mapped Network drive showed red
although it is supposed to reconnect at logon. Access the drive
hoping the red will vanish. Sometimes it does you know. But
sometimes it doesn't. Network drive still unavailable. So I will
disconnect and reconnect it. That always works. Then I am back in
business. For a bit.

This issue occurs over and over again. Is there a hotfix for an
issue such as this or any other suggestion in Windows 2000.? I can
tell it has nothing to do with my configuration but that it is
because Network drive mapping as implemented by Microsoft seems to be
a technology that has not gotten out of the Stoneage. Thanks.
Click to expand...
 
I respectfully disagree with your disagreement - but that's life. :-)

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


"Lanwench [MVP - Exchange]"
 
That's a tough one, wish I had a good solution. If drive letters are
necessary then mapping is also necessary. Have you tried setting the
AUTODISCONNECT setting on the server so that auto-disconnect is disabled?
Do you un-map then re-map the drive at logon?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Yes when I use Windows Explorer to Tools | Map Network Drive... the
connection is set to
\\MachineName\(drive)$ That is a UNC path is it not? This is where the
issue always occur. Of course I can set it up differently using New Network
Connection (no issue here) but apps in the Server need to see the domain
controller's drives as drives not Namespaces.
 
Yes when I use Windows Explorer to Tools | Map Network Drive... the
connection is set to
\\MachineName\(drive)$ That is a UNC path is it not?

Yes that is a UNC path, but that is not what he meant. He meant don't map
and drive letters at all just connect to the resource via the UNC only (no
drive letters, no "connection")
 
Distributed File System (DFS) is a good way to cover for data locations that
change.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Lanwench [MVP - Exchange]"
 
Phillip said:
Distributed File System (DFS) is a good way to cover for data
locations that change.
Click to expand...

Yes, I find DFS interesting - but I support small companies with a small
number of servers (often just one), and it just seems like overkill. I don't
have a problem with drive mappings in these situations, primitive though
they be. It is far easier for me to switch things around, and all the user
needs to know is "S is for Shared". Cheap, cheerful, and reliable. ;-)
"Lanwench [MVP - Exchange]"
Respectfully disagree - UNC paths mean, whenever you move data, you
have to change the path the client points to. Drive
mapping/variables makes life easier.
Click to expand...
Click to expand...
 
Richard said:
I respectfully disagree with your disagreement - but that's life. :-)
Click to expand...

I agree with your disagreement with my disagreement and concur. ;-)

"Lanwench [MVP - Exchange]"
Respectfully disagree - UNC paths mean, whenever you move data, you
have to
change the path the client points to. Drive mapping/variables makes
life easier.
Click to expand...
Click to expand...
 
Now how could I disagree with that? ;-)

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


"Lanwench [MVP - Exchange]"
Richard said:
I respectfully disagree with your disagreement - but that's life. :-)
Click to expand...

I agree with your disagreement with my disagreement and concur. ;-)

"Lanwench [MVP - Exchange]"
Richard G. Harper wrote:
You are quite correct. Drive mapping is old-school. Applications
should be configured to use UNC paths instead. If you use UNC
instead of mappings do you have the same problems?

Respectfully disagree - UNC paths mean, whenever you move data, you
have to
change the path the client points to. Drive mapping/variables makes
life easier.
Click to expand...
Click to expand...
Click to expand...
 
Not always but yes sometimes. Where is this setting AUTODISCONNECT set?

--
George Hester
_________________________________
Richard G. Harper said:
That's a tough one, wish I had a good solution. If drive letters are
necessary then mapping is also necessary. Have you tried setting the
AUTODISCONNECT setting on the server so that auto-disconnect is disabled?
Do you un-map then re-map the drive at logon?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Yes when I use Windows Explorer to Tools | Map Network Drive... the
connection is set to
\\MachineName\(drive)$ That is a UNC path is it not? This is where the
issue always occur. Of course I can set it up differently using New Network
Connection (no issue here) but apps in the Server need to see the domain
controller's drives as drives not Namespaces.

--
George Hester
_________________________________
Richard G. Harper said:
You are quite correct. Drive mapping is old-school. Applications should
be
configured to use UNC paths instead. If you use UNC instead of mappings
do
you have the same problems?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Windiows 2000 Advanced Server SP3 Windows 2000 Server Client SP4.
I am having a dickens of a time trying to keep these Network drives
functional. They fail sporadically and the issue is NOT DNS. For
example.
Booted the Server and the mapped Network drive showed red although it is
supposed to reconnect at logon. Access the drive hoping the red will
vanish. Sometimes it does you know. But sometimes it doesn't. Network
drive still unavailable. So I will disconnect and reconnect it. That
always works. Then I am back in business. For a bit.

This issue occurs over and over again. Is there a hotfix for an issue
such
as this or any other suggestion in Windows 2000.? I can tell it has
nothing
to do with my configuration but that it is because Network drive mapping
as
implemented by Microsoft seems to be a technology that has not gotten out
of
the Stoneage. Thanks.
Click to expand...
Click to expand...
 
Yes I undersstood that. But that won't help the apps on the server. They need to see the connection as a drive letter.
Without that it is sort of worthless. In other words Namespaces are no good.
 
I wonder if that might work....

--
George Hester
_________________________________
Lanwench said:
Phillip said:
Distributed File System (DFS) is a good way to cover for data
locations that change.
Click to expand...

Yes, I find DFS interesting - but I support small companies with a small
number of servers (often just one), and it just seems like overkill. I don't
have a problem with drive mappings in these situations, primitive though
they be. It is far easier for me to switch things around, and all the user
needs to know is "S is for Shared". Cheap, cheerful, and reliable. ;-)
"Lanwench [MVP - Exchange]"
Richard G. Harper wrote:
You are quite correct. Drive mapping is old-school. Applications
should be configured to use UNC paths instead. If you use UNC
instead of mappings do you have the same problems?

Respectfully disagree - UNC paths mean, whenever you move data, you
have to change the path the client points to. Drive
mapping/variables makes life easier.
Click to expand...
Click to expand...
Click to expand...
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;297684

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Not always but yes sometimes. Where is this setting AUTODISCONNECT set?

--
George Hester
_________________________________
Richard G. Harper said:
That's a tough one, wish I had a good solution. If drive letters are
necessary then mapping is also necessary. Have you tried setting the
AUTODISCONNECT setting on the server so that auto-disconnect is disabled?
Do you un-map then re-map the drive at logon?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Yes when I use Windows Explorer to Tools | Map Network Drive... the
connection is set to
\\MachineName\(drive)$ That is a UNC path is it not? This is where the
issue always occur. Of course I can set it up differently using New
Network
Connection (no issue here) but apps in the Server need to see the domain
controller's drives as drives not Namespaces.

--
George Hester
_________________________________
Richard G. Harper said:
You are quite correct. Drive mapping is old-school. Applications
should
be
configured to use UNC paths instead. If you use UNC instead of mappings
do
you have the same problems?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* In fond memory ... Alex, you shall be sorely missed
* http://www.aumha.org/alex.htm


Windiows 2000 Advanced Server SP3 Windows 2000 Server Client SP4.
I am having a dickens of a time trying to keep these Network drives
functional. They fail sporadically and the issue is NOT DNS. For
example.
Booted the Server and the mapped Network drive showed red although it is
supposed to reconnect at logon. Access the drive hoping the red will
vanish. Sometimes it does you know. But sometimes it doesn't. Network
drive still unavailable. So I will disconnect and reconnect it. That
always works. Then I am back in business. For a bit.

This issue occurs over and over again. Is there a hotfix for an issue
such
as this or any other suggestion in Windows 2000.? I can tell it has
nothing
to do with my configuration but that it is because Network drive mapping
as
implemented by Microsoft seems to be a technology that has not gotten
out
of
the Stoneage. Thanks.
Click to expand...
Click to expand...
 
Back
Top