Topic: An error occurred while reconnecting Z: to

[noaptus]

Hi.

I am having a problem with share folders on my server. V9

This is the error I have.

An error occurred while reconnecting Z: to
\\SERVERNAME\keining3
Microsoft Windows Network: The local device name is already in use.

This connection has not been restored.

Can some one explain why this is happening. I'ts like the mapped hdd is loosing the connection.

Best regards.

[Daniel B.]

As the message explains: you already have a Z: drive pointing on something else

[Stefano]

moving to General Discussion as not striclty SME related

[noaptus]

Thanks for the reply.

But it doesn't matter what letter I use to drive pointing. I have used it all and I have tried all.


And it's all the same.

[Stefano]

ok.. time for you to give us as much details as you can about your setup and about your issue..

please be verbose

[janet]

noaptus

Windows network connections are usually persistent (once initially established).
You need to disconnect them in order to use them again with a different drive letter mapping.
Google
net use .....
& google for
persistence
to get the answers you (probably) need.

edit:

The Z drive letter is typically by default used for users Home folders.
You can (typically) change that to H if preferred

eg in a login.bat file you might have something like

net use /delete M: /yes
net use /delete N: /yes
net use /delete X: /yes

net use M: \\servername1\sharename-m
net use N: \\servername1\sharename-u
net use X: \\servername2\sharename-x

net use H: /home
net use /delete Z: /yes

[Jáder]

you can use something like this:

 net use * /del /y

as first command before mappings.
This will delete all mappings before start mappings.
There are another command to change letter for home drive. I personally use P: (name after PERSONAL STUFF).
search command on wiki, its something like "db configuration setprop homedir p:"

[josehart]

As the message explains: you already have a Z: drive pointing on something else

Dude i would recommend you to check the Error Log carefully . I faced the same problem but then i downloaded the Event Log Explorer and i found that my printer was the problem. You can check it at http://eventlogxp.com/event-log-admin.html

[Stefano]

josehart: your post seems just promotion of a windows' software.. can you please clarify? thank you