Little help with drive mapping!!

[PieDerro]

Gday,

I'm having a problem setting up a network. I have to map a drive off the fileserver so that programs run from that drive at the client machines. The clients are Windows98 and can only be Win98 since I am dealing with a primary school.

Is there any way (in Windows registry, ini files etc) to FORCE the computer to attempt to connect to the network drive? It's just that if somebody logs in incorrectly, Windows98 lets them in, but the Fileserver (Linux based E-Smith) won't let them access it's drives, and a message comes up asking if you'd like to reconnect the drive at the next logon. Of course, the default "No" is selected, so immediately that someone gets their password wrong and logs in (Windows will log in irrespective of whether the password is right or wrong), they lose the network drive connection. Is there any way to FORCE the drive connection??

Thanks a stack people,

-PieDerro

 

[SoulAssassin]

How are your permissions setup on the server? Based on the fact that you're requiring them to use a password to connect to the server it seems like it wouldn't be an 'anything goes' situation and each user has specific permissions. Thus I can't imagine wanting to have a user not enter or enter an incorrect password and be able to access password restricted network resources. If that's the cause I would rely on user education.

If that's not the case then you could simply put a batch file in the startup folder with something like:

net use \\servername\share z:

 

[IsOs]

Does the fileserver requires login?
I use this command inside the autoexec.bat of Windows 98 to map a drive.
NET USE [devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]

example: NET USE Z: \\ALOHABOH\BOOTDRV Term1 /y

 

[RaySun2Be]

Are you running a peer to peer, NT Domain, or Win2K Domain?

We run an NT Domain, and require logon to that domain. Of course, our WIN95 clients will allow you to cancel the network logon and continue, but then they don't get their network drives. At which point, they will have to logoff, and log back in. If they have forgotten their password, they can call the help desk (or find me) and I can reset it.

For security reasons, under no circumstances do I allow them network drive access without logon authentication. If they can't remember their password, they know the procedure to reset it.

If they logon correctly, we have a nice server side login script that maps every network drive they need.

 

[PieDerro]

Thanks a stack guys!!!!

You guys make my life so much easier!!!

-PieDerro