W95 accessing W2K & AD

[DazzaC]

Hi there, I am experiencing problems with W95 client machines accessing a new AD structure I have just implemented within my business.
I am aware that windows 95 machines are not compliant with W2K GPO but was wondering if anyone had any experience of joining and getting w95 client machines to connect to a domain and the directory structure based on a KixScript.
I was thinking it may be possible by specifying the login script from the user profile tab, then login script and in here pointing the profile at a specific KixScript?
Thanks

 

[karlisi]

Win9x computers can use AD resources, for example they can use share access and logon validation for domain users. If there is AD client installed, you can search for printers or people in active directory.
Win9x computers cannot browse AD like win2000 or winxp even with AD client installed.

===
Karlis
ECDL; MCP

 

[DazzaC]

Do you need to install and AD Client on the W95 machine? Is that what you are suggesting?
How else could I map to the resources on the W2K server when the user logs in??

 

[dearingkr]

Kixstart has a client agent that needs to be installed on win95/98 machines in order for the logon scripts to work.

MCSE CCNA CCDA

 

[DazzaC]

Do you know where this client can be obtained from?

I have been searching for a resolution for this problem for weeks now, if you can give me any guidance it would be much appreciated.

Many thanks

 

[dearingkr]

You will need to load a couple DLLs

Go to:

http://www.kixstart.org

It has everything you'll need.

The manual is at:

http://www.kixstart.org/bin/KIX2001.doc

MCSE CCNA CCDA

 

[DazzaC]

Hi thanks for getting back to me so quick.

I have visited this site and have downloaded both the manual and software, but I am having problems connecting the win95 clients to the w2k resource.

In the AD for the user profile->login script I have specified that the script exists in a folder on the domain controller.

The client machine will not process these scripts.

Of the *.exe's and *.dll's that come with the download what if anything needs to be installed on the client machine and where do the files need to be installed to?

Apologies for this, I have taken this project on from a guy who has just left and I have never used Kix I usually work in Novell.

Thanks

 

[dearingkr]

Required files for Windows 9x Clients
Windows 9x clients must install both Kix32.exe and two dynamic-link libraries (DLLs) called KX16.DLL and KX32.DLL.

If Windows 9x clients are to communicate with the KiXtart RPC service, an additional DLL, called KX95.DLL, should also be installed. Please see the separate paragraph on the KiXtart RPC service for full details.

Note
KX95.DLL should only be installed if the KiXtart RPC service will be used. Without the KiXtart RPC service, KX95.DLL will generate unnecessary network traffic and delay the start of KiXtart.


MCSE CCNA CCDA

 

[DazzaC]

I have managed to obtain these files from the Kixtart website.

Where do i need to install the *.exe and the two *.dlls?

Do they go into the system folder within the windows directory?

Do I need to use the *.scr or the *.kix file extension for 95 clients?

Can I specify on the user profile within AD the location of the script i.e. \\domaincontroller\c$\script\kix.exe w95script.scr? Or use a local path on the client?

Thanks again for your time

 

[dearingkr]

It's been a while since I've played with it, so you may have to experiment.

Create a folder: C:\KixtartPut Kix32.exe & DLLs in there.

Add the following to the autoexec.bat:
C:\Kixtart\Kix32.exe


MCSE CCNA CCDA

 

[crobin1]

Slight correction, you do not HAVE to install any files on the client. I have been using KiXtart for a couple of years now with clients from Windows 95 through Windows XP with no problems.

In the most basic setup, the following files need to be in the Scripts folder of a domain controller (physical path: C:\WINDOWS\SYSVOL\sysvol\<domainname>\scripts)
KIX32.EXE
KX16.DLL
KX32.DLL
KiXtart script file (something.kix)
Batch file to call KiXtart file (something.bat)

Your batch file (say start.bat) will have a line in it like this:

%0\..\kix32.exe start.kix

Your KiXtart script (start.kix) could have some lines like this:

; For everyone
use f: "\\server1\share1"

;For Accounting
If INGROUP("ACCTG")
    use k: "\\server1\share2"
Endif

In the user's profile in Active Directory, set the logon script on the Profile tab to start.bat and you should be good to go.

There are other things you can do (explained more in the documentation and on the Web site) by installing some of the files on the client, but it is not necessary.

If this doesn't help, please report any specific problems or error messages that you are getting.

 

[DazzaC]

Crobin, many thanks for your comments.

I have tried what you suggested. Here is where I am at.

I have configured the client machine to join the company domain.

In network neighbourhood, identification, workgroup I have added the domain I want to join.

In Microsofto Networking I have ticked the option join domain and have specifed the domain.

I have also configured the DNS settings.

In the Active Directory, on the Policy I have a default policy. When I go to the logon / logoff and browse to the folder containing the script and the Kix files I have the following files:

KIX32.EXE, KX16.DLL, KX32.DLL, KX95.DLL the batch file (that calls the script) and the Kix files (the script).

On the user profile, in the login script I have entered the name of the batch file in the folder.

I have tried logging into the domain with these settings but can still not map to the shares in the script?

Any ideas?

Many thanks

 

[karlisi]

You can use logon scripts on Win9x in Win2000 AD without DS client installed and without Kixtart too. You only must use Client for Microsoft networks as primary logon and must logon in your domain.
Also check if you have \\Domain_controller\NETLOGON share available for your users because pre-Win2000 clients uses this share to download logon scripts.
There are some Win9x specific things for scripting - you cannot map share subfolder to network disk (net use X: \\server\share\folder is invalid command), only share itself (net use X: \\server\share is OK). It is not recommended to map something to Z: because this letter Win9x uses as temporary mapping for running logon script. If you use DOS batch files for scripts, use .bat extension, not .cmd.
Read also these threads:
Thread96-646392
Thread96-669186

===
Karlis
ECDL; MCP

 

[DazzaC]

Please excuse my ignorance, but what is the NETLOGON that you are referring to?

 

[crobin1]

At a command prompt issue the following:

net view \\domaincontroller

Among the shares listed you should see NETLOGON. Assuming it is there, from any workstation you should be able to browse to the folder through Network Neighborhood/My Network Places or from a command prompt:

dir \\domaincontroller\netlogon

From one of your Windows 95 boxes try to access the netlogon share and see what happens.

 

[karlisi]

For Windows 2000 server share \\servername\netlogon holds logon scripts. Locally on server this is C:\winnt\system32\sysvol\sysvol\yourdomainname\scripts\ directory where yourdomainname is your domain name i.e. acme.net.

===
Karlis
ECDL; MCP

 

[DazzaC]

Thanks guys I will look at this in the morning.

I read on the Microsoft site today that the Windows 2000 Pro disc contains extensions, that allow you to connect Windows 9x machines to w2k resources?

Anyone ever used or heard of this?

 

[tangostar]

Ok this sounds like the long and hard way.

All I've ever done for 95 clients is:
Specify domain
Specify DNS
On the DC for the Domain inclued in the NETLOGON share:
KIX32.exe
KX32.dll
KX16.dll
KX95.dll
and the Kix script
then in AD for the user specify a logon script that starts KIX
like logon.bat
which contains:

%0\..\kix32.exe scriptname.kix

EXIT

that one line tells KIXTART to use the file scriptname.kix as the logon script and you're done.

 

[DazzaC]

At present in the NETLOGON share I do not have the kix16.dll.

So what you are saying is on the users profile, in the profile, logon script [logon.bat]- represent entry box.

Then in the batch file:

%0\..\Kix32.exe and the script name.

What is the %0 for please?

 

[tangostar]

Yep, in the box where it says logon script you put the name of the, logon script. The one that references the kixtart script.

%0 is an expansion variable used to reference the batch file name.