"The network name cannot be found" + An error occurred while recon

  • Thread starter Thread starter Steve Behman
  • Start date Start date
S

Steve Behman

Out of the blue,when I attempt to open a Network Drive (that used to 'work')
I started getting a seemingly random occurrence of one of the two dialogs
below.

============== Dialog 1 ===========================

An error occurred while reconnecting D:\ to \\computer_name\share_name



Microsoft Windows network: The network name cannot be found.

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


================== Dialog 2 =================
An error occurred while reconnecting D: to \\computer_name\share_name.

Microsoft Windows Network: Not enough server storage is available to process
this command.

This connection has not been restored.
==========================================


Does anyone have an idea about what's going on?
 
-------- Original-Nachricht --------
Out of the blue,when I attempt to open a Network Drive (that used to 'work')
I started getting a seemingly random occurrence of one of the two dialogs
below.

============== Dialog 1 ===========================

An error occurred while reconnecting D:\ to \\computer_name\share_name



Microsoft Windows network: The network name cannot be found.

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


================== Dialog 2 =================
An error occurred while reconnecting D: to \\computer_name\share_name.

Microsoft Windows Network: Not enough server storage is available to process
this command.

This connection has not been restored.
==========================================


Does anyone have an idea about what's going on?
Click to expand...
Look here (Norton SW ?):

http://groups.google.com/group/micr...read/thread/2d80348c3c743a65/836dd66b3631cc5e

Bernd
 
Bernd, thank you very much for your response. Although it did not directly
solve my problem it started me off on a path that did!

I ended up at "PChuck's Network Blog". This is the second time that this
blog helped me solve a very sticky network problem -- its value cannot be
overestimated! Hereafter, when I encounter a networking problem, it is the
first place I will look.

The genesis of my problem remains (to me) very mysterious. I say this
because the fix (involving adding a parameter in the registry) had to be
applied to my wife's machine -- a machine which she uses ONLY for web
browsing, Microsoft Word and a checkwriting program which I, myself, wrote.
That is to say, NOTHING that affects the XP O/S in any way shape or form! On
Monday there was no problem and on Tuesday it was there.

I have been computing for 60+ years and have never before encountered
something like this, oh well...

Again thanks
 
-------- Original-Nachricht --------
Bernd, thank you very much for your response. Although it did not directly
solve my problem it started me off on a path that did!

I ended up at "PChuck's Network Blog". This is the second time that this
blog helped me solve a very sticky network problem -- its value cannot be
overestimated! Hereafter, when I encounter a networking problem, it is the
first place I will look.

The genesis of my problem remains (to me) very mysterious. I say this
because the fix (involving adding a parameter in the registry) had to be
applied to my wife's machine -- a machine which she uses ONLY for web
browsing, Microsoft Word and a checkwriting program which I, myself, wrote.
That is to say, NOTHING that affects the XP O/S in any way shape or form! On
Monday there was no problem and on Tuesday it was there.

I have been computing for 60+ years and have never before encountered
something like this, oh well...

Again thanks
Click to expand...
Thank you for the feedback !

Bernd
 
Back
Top