Re: map network drive - password error - logistics


"Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%2363MGipeGHA.3572@xxxxxxxxxxxxxxxxxxxxxxx
"Why would this be? Isn't a little cumbersome to only be able to map to
folders ON a
server rather than just the "root" of the server?"

Drives are concerned with data storage - if you mapped drive X: to a server
instead of a share and you saved data to drive X: ................... where
would it go?

***
Mapped network drive X: is to data storage as hard drive C: is. IOW, if you save to C:,
it goes to the root directory. Do servers have a "root directory"?


If you want to map a drive to the 'root' of a server, share
the entire C: drive - \\Server\C.

***
I would think the above nomenclature would point to a FOLDER named C, not a whole drive.



"IIRC, both "B" (win 2000) and "C" (XP pro laptop) have the same username
and password for
BOTH machines. Yet, we always get denied on the pw screen.

Does machine "B" have to do anything special to allow "C" to see him from a
MANUAL
security or SHARING options standpoint?"

- No, provided the default settings are in effect.

Try:

On the Win2k machine, go to Administrative Tools/Local Security Policy -
Expand local Policies and click on User Rights Assignment. Double click on
Access this computer from the network - add the user account even if
Everyone is already listed. Make sure no users or groups are listed in Deny
access from the network.

***
Can you list or provide a reference for all the commands/utilities that can used at each
workstation/laptop to more fully understand what's going on?



Add the user to the permissions on the Share even if Everyone is already
listed.

Check firewalls and/or any other third party security software. This kind
of software can easily block file and printer sharing and usually does so by
default.

Troubleshooting the XP machine varies depending on whether SFS is enabled:

http://support.microsoft.com/kb/304040/en-us

"What do you mean "you could use" the above? In what context?"

Start/Run \\RemoteComputerName /user:RemoteComputerName\RemoteUserAccount
ENTER

Or - net use X: \\RemoteComputerName\ShareName
/user:RemoteComputerName\RemoteUserAccount


***
What do the above 2 commands SPECIFICALLY DO?

JL


Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Jim Lewandowski" <jlewand@xxxxxxxxxxxxxxxxxxx> wrote in message
news:ZI%ag.9988$fb2.6611@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

"Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:OHl3GlgeGHA.4532@xxxxxxxxxxxxxxxxxxxxxxx
I don't understand the last 4 questions, but the answers to the first 2
are:

1. No. You cannot map a drive to a server; you can only map to a
share.
If you want to 'see' all the shared resources on a server, click
Start/Run
\\ServerName ENTER, or create a shortcut that points to \\ServerName,
or
use My Network Places.

***
Why would this be? Isn't a little cumbersome to only be able to map to
folders ON a
server rather than just the "root" of the server?



2. With classic file sharing (Windows 2000), when you connect to a
remote
computer in a workgroup environment, you must provide credentials which
can
be authenticated on the remote machine. By default the machine you are
connecting from provides the user name and password used to log onto
that
machine. Unless the remote machine has a matching account and that
account
has permission to access the shared resource, access will be denied.

***
IIRC, both "B" (win 2000) and "C" (XP pro laptop) have the same username
and password for
BOTH machines. Yet, we always get denied on the pw screen.

Does machine "B" have to do anything special to allow "C" to see him from
a MANUAL
security or SHARING options standpoint?


The
conventional way to deal with this is to add a user account on the
remote
machine which has the same user name and password as the user name and
password used to log onto the machine you are connecting from. You do
not
need to log onto the remote machine with this account, just create it.
Instead you could use:

\\RemoteComputerName /user:RemoteComputerName\RemoteUserAccount

***
What do you mean "you could use" the above? In what context?



When connecting to an XP machine this may not be an issue because XP
supports something called Simple File Sharing which allows remote users
to
authenticate as guests. This may or may not be enabled on your XP Pro
machine.

***
I'm aware of guest accounts but without knowing HOW this works, it doesn't
help.

JL


Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Jim Lewandowski" <jlewand@xxxxxxxxxxxxxxxxxxx> wrote in message
news:8nNag.28612$4L1.3720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This is my first real exposure troubleshooting anything related to
mapping
of network
drives and/or folders so PLEASE be complete in your answer.

Small business

"A" Win 2000 PC (desktop)
"B" Win 2000 PC (desktop)
"C" Win XP Pro PC (laptop)


Why can't you map a WHOLE server rather than having to map only the
FOLDERS. For example,
on PC "A", when in Windows Explorer, if you double-click on a network
drive/resource, in
the "title/address" bar, it will say something like \\server\folderA.
I
can overtype and
delete the "folderA" part and I WILL then get a list of ALL the folders
under \\server.
Is there anyway to map the whole shebang?


From "C" (XP Pro) laptop, whenever we try to map any network resource
(like trying to map
the "A" desktop PC), a user/password window pops up that no matter what
user/pw we enter,
it just poops right back up.

Example:

userid: joe.lastname
password: joepassword

When popup window comes BACK, it will have:

userid: joelaptop.joe.lastname (joelaptop has been appended to the
front)
password: *******

When one is entering a password here, is it the userid/password for the
LAPTOP ("C") or is
it for the DESTINATION of what we're trying to map FROM laptop ("C")?

I've seen references to doing some net use command but, as usual,
incomplete information
explaining EXACTLY WHAT are we accomplishing with said command. Is
there
some "caching"
problem here that the net use is used to rectify?

What are the rules for user/password with respect to who can talk to
what
network PCs,
etc? Naming conventions.

Are there options that allow one PC to "see" another PC as a "network
place"? IOW, a
sharing specification from one PC that by default doesn't allow ALL PCs
to
see his data?

JL










.

Relevant Pages

  • Re: Vista drive mapping to 2008 Server
    ... The chimney offload was disabled on both client and server and I have reset ... Now I can map a drive using the command Prompt and access it via that method ... It sounds like something in the network infrastructure may not be working ... connect or map drives. ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: Vista drive mapping to 2008 Server
    ... It sounds like something in the network infrastructure may not be working with some of these features. ... Try each setting both on the server alone, a client alone, then both. ... After doing this map a drive by any method then see if it loses the ... > No logon script used in this instance and it maps drives not used by> any ...
    (microsoft.public.windows.vista.networking_sharing)
  • The list of servers for this workgroup is not currently availiable
    ... I already had all pcs mapped to either server w/ ... Now I can't create any new mapped drives from either office. ... are mapped and you can map a drive to the remote office just fine ... office......when browsing for a folder the remote office server will ...
    (microsoft.public.windows.server.sbs)
  • Re: Mapping drives from client TO the server
    ... where you can map a drive. ... mapping" for RDP and the drives on the client will show in Explorer as ... > However, what I'm really asking is, can I map to a drive on the SERVER ... >> map drives in the RDP Session to the client computer. ...
    (microsoft.public.windows.terminal_services)
  • Re: Win98 and lunux samba server
    ... >I have a problem when I try to log in from a Win 98 system to a samba ... >If I log is as Root I can Map the drive's on the samba server ... >That I made on the server, I try to map the drives and I get a message ...
    (comp.protocols.smb)
Loading