I
iaminlondon
For those who might ever come across this:
You have a computer on a network that has mapped drives from a server.
It all works across reboots. One day, though, it stops working, i.e.
you can see the drives showing up in Windows Explorer, but whenever you
click on them, you get an error:
An error occurred while reconnecting X: to \\YourServer\yourfolder
Microsoft Windows Network: Element not found.
This connection has not been restored.
You rush to the Event Viewer and find no mention of it. If you have
access to the server's Event Viewer you won't find anything relevant
there either. Maybe an Anonimous Logon- Event 538? But in a busy
network it wouldn't have helped much.
Then you go to google. You are certain someone must have come accross
this before. You try your best, but apart from getting listings of
Windows errors in a number of pages, nothing specific. Might get
luckier next time. Will keep it in Google Alerts for a few days, see if
something turns up. But as the days go by, nothing, nada, res de res.
Maybe it's a problem everyone sorts out without much fuss because it's
obvious? Maybe. For those few (any?) that might bang their heads
against a wall because of this, here is the reason for the message in
this particular instance and the solution.
The problem is that the drives where mapped with an account that has
changed password since the time the drives where mapped. And whoever
set up those drives told Windows to remember the password. Now, when
the password changes, all you get from (expletives deleted) Windows is
that "element not found" error. The solution is very simple once you
know the problem. Just remap one of the drives (or a new one). In the
dialog that comes up you will have an option to "Connect using a
different user name". Click on that and write the correct name and
password of the account used to allow the mappings. Voila. Everything
is back to normal. Further reboots won't have the system complaining.
One more thing. This wouldn't have happened to me if I hadn't logged on
as a local administrator to sort a few issues and had the drives mapped
in the first place. Logging as a user of the domain didn't show any
problems and in that instance the mapped drives worked like a charm.
Hope this helps someone else.
/J
PS: If anyone feels grateful donate to the PDFCreator project at
sourceforge. If nothing else, try Firefox
You have a computer on a network that has mapped drives from a server.
It all works across reboots. One day, though, it stops working, i.e.
you can see the drives showing up in Windows Explorer, but whenever you
click on them, you get an error:
An error occurred while reconnecting X: to \\YourServer\yourfolder
Microsoft Windows Network: Element not found.
This connection has not been restored.
You rush to the Event Viewer and find no mention of it. If you have
access to the server's Event Viewer you won't find anything relevant
there either. Maybe an Anonimous Logon- Event 538? But in a busy
network it wouldn't have helped much.
Then you go to google. You are certain someone must have come accross
this before. You try your best, but apart from getting listings of
Windows errors in a number of pages, nothing specific. Might get
luckier next time. Will keep it in Google Alerts for a few days, see if
something turns up. But as the days go by, nothing, nada, res de res.
Maybe it's a problem everyone sorts out without much fuss because it's
obvious? Maybe. For those few (any?) that might bang their heads
against a wall because of this, here is the reason for the message in
this particular instance and the solution.
The problem is that the drives where mapped with an account that has
changed password since the time the drives where mapped. And whoever
set up those drives told Windows to remember the password. Now, when
the password changes, all you get from (expletives deleted) Windows is
that "element not found" error. The solution is very simple once you
know the problem. Just remap one of the drives (or a new one). In the
dialog that comes up you will have an option to "Connect using a
different user name". Click on that and write the correct name and
password of the account used to allow the mappings. Voila. Everything
is back to normal. Further reboots won't have the system complaining.
One more thing. This wouldn't have happened to me if I hadn't logged on
as a local administrator to sort a few issues and had the drives mapped
in the first place. Logging as a user of the domain didn't show any
problems and in that instance the mapped drives worked like a charm.
Hope this helps someone else.
/J
PS: If anyone feels grateful donate to the PDFCreator project at
sourceforge. If nothing else, try Firefox
