General discussion

Locked

Logging on to W2K server w/ W98 station

By jneag ·
I'm in a learning process here, so I might have questions pop up from answers.

First of all, I admin a small (120+) NT4 network, so I'm used to doing things the NT4 way. We just recently purchased 3 W2K servers. These servers are going to act as file servers, nothing special. I'm needing to know how and here to put a logon script so a W98 station can log on to a W2K server.

With NT4 you could put a .bat file into the WINNT\system32\repl\import\script path and each station assigned to the server would run the script when logging on. With W2K this doesn't seem to be the way.

My problem is that this path does not exist on a W2K server. How would one do this with W2K? Can you still do it this way?

This conversation is currently closed to new comments.

18 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

No need

by LordInfidel In reply to Logging on to W2K server ...

Simply join the 2k servers to the NT4 domain.

2K srvs in an NT4 domain do not do any authentication. Logon scripts are not used in 2K AD. Which is why there is no path.

But you are not using AD, and again, a 2K srvr does not do any logon verification (except for the normal creditianal verification when accessing resources. But it will not authenticate any logons to the domain. 2K can not be a domain controller in NT4.

2K can play just fine with NT4 domains when they are file and print servers or any other type of server, just not a domain controller.

So in short, join the 2K srvr to the domain as though you were joing any other server to the domain that is not a domain controller.

Collapse -

by jneag In reply to No need

OK, this is what I've done.

Further explaination:
The logon script that I need these W98 stations to run maps a drive to these file server. Without manually mapping (which I consider unreliable), is there a way to map a drive in W98 to a W2K server?

Collapse -

No differernent then any other

by LordInfidel In reply to

in your logon script that is located on your NT4 PDC's/BDC

specifiy the net use (drv ltr) \\servername\share

As long as the 2K srvr is joined to the domain, and the appropiate ACL's assigned to the folders. Then your users should not have a problem.

(errata- never control access with share permissions, share permissions should always be everyone/full. Always use NTFS permissions to control access)

Again 2K srvr is no different then NT4 srvr in this respect.

Collapse -

by jneag In reply to No differernent then any ...

Here are the contents of the logon script on the PDC:
net use h: \\___L-NT4\Apps
net use j: \\___L-NT4\Pri_ebs
net use k: \\___L-NT4\Disc_win
net use l: \\___L-NT4\Mas_ebs
net use m: \\___L-NT4\Sirscd1
net use n: \\___L-NT4\Sirscd2
net use o:\\___L-NT4\Sirsgov
net use p: \\___L-NT4\Sirsren

The contents on the BDC's are the same, except for the ___ portion is replaced with a 3-digit location number. For example, location 001's server is named 001L-NT4.

Would it be possible to change the ___ portion of the script with a variable, %servername% maybe? Or is that not going to work?

Collapse -

Just add the 2k server name

by LordInfidel In reply to

Your on the right track....

If your 2K server is called 001L-2K then add an entry to the logon script the same way you have it now.

There is no magic here.

Let's say that the location of \\___L-NT4\Sirsren has changed to \\___L-2K\Sirsren

Then just change it in your *current* login script.

I'm not really sure where your confusion is coming from with this is.

Just don't think of the 2K srvr as authenticating logins and think of it as just another server in the domain. The login script contains commands for what you want the client machines to do when they (the user) logs in to the domain.

If you want them to synch their time, then put it in the login script; if you want them to map a drive to server xyz, then put that in the login script.

You seem to have a grasp of what how to use the net use command and how you want it to work. I'm not sure where the idea came about that you needed login scripts on the 2K server in order for clients to map a drive to them.

As long as there is a share on the 2K server for them to map to, just edit your login script with the info you already have.

Collapse -

by jneag In reply to Just add the 2k server na ...

"I'm not really sure where your confusion is coming from with this is.

Just don't think of the 2K srvr as authenticating logins and think of it as just another server in the domain."

It's probably coming from the fact that the stations do notauthenticate off of the PDC, but the BDC's at their locations. This WAN is spread out over a city of 600,000. (Ft Worth TX, ever heard of it?) I don't know why it was setup this way, length of time for connection I guess.

Collapse -

by jneag In reply to No differernent then any ...

Let's try posting this again.

Here are the contents of the logon script on the PDC:
net use h: \\___L-NT4\Apps
net use j: \\___L-NT4\Pri_ebs
net use k: \\___L-NT4\Disc_win
net use l: \\___L-NT4\Mas_ebs
net use m: \\___L-NT4\Sirscd1
net use n: \\___L-NT4\Sirscd2
net use o: \\___L-NT4\Sirsgov
net use p: \\___L-NT4\Sirsren

The contents of the logon script on the BDC's are the same, excluding the ___ portion. The ___ is replaced with a 3-digit location number. For example, location 001's server is named 001L-NT4.

Could the ___ portion of the script on the PDC be modified with a variable that tells the workstation to map it's drives to correspond with its location?

Collapse -

by jneag In reply to No need

Hmm... My comments aren't posting for some reason.

This is what I've already done. The W2K server has joined the domain and that's great.

Further explaination:
These W98 machines map a drive to these W2K servers. Without manually mapping a drive (which I consider unreliable), how would you map a drive when logging on? Is this able to be done?

Collapse -

It is possible..

by btrue In reply to

You can still create the .bat file with your login script. You just need to put it in the winnt\sysvol\sysvol\DOMAIN\scripts folder. Make sure the folder is shared with read rights to everyone that needs to see it. You then have to point towards the file in each users profile. In AD go to the user properties and then click on the profile tab and you will see "Login Script". Just type the name of your whatever.bat in there and you should be good to go!

Collapse -

by jneag In reply to It is possible..

What happens when the path isn't there? Seriously, it's not even there. Hidden files are shown and system files are not protected.

Should I create the path?

Back to IT Employment Forum
18 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums