|
|
|||||||
We have a problem on a win95 machine The variable @ldomain is not recognised. I have kixrpc-service installed on every logonserver, and kx16.dll kx32.dll and kx95.dll installed in the windows directory, where also kix32.exe is. if the user logges on to a other machine there's no problem. I've copied the .dll's from the second machine to the first, with no succes. the code is: code:All the items where listed, except for the @ldomain, this one is empty.if @userid = ("test") Anyone with an idea? |
||||||||
|
|
|||||||
Hi Arjen, Can you check if you don't see these macros too?: @HomeDrive @PrimaryGroup @RServer @SID If you can see those we can safely say the RPC service is working, and we have to look at the network configuration. If you don't see them we should look at the RPC configuration a bit more... |
||||||||
|
|
|||||||
nope, all of them are empty.... We've installed this service a couple of months ago, and this seems to be te only computer with this problem....... [ 10 April 2002, 13:03: Message edited by: Arjen ] |
||||||||
|
|
|||||||
ok, you're saying that you just have one W95 system that can't resolve the variables? If that's the case... imho, you shouldn't look any further but just re-install that system, or isn't that an option? |
||||||||
|
|
|||||||
it might be an solution, but i'm wondering why it's happening... I've replaced all the kix-files, so where would be the problem. That's what i wanna know.... |
||||||||
|
|
|||||||
OK.. The server side is fine.. But when you login, do your users have access to KX95.DLL, KX16.DLL, KX32.DLL as well as KIX32.EXE? OK.. I re-read your initial post and yes.. What version of Kix are you running? Are the above DLLs out of the same archive that the KIX32.EXE is from? For example KX32.DLL should be version 3.60.0.0. And this is what is shown under 3.63 as well as 4.02. Have you looked at this - http://www.jsiinc.com/SUBA/tip0100/rh0120.htm ? - Kent |
||||||||
|
|
|||||||
How are you calling the kix32.exe? The only thing I can think of (other than file versions) is that there may be something not quite right with your search path on the Windows 95 machine. Does the problem present itself if you are in the windows directory when you call the script? Brian |
||||||||
|
|
|||||||
It's a problem in our logonscript for this computer. Drivemappings based on logondomain are wrong mapped, just because the pc doesn't know @ldomain. The code I've posted is just a part of a checking script, wich I've put in our logonscript to find the error. |
||||||||
|
|
|||||||
What version of Internet Explorer is on this Win95 system? As long as your not in a locked down type of environment, maybe try updating IE with all the latest updates. Try checking all the path locations for a possible file name for kix32 or your script name that may be an older copy somewhere in the path, or to rule that out locate and delete all copies of KIX32.EXE and the .DLL files locally. Maybe also try using an account with NO logon script assigned. Then put a batch file in the startup folder using all local files that calls your test script. MD C:\MYTEST Copy all the KiXtart v4.02 files into this folder. Delete any other copies of KiXtart from the computer in question. BATCH code:MYTEST.KIX@ECHO OFF code:Please let us know if any of these ideas work or not.cls |
||||||||
|
|
|||||||
We're still working here with kix3.62, We've got some troubles here to upgrade, people don't really want to... I've already logged in with an user with a different logonscript not using kix, and there was still the problem. I can't test your script anymore, the costumer have the computer back now and he's waiting for reinstall. I hope the problem will not return after reinstall, but i'm still wondering why this could happen... |
||||||||
|
|
|||||||
I'm not really sure, that is why I wanted you to try some of these suggestions. It could possibly be that KiX was looking for a file that a newer version of IE has. Les used to use 3.62 but I don't recall him ever complaining about that. Then again he does not seem to have many Windows 9x systems (if any). I assume something is wrong with that computer since you don't say it is a problem on any other system. I use 3.63 and I don't have this problem on any system I've seen so far. Well, if you don't have it anymore then I guess it is not an issue until such a time as it resurfaces. If it does, keep this link in mind for some things to try. |
||||||||
|
|
|||||||
Dear Arjen, Very important is that kixtart binaries are from same release. First we advise you: - put the files kix32.exe, kx16.dll, kx32.dll, kx95.dll in your c:\windows directory. - remove all other kixtart binaries from your clients. Reasons:
- verify all KXRPC on your domain controllers and verify they are the right one. Third: - simply your script and BATch file. LOGON.BAT code:logon.kix@echo off code:Fourth: you can use following code to retrieve actual domain and ldomaincls values from your registry. code:greetings.$domain="" btw: Arjen, what are your problems with upgrading? did you have also problems with upgrading to f.e. kixtart3.63 release? |
||||||||
|
|
|||||||
I've checked all thel .dll-files, they were only in the windows dir. And i would rather not changing the loginscript for just 1 computer. But the computer is being reinstalled, and i haven't heard of any problems yet. I don't know what was the problem, but i guess It's over now..... Thanx all for thinking with me... |
||||||||
|
|
|||||||
In most cases this happens because a file is missing or there is an incompatible file version associated with the problem machine. This problem comes up daily in dozens of different variants. Suggestions. 1. Make sure the same version of kxrpc is installed on all PDC & BDC servers. 2. Make sure your logon scripts are replicating to all PDC & BDC. 3. Make sure all netlogon shares have the complete set of kix dll files & make sure they are same versions of the kix dlls (replication should fix this) 4. Make sure that locally each machine has the same versions of the kix dlls installed. 5. Make sure kxrpc & dlls are same version. 6. Make sure that all machines are starting the same logon script. 7. Make sure logon scripts are starting on all machines. 8. if your logon script is using shares other than netlogon make sure all machines are successfully attaching these share. 9. On win9x machines do not try to assign the z. 10. Watch out for old versions of logon scripts, kix scripts or kix dlls installed locally. I hope this helps. MCA programs can help you automate these checks. |
||||||||
|
|
|||||||
Dear Jack Lothian, Your suggestion is good input for the FAQ forum. A possible description can be: what to do with kixtart problems. greetings. |