mapped drives disconnected at boot on workstations

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

We loaded Windows 2000 server advanced last night and are just still using
the workgroup. We loaded server with 15 cals to bypass 10 connection issue.
We did not setup a domain and are still using the workgroup. Everything
seems to be working; but the mapped drives are disconnected at boot. Once
the drive is clicked on and password is entered. The problem is gone. I
know I am just missing something. Any help would be appreciated. We will be
setting up the domain; but this is for a tax office and limited on downtime.
The workstations are running Windows Xp Home.

Thanks,

Sandra
 
trsshh said:
Hi,

We loaded Windows 2000 server advanced last night and are just still using
the workgroup. We loaded server with 15 cals to bypass 10 connection issue.
We did not setup a domain and are still using the workgroup. Everything
seems to be working; but the mapped drives are disconnected at boot. Once
the drive is clicked on and password is entered. The problem is gone. I
know I am just missing something. Any help would be appreciated. We will be
setting up the domain; but this is for a tax office and limited on downtime.
The workstations are running Windows Xp Home.

Thanks,

Sandra
Click to expand...

With 15 workstations you should use a centralised logon script.
Create a batch file called "netlogon.bat" and save it on the server
in the "\\server\netlogon" share. Its lines could look like so:

@echo off
net use S: \\Server\SomeShare
net use P: \\Server\%UserName%

Since you operate in a workgroup environment, you must invoke
this batch file like so: Place the following batch file into the
"All Users\Startup" folder of each and every workstation.

@echo off
call \\Server\netlogon\netlogon.bat
 
That is kinda of what I thought I would have to do and that makes since, the
only thing I am confused on it where to save the netlogon.bat on the server.
Do I need to use the net command to save this to the server\netlogon share.

Thanks,

Sandra
 
Maybe I am making this more complicated than it needs to be. So let me break
what we have down.

I have Windows XP workstations and a server running Windows 2000 Server.
They are on a workgroup. The drivers are mapped under my computer and show
up as disconnected drives. Once you click on them and use the administrator
password they work. Until Windows 2000 server was loaded they worked well
with the 10 workstation limit. The units are running Windows xp home
edition. The netlogon service does not start on windows 2000 server because
i am using the workgroup. I kinda of understand creating the batch file; but
not necessarily on the server. The workstations boot to the desktop of
Windows xp home edition.

My share names are routed to drive P and Q.

The folders are under the c drive on the server.

I am now throughly confused.

I am sorry,

Sandra
 
Your problem arises because you're mixing a few issues that are
not related to each other.

Your drives show as "disconnected" because they are remembered
from a previous session. You don't need this "persistency", because
you now map the drives with a logon script. Modify your server script
like so to get rid of it:

@echo off
net use * /del /yes
net use /persistent:no
net use P: \\Server\SomeShare
net use Q: \\Server\%UserName%

The need to enter passwords arises because the server treats
you as a "stranger" when you log on to your workstation. Make
yourself known to the server by creating an account+password
on the server that is identical to the workstation account+password.

The netlogon service with start by itself when needed.

You need the script on the workstation to invoke the centralised
server-based logon script.

You need the script on the server in order to map your shares.

Both the account issue and the centralised scripting issued
would be much simpler if you moved from a workgroup-based
model to a domain-based model!
 
I think the key there is when he said "as soon as they click them and enter
the password" - Sounds like he doesn't have the user accounts set up for
pass-thru authentication. Users are having to authenticate each time they
connect.

....kurt
 
thanks for the help, we will be moving to a domain; but as I said before, my
time for working is limited this is for a tax office and this is the height
of tax season, In June, I will be able to implement a domain, This was only
done because of the connect issue, the office is open and moving about 12-16
hours a day. For them time right now is money.

sandra
 
Back
Top