Rights to share directory

[Guest]

I have a problem getting some users to a shared driver on a server. We have two servers, both running Windows 2000 Server, Version 5, Build 2195, SP4. Both servers have a shared folder, both shared folders are shared with the group Everyone, all the permissions are the same. Everyone can get to the shared on Server A, but only some users can get to the share on Server B. It appears that the users who CAN access the share on Server B are running XP on their local machine, while those who can't get to the share on Server B are on Windows 98. However, since drive mappings to these shares are set to run from a login script, I tried logging in on an XP machine as a user who CANNOT access Share B , but the map to Share B still didn't connect her to that drive, so it really does not appear to be an XP/98 issue. Any ideas?

 

[Ricardo M. Urbano - W2K/NT4 MVP]

I have a problem getting some users to a shared driver on a server. We have two servers, both running Windows 2000 Server, Version 5, Build 2195, SP4. Both servers have a shared folder, both shared folders are shared with the group Everyone, all the permissions are the same. Everyone can get to the shared on Server A, but only some users can get to the share on Server B. It appears that the users who CAN access the share on Server B are running XP on their local machine, while those who can't get to the share on Server B are on Windows 98. However, since drive mappings to these shares are set to run from a login script, I tried logging in on an XP machine as a user who CANNOT access Share B , but the map to Share B still didn't connect her to that drive, so it really does not appear to be an XP/98 issue. Any ideas?

It's probably a rights issue on server B. I'm wondering if you have the
local guest account enabled on server A (BAD!!). Do you have a domain?

What happens when they try to connect to B? What is the message, if
any?

 

[moonchildokc]

Well, using the login script, if it gives an error, it
goes by so fast I can't see it.

If I try to map a drive manually, I get the error message:
The computer or sharename cannot be found.

If I click Start, Run, and type the unc path to that
share, I get the following message: The network name
cannot be found.

 

[Ricardo M. Urbano - W2K/NT4 MVP]

Well, using the login script, if it gives an error, it
goes by so fast I can't see it.

If I try to map a drive manually, I get the error message:
The computer or sharename cannot be found.

If I click Start, Run, and type the unc path to that
share, I get the following message: The network name
cannot be found.

Well, that sounds like a name resolution problem (the machine cannot
translate the machine name to an IP address), or maybe the sharename is
too long for the workstation. 9x machines cannot access sharenames that
are longer than 15 characters in length.

To r/o name resolution, try to use the server's IP address in the UNC
path.

 

[Darla Hughes]

Well, you are absolutely right. If I use the IP address, it works. Thanks,
man! You rock!

 

[Darla Hughes]

Well, Ricardo, I thought we had this one, but it is still elusive! I
changed the login script to the following:

@ECHO ON

REM If RAS passed as parm, skip commands to not be processed if dialing in
IF _%1 == _RAS GOTO start_if_ras
IF _%1 == _ras GOTO start_if_ras
IF _%2 == _RAS GOTO start_if_ras
IF _%2 == _ras GOTO start_if_ras
IF _%3 == _RAS GOTO start_if_ras
IF _%3 == _ras GOTO start_if_ras

NET TIME %LOGONSERVER% /SET /YES

:start_if_ras
NET USE L: /d 1>nul 2>nul
NET USE V: \\servera\src
NET USE W: \\serverb's ipaddress\src

Yesterday it worked great, but today when we log in, it's not connecting to
server B again. I can ping the server by IP address OR by share name, and
get a reply, but I can't connect to it. This is getting really
frustrating!!!

 

[Darla Hughes]

One more note...I logged in with the same user's credentials on a Windows XP
machine, and the drive mapping worked. I'm thinking now it has something to
do (maybe) with the Pre-2000 account, but I gave that account full rights on
the domain controller (Start, Programs, Administrative Tools, DNS, forward
lookup zones, server name, properties), but it still doesn't work on a 98
machine.

 

[Ricardo M. Urbano - W2K/NT4 MVP]

One more note...I logged in with the same user's credentials on a Windows XP
machine, and the drive mapping worked. I'm thinking now it has something to
do (maybe) with the Pre-2000 account, but I gave that account full rights on
the domain controller (Start, Programs, Administrative Tools, DNS, forward
lookup zones, server name, properties), but it still doesn't work on a 98
machine.

Darla, pls keep in mind that messages, error or otherwise, greatly help
the troubleshooting process. Also, some us, like myself, can only get
around to the NG's like once a day, so this would vastly shorten how
quickly we can help you. W/o any message, I really can't say why this
is happening.

You may want to try 'net use /d' for each drive letter before mapping
it. I also do a subst /d just to be thorough. Also, you may want to
use the /persistent:no switch in the drive mappings, but I'm not sure if
that is supported on 9x

It could be failing because w: already exists when it tries to map it.

 

[Matt Hickman]

:start_if_ras

NET USE L: /d 1>nul 2>nul
NET USE V: \\servera\src
NET USE W: \\serverb's ipaddress\src

Yesterday it worked great, but today when we log in, it's not connecting to
server B again. I can ping the server by IP address OR by share name, and
get a reply, but I can't connect to it. This is getting really
frustrating!!!

Have you tried

net use w: /d
or
net use \\serverb's ipaddress /d
prior to
NET USE W: \\serverb's ipaddress\src

This would clear out things if there is a duplicate drive letter or
credentials conflict.

When you run the command from a command prompt, does it give you an
error? Anything in the security event log of either the client or
serverb?

 

[Darla Hughes]

Guys, I really appreciate your suggestions. The error message I get are in
earlier posts in this thread. However, I'm giving up on this. There is no
conflict with the drive letter I'm using. I logged onto XP with the same
user credentials, and it's works fine, so it's gotta be something to do with
XP versus 98. The user I'm trying to get connected is a web developer, so I
just installed Remote Desktop and she is logging directly into the server
with the administrator password. This is not something we'd do for most
users, but in her case, we feel safe since the box she is accessing is our
web development box anyway.

Thanks again for your suggestions.