Click to See Complete Forum and Search --> : Necesito ayuda, Por favor


DJ Flipper
July 29th, 2005, 11:00 AM
Saludos a todos.

Para el que pueda ayudar.
Tengo instalado Windows XP en la PC y en el servidor Windows 2000 Advanced Server. Cuando voy a conectar una unidad de red en el servidor no me da acceso y me da el siguiente error: "Error mientras se volvía a conectar a F: Red de Microsoft Windows: Ya se está utilizando el nombre del dispositivo local"

No importa que letra quiera asignarle desde la opción de Conectar a unidad de red del Explorador no trabaja. De la única forma que lo logro es entrando por Mis sitios de red, buscar la carpeta compartida en el servidor y desde ahí conectar a unidad de red, con una contraseña de administrador de dominio. Con un usuario cualquiera me dice que ya ese usuario esta conectado.

Que hago?

Please excuse my poor translation.

Rich

(Greetings to all.

To whomever can help. I have installed Windows XP in the PC and in the servant(client?) Windows 2000 Advanced Server. When I am going to connect a unit of network in the servant(client?) it does not give me access and I get the following error: "Error while was connected again to F: Network of Microsoft Windows: Already is being utilized the name of the local device"

It does not it matter that letter wants to assign it since the option to Connect to unit of network of the Explorer does not work. Of the only form that it achievement is entering for My places of network, to seek the folder shared in the servant(client?) and since there connect to unit of network, with a control administrator password. With a user any tells me that already that user this connected.

What should I do? )

XII
July 29th, 2005, 01:31 PM
Disconnect all network drives and then click on map network drive, select F (if it is available) and then put in the path as \\servername\share. I have seen this happen where for some reason, a system was unable to connect to a given drive letter because of some other problem but it caused all of them to stop working correctly. The way to fix it was to disconnect all network drives and re-map them.

Good luck... might help.