• We use NT Server 4.0 as our server
• We have a PDC on our HQ (let's call it HQ) and a BDC at our branch (let's call it BR).
• On Both places, we have clients with OS vary from DOS 5.0 to Windows XP.
• We use fixed IP to identify our workstations and servers, 192.168.1.X (for HQ) and 192.168.2.X (for BR) except for DOS.
• On both places, we had login script:
  HQ - NET USE G: \\PDC\DATA
  BR - NET USE G: \\BDC\DATA
• WAN communication from HQ to BR (VV) we use L/C (only 128 kbps).

• I want to grab the correct login script. ex. When i am at HQ, i want to to run login script at HQ. Somebody tell me, i can just use KiXtart to overcome this problem, and i found it really help me (I use @IPADDRESS0 to identify where am i now and use SHELL to execute the right NET USE). Everything works well except for DOS workstation since they don't have IP Address. How do i overcome this ?
• Since the size of KIX32 is about 230KBytes, while our WAN bandwidth is only 128 kbps and we have a lot of workstation on both places, how do i tell the server to grab the correct KIX32 to save our bandwidth. ex. when i am at HQ, it will run KIX32 from HQ. How do i overcome this (i don't want to copied it to every station manually)?

code:

---

 "our logonscript - ver 1.1" ?
"run from: @lserver" ? 

---

thus, you would see that info always.
this being the simpliest way, obviously.

finally, what comes to dos-boxes...
do they run logonscripts?

[ 18. September 2003, 12:26: Message edited by: Lonkero ]

quote:

---

instead of net use, read the manual for USE.
this way you don't need shelling and your script will definitely run faster.

the logonscript is always drawn (IIRC) from the server with best response/willingness.

you could check on that.
at to very start of your script:

code:
--------------------------------------------------------------------------------

"our logonscript - ver 1.1" ?"run from: @lserver" ?

--------------------------------------------------------------------------------

thus, you would see that info always.
this being the simpliest way, obviously.

---

quote:

---

finally, what comes to dos-boxes...
do they run logonscripts?

---

code:

---

 
$tcpip = @IPAddress0
$3octet = val(substr($tcpip,9,3))   ;Assuming all of your IP addresses use a single digit class C

SELECT
	Case $3octet = 1
		$location = "Headquarters"
		$localserver = "HQ"

	Case $3octet = 2
		$location = "Branch Office"
		$localserver = "BR"

	Case 1
		"Something screwy going on if you don't have either of these IP addresses"
EndSelect

;Time to map drives

	? "YOu are located at the $location office"

	? "Connecting G: to \\$localserver\data"
		use g: "\\$localserver\data"
 

---

quote:

---

You could do something like this:

code:
--------------------------------------------------------------------------------

$tcpip = @IPAddress0$3octet = val(substr($tcpip,9,3)) ;Assuming all of your IP addresses use a single digit class CSELECT Case $3octet = 1 $location = "Headquarters" $localserver = "HQ" Case $3octet = 2 $location = "Branch Office" $localserver = "BR" Case 1 "Something screwy going on if you don't have either of these IP addresses"EndSelect;Time to map drives ? "YOu are located at the $location office" ? "Connecting G: to \\$localserver\data" use g: "\\$localserver\data"

--------------------------------------------------------------------------------

[ 23. September 2003, 07:57: Message edited by: Paul_Berquam ]

---

quote:

---

we suggest also to install kixtart files (kix32.exe
+ kx16.dll, kx32.dll, kx95.dll) on your clients

---