Page 1 of 1 1
Topic Options
#1238 - 1999-12-28 08:51 PM Ingroup still not working in windows 95!
Anonymous
Unregistered


Thanks for all the suggestions, but I've tried to make INGROUP work in Windows 95 OSR2, but to no avail. The script itself is pretty simple:

IF INGROUP("SMS")=1
run smsls.bat
ENDIF
exit

I've tried replacing the MSNET32.DLL with the most recent version. That didn't work. I tried installing the kxrpc service on all domain controllers (even though I shouldn't need to, with the system only using global groups). That didn't work. I tried using the latest kixtart 95 (v.3.62). That didn't work. When I run the file

%0\..\kix32 sms

nothing happens. No error messages, only a blank space. It works just fine on NT. I'm trying to specify for users in a SMS global group to delineate users to install the SMS client on. Has anyone got any suggestions or seen this type of problem before?? Thank you!!!

Top
#1239 - 1999-12-29 02:14 PM Re: Ingroup still not working in windows 95!
Anonymous
Unregistered


Have you tried:
1. Running the script in debug mode to see if any errors appear (run kixtart from the command line with a /d after the script eg "kix32 myscript.scr /d" then step through).
2. Checking the kixtart log (%windir%\temp\kixtart.log).
3. Creating a Kixtart.ini file with a [KXRPCMapping] section specifying KXRPC servers.


Ken Ralston
Ken Ralston IT Consultants
Auckland
New Zealand

Top
#1240 - 1999-12-30 08:17 AM Re: Ingroup still not working in windows 95!
Anonymous
Unregistered


We had the same problem in our master domain model. Kixtart INGROUP function works only fine with local groups on Windows 95. On NT global groups are supported. Create a local SMS group and fill it with the global SMS group, then check to see a user is member of the local group. That should work (worked for us)...

Top
#1241 - 1999-12-31 02:35 PM Re: Ingroup still not working in windows 95!
Anonymous
Unregistered


Thanks for your replies guys, its working now...(local groups)

moogeboo

Top
#1242 - 2000-01-06 12:27 AM Re: Ingroup still not working in windows 95!
Anonymous
Unregistered


Having INGROUP problems also. Just effects certain users who are on a different network segment. When they logon to a PC within same segment as PDC/BDC INGROUP functions properly.

This behavior exists regardless of whether the user is a member of the GLOBAL Development group or not (tested for membership in another group which also failed). If I run the script, after logging in, at a DOS prompt, the correct mappings are set for the Development group.

All users are running Win95
All users are within the same domain
The domain name matches the workgroup name for all users
The users within the Development group are on another network segment than the other users.
Users in the development group get the correct mappings when they log on a PC within the same segment as the domain controllers.
I used the debug switch (/d) to step thru script - nothing unusual except INGROUP failed where it should not.

if INGROUP("Development") = 0
use h: "\\ny-prod-nt\oralce
else
use h: "\\ntbrokdev\oracle"
endif

Any suggestions?

Top
Page 1 of 1 1


Moderator:  Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart 
Hop to:
Shout Box

Who's Online
0 registered and 640 anonymous users online.
Newest Members
ManuvdWielNL, Sir_Barrington, batdk82, StuTheCoder, M_Moore
17887 Registered Users

Generated in 0.049 seconds in which 0.023 seconds were spent on a total of 12 queries. Zlib compression enabled.

Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org