#43802 - 2003-08-07 07:37 PM
ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
Until last week my logon scripting worked fine. It still does for Win2K and XP. However, in Win98 my script now exits as soon as it hits the first ingroup command. I have placed print statements in the script to narrow down where it is dying and it is definitely as soon as it hits the ingroup statement. Other If statements don't cause a problem. I have about 50 users who this effects.
Any ideas?
Dan
|
|
Top
|
|
|
|
|
#43804 - 2003-08-07 07:58 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
No changes in the script in the 2 months I've been using it until I put some print statements in today to track down where it was bombing.
Ok. I tried the debug on and as soon as I get to teh first if ingroup it exits. Dumps it right back to the batch file. My test If statement a fe wlines before the if ingroup works without a hitch, so I don't think it's the if part of things.
Dan
|
|
Top
|
|
|
|
|
#43806 - 2003-08-07 08:07 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
I am running the kxrpc service. I updated to whatever came with 4.2.1 this morning. (I was running 4.2.0 before that.) I can't reboots the DC's, networking contgrols those. I can possibly reboot my server (a member server in the domain) in an hour or so when most folk are gone to lunch, otherwise that has to wait until tonight.
I have restarted the kxrpc service, however.
Dan
|
|
Top
|
|
|
|
|
#43808 - 2003-08-07 08:49 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
I was afraid that was the answer, although why it's worked up until now is beyond me.
Our cmapus is migrating to an Active Directory environment. However, it isn't as centralised as it should be. The DC's are run by netowrking, and they do pretty much whatever they want with them. My server is for one college and is a member of the AD, but not allowed to be a DC by networking policy.
Any suggestions? I am trying to get them to update the version of kixtart on teh dc's since it isn't in use anywhere else.
Dan
|
|
Top
|
|
|
|
#43810 - 2003-08-07 09:16 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
I will see what networking is willing to do. However, they are going to argue about why it worked for 2 months and quit now and they will argue because the manual states "The server side of the RPC interface is provided in Kxrpc.exe, and this should be installed and run on one or more Windows NT systems. The KiXtart RPC service can run on any Windows NT system: a workstation, a standalone server, or a logon server. The system must be either a member of the logon domain or a member of a resource domain that has a trust relationship with the logon domain." Since this says the system can be a member of the logon domain, I may have a problem with them.
I am currently using the .ini file method of pointing it to the kxrpc server.
Dan
|
|
Top
|
|
|
|
|
#43813 - 2003-08-07 09:22 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
So, any other suggestions while i wait on networking?
Thanks.
Dan
|
|
Top
|
|
|
|
|
#43816 - 2003-08-07 10:19 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
Ok. Here's the batch file to call the KIX script:
@Echo Off
CLS
Echo "Test file for calling test.kix"
%WINDIR%\SYSTEM\KIX32.EXE c:\mydocu~1\kixtest\test.kix
Echo "Back in batch file"
pause
exit
Here's the test script:
;debug on
dim $testname
$testname="testing"
? "Test Script now processing..."
SHELL "winset.exe USERNAME=@USERID"
? @userid " userid"
SHELL "winset.exe DOMAIN=@DOMAIN"
? @domain " domain"
? $testname
$testname = ingroup("COE-CEP")
? $testname
EXIT
Here's the results:
"Test file for calling test.kix"
Test Script now processing...
DFENWICK userid
UNR domain
testing"Back in batch file"
Press any key to continue . . .
I did get networking to install the kxrpc on the dc's, but didn't have any better luck when I pointed my login script to them, instead.
Is there a possability of a problem with something timing out? script processing seems to be taking forever when it has anything to do with getting to the DC's.
Dan
|
|
Top
|
|
|
|
|
#43817 - 2003-08-07 10:21 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
Our DC's are Windows 2000 AD. I believe in mixed mode so tehy are happier with Windows 9x, but I can't guarentee that one.
It is possible they changed permissions somewhere, but I have the logon directory on my local server and it has read rights for everyone to try to keep those kinds of changes from causing issues.
Dan
|
|
Top
|
|
|
|
|
#43819 - 2003-08-07 11:01 PM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
Just for informations sake, it's all one site, just spread across campus. Everything runs on a routed Gig backbone with HP switches splitting out to 100 mb feeds to downstream switches. If I ping the DC it comes back immediately, but smb traffic seems to be going extremely slowly. I can't find a reason and I'm told that "we didn't change anything." We have WINS running, too.
Dan
|
|
Top
|
|
|
|
#43820 - 2003-08-08 01:06 AM
Re: ingroup boming script
|
DanNV
Fresh Scripter
Registered: 2003-08-07
Posts: 16
|
Thanks for all the ideas. At least I have the kxrpc updated on the DC's now. Turns out networking had something plugged into teh network that was trashing smb connections all over campus. Now that they have it disconnected everything is working again.
Dan
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 2220 anonymous users online.
|
|
|
![[Confused]](images/icons/confused.gif){kind=icon}
