I've got a PDC and a BDC. Both servers are running the kxrpc service and have the kx16, 32 and 95.dll's in the netlogon share.

I'm using the 'Case InGroup' function to specify what departments get what drive mapped and I've noticed this is where the message appears but the script can continue and map drives which aren't using the 'Case InGroup' function. All help appreciated

; KIXTART.SCR
;
; Crawford THG default logon script
;
; Changed to delete network connections for amfproject 22/09/00
;
CLS

Small
Color g+/n
at (2,8) "Hello, "
@userid

Color r+/n
if @userid = ""
at (6,10) "unable to logon to " + @LSERVER + " - press any key to retry"
Get$
endif
at (6,0) "Creating Server connections "

Use "*" /delete /persistent ; Delete all current connections permenantly
; Except for netlogon

Select

; Case InGroup("LCSUSER")
; use X: "\\MIL2PDC1\XDRIVE"
; USE T: "\\MILTLCS1\LCSDATA"
; USE S: "\\MILTLCS1\SHARED"

Case InGroup("MIMSUSER")
USE X: "\\MIL2BDC1\RECORDS"
USE N: "\\MIL2BDC1\MIMS"
USE J: "\\MIL2BDC1\LETTERS"

Case InGroup("Healthcare Users")
USE X: "\\MIL2BDC1\RECORDS"
USE S: "\\MIL2SQL1\HEALTH"
USE P: "\\MIL2SQL1\PRINSTAL"

EndSelect

USE L: "\\MIL2SQL1\DISKS"
USE V: "\\MIL2SQL1\COVER"
USE Y: "\\MIL2BDC1\@USERID$"
USE W: "\\MIL2BDC1\ClaimsAdmin"
USE Z: "\\MIL2PDC1\CDROM"

code:

---

break on
cls

$a=1
$b=2

select
	case $a=1 "$$a is 1" ? 
	case $b=2 "$$b is 2" ?
	case else "something is not" ?
endSelect
quit

---

When you run that, you will get "$a is 1" only because KiX will not test the CASE $b=2 line.

cj

------------------
For more scripts goto my website and click the hammer and spanner icon.

chrismat@ozemail.com.au

Additionally, while the case statement would not evaluate the 2nd grouping for dual members, this condition by itself would not cause the original error you noted - 'Unable to logon to \\xxxBDC...'.

My guess is the situation is either KiXRpc service, or another LAN/Windows NT issue, and not your script syntax causing the error.

Suggest reinstalling KixRPC service on the BDC(s) noted in the error, as you may have corrupted DLL files (we are assuming you are using v3.63). Also, delete and reinstall Kix DLL's for Win9x clients in your netlogon share (confirm properly copied from PDC to BDC).

Are all clients receiving this error (WinNT/2K/9x), or only Win9x? Does it happen only to users on particular hub/switch?

Suggest also examining NT Event Logs on BDC and PDC for any unusual events - perhaps another service or software interfering with KixRPC.

You might also try changing script from CASE statements to IF, so that running script in debug mode (/d) for dual group members will properly confirm if all mapping attempts to the '\\xxxBDC' are failing, or only particular mappings (I suspect all would be failing).

Also, if you are noticing any other flakey connectivity issues to the BDC(s) in question check hub/switch device for failing port, loose/worn cables (to servers, and between hub/switch devices) etc.

Lastly, check this post for script on checking/updating Kix files to keep clients/servers current.
http://kixtart.org/board/Forum1/HTML/002030.html

Bill

[This message has been edited by bleonard (edited 20 March 2001).]

Cheers

Cheers

quote:

---

When a Win9x user logs onto my network using kixtart they receive the message 'Unable to logon to \\xxxBDC - press any key to retry'.

---

An early part of the script is:

code:

---

if @userid = "" 
at (6,10) "unable to logon to " + @LSERVER + " - press any key to retry"

---

Based on that I would say you appear to have an empty @USERID. Or did I miss something? Anyway, assuming you are calling this via a batch file I suggest that for at least on etest user you call Kixtart with the /d option and single step the script so that you can reliably pinpoint where it's going wrong. Please let us know the results.

Bleonard, you gave me credit for CJ's comments. You must have been thinking of another post. (I'd put a winking smiley here but haven't worked out that bit yet.)

Regarding the problem at hand - I am not sure why to even test for a blank '@USERID', since lack of a valid id would prevent authentication by the DC's by definition. I would recommend removing that section from the script to see what happens. If works, but still require, perhaps alter to '@USERID < "0"' (since I believe numeric evaluated before alpha characters).

Bill

CJ - Just kidding. Don't come flying up here to exact revenge.

------------------
"Array-Boy for the Northern Hemisphere"

If only on win9x computers... are these computers win95, or win98?

If only win95.... this might be a msnet32.dll problem (i have been saying this a lot lately )

Read the end of this thread here KXRPC Server error

Bryce

------------------
kix.isorg.net

This is happening on both 95 and 98 clients. I've just upgraded Dll's and exe's to 3.63. I tried replacing the top part of the script with whats printed below but still no joy it just missed the drive mappings under 'Case Ingroup' but again it mapped the drives under 'End Select'.

Small
Color g+/n
at (2,8) "Hello, " + @userid
Color W+/n
at (4,0) "Creating Server connections "