Can't map
a remote computer's folders
Logon batch keeps asking for the password
Mapping problem -
persistent connection
Mapped Network Drives Disconnected at
Logon
Problem
with a red x on mapped drives
Some network drives
show with a red X
The local device name is already in use
Why some mapped
network drives show a red x
Why some mapped network drives show a red x
Can't map
a remote computer's folders
Causes: 1. Server service is disabled.
2. Fie and Printer Sharing is disabled.
3. No folders are shared.
4. Firewall blocks the sharing.
How to
map a network drive
without logon the domain
If you have a laptop used
at home and sometimes used in the office, you would like to map a
network drive without logon the domain, you can create a batch file like
that “net use h:
\\ervername\sharename password /user:domainname\username".
Logon batch keeps asking for the password
Symptom: I use logon batch to map
network drives when starting the computer. The problem is that it always
asks me for the password. How can I make that it remembers the
password?
Resolutions: 1. add the password into
the logon batch, for example, net use
\\computername\shaed
password.
2. If you are logging on a peer-to-peer workgroup, create the same user
account and password on remote computer.
The
local device name is already in use
Cause: the drive has a persistent
mapping or reconnect when logon.
For consultants, refer to case RL102504
Mapping problem - persistent connection
After you changed net use I:
\\serverA\shared
to
\\serverB\shared in your logon script, some windows 2000
machines are still mapping to \\serverA\shared. The reason is that
net use /persistent:yes is default settings for NT and win2000/XP.
You can disconnect the old mapping and re-logon. That will map to
\\cbgntB\shared.
Also you may want to use NET USE I: \\servername\folder /persistent:no
so that next time when we change the mapping, it will automatically map
to the new settings.
Problem
with a red x on mapped drives
Symptoms: 1. there three computers in
the peer to peer workgroup with a Multi-user version of Peachtree. Two
computers were just upgraded from ME to XP Home and third one runs ME.
After this upgrade, XP #2 shows a red x on the mapped XP #1 peachw
folder and can't run Peachtree unless you double-click red x marked
peachw drive to active it.
2. You may also experience saving issue too. Sometimes, when saving a
file to a network drive with red x, you may get an error which says
document not saved while is saving.
3. You may have browser issue when opening My Network Places and can't
see any or some computers. Or it takes long time to shows networking
computers in My Network Places.
4. Firewall and autodisconnect are not issues here because all firewall
and autodisconenct are disabled.
Resolution: 1. Make sure no
browser problem (Re:
Browser issues)
2. Create a logon batch file with non-persistent mapping.
3. You may want to turn Autodisconnect off on the server.
4. Still need help, contact consultant
blin@mvps.org at
http://www.ChicagoTech.net for the tech support.
Some
network drives show with a red 'X'
Symptoms:
you have mapped some network drives and checked the reconnect at logon,
or your network uses logon script to map network drives. After
rebooting, some network mapped drives may show with a red 'X'. If you
click on the drive, it becomes active.
Cause:
net use /persistent:yes is default settings for NT and win2000/XP.
This is why when you have mapped some network drives and check the
reconnect at logon, or your network uses logon script to map network
drives, the mapped network drives may show red Xs after rebooting. If
you enable echo and pause the logon script or if using net use to map
the same drive manually, you may get "System error 85 has occurred. The
local device name is already in use." One thing you may want to try to
avoid the red X is using net use /persistent:no, for example, net use i:
\\servername\folder /persistent:no.
Why
does net use default is persistent
If you disable autodisconnection and you are running
workgroup, you may be easily to hit the limit (10 connections for
workgroup). Even some computers are idled, but since you have disabled
the autodisconenction, they are still accounted 1 connection. This is a
why MS put the autodisconnect feature in.
Why some mapped network drives show a red x
SYMPTOMS: You find that the network drive
mapping may be disconnected after 15 minutes of inactivity and Windows
Explorer may display a red "X" on the icon of the mapped drive. However,
if you double-click it reconnects quickly.
RESOLUTION: by default, idle connections
will be dropped after 15 minutes. To modify idle time, at a command
prompt using net
config server /autodisconnect: minutes.
For example, to set
the Autodisconnect value to 30 minutes, you would run the following
command line: net config server /autodisconnect:30. If you
would like to turn Autodisconnect off, do net config server /autodisconnect:-1.
Logon batch keeps asking for the password
Sympton: I use logon batch to map
network drives when starting the computer. The problem is that it always
asks me for the password. How can I make that it remembers the
password?
Resolutions: 1. add the password into
the logon batch, for example, net use
\\computername\shaed
password.
2. If you are logging on a peer-to-peer workgroup, create the same user
account and password on remote computer. |