Break On
Dim $SO
$SO=SetOption('Explicit','On')
$SO=SetOption('NoVarsInStrings','On')
  
Dim $LServerIP
$LServerIP=Ping(Join(Split(@LServer,"\\"),""),1,0,3)
? 'Logon Server IP is: ' + $LServerIP
? 'Logon Server name is: ' + Join(Split(@LServer,"\\"))
  
function Ping($Computer,$GetIP,optional $LoopCount,optional $TimeOut)
	if $GetIP
		dim $ip, $ipfile, $
		$ipfile = @scriptdir + '\ip.txt'
		shell '%Comspec% /q /e:1024 /c for /F "tokens=2 delims=[]" %%i IN ('+ chr(39)
		+ '"ping ' + $Computer + ' -n 1 | find "]""' + chr(39) + ') do echo %%i >"' + $ipfile + '"'
		$ = open(10,$ipfile,2) $ip = readline(10) $ = close(10) del $ipfile
		if $ip
			$Ping = $ip
		else
			$Ping = 'Bad IP address ' + $Computer + '!'
		endif
		exit 0
	else
		if $TimeOut
			for $c = 0 to $LoopCount
				shell '%Comspec% /C ping ' + $Computer + ' -n 1 -w ' + $TimeOut + ' | find /C "TTL=" > nul'
				if @error = 0
					$Ping = 1
					exit 0
				endif
			next
		else
			for $c = 0 to $LoopCount
				shell '%Comspec% /C ping ' + $Computer + ' | find /C "TTL=" > nul'
				if @error = 0
					$Ping = 1
					exit 0
				endif
			next
		endif
		$Ping = 0
	endif
endfunction

Quote:

---

Shouldn't be a real need to get the IP since the logon server should have a STATIC IP and you can get the name of the server that logged the client in with the @LServer macro.

---

Quote:

---

if there is a need though try : Ping() - checks for reply , or returns ip-address of remote host

---

Quote:

---

What do you think of that solution?

---

Quote:

---

I have only glanced at your function but I saw a timeout parameter and that makes me think that there is a possibility it might fail to recieve the ip address.

---

nah, that timeout is just an optional parameter for the maximum duration of trying to get a reply ... the resolution of course relies on the systems ability to resolve the IP from host name, speak DNS, WINS or a hosts file

Quote:

---

I think it's a pretty awful idea. Why do you need the IP address explicitly, rather than the machine name?

---

Ofcaurse it's a bad solution, that's why I've asked for a better one here but at least it is robust. The client will always be able to get the ip address.

I need the ip address to setup the timesync between the client ( win xp ) and the server ( win nt4 ). But that's beside the scope of this forum.

Quote:

---

I need the ip address to setup the timesync between the client ( win xp ) and the server ( win nt4 ). But that's beside the scope of this forum.

---

1. The best solution then would be what you already came up with. Awful? Who cares! ... Well, ok, an ini-file would fit better to prevent file lock issues!! See read/writeprofilestring functions.

2. What makes you think that the scope of KiXtart.org is reduced to KiXtart scripts?

$oWMI = GetObject("winmgmts:\\.\root\cimv2")
$colPings=$oWMI.ExecQuery("Select * From Win32_PingStatus where Address = '"+SubStr(%LOGONSERVER%,3)+"'")
 
For Each $oStatus in $colPings
	"Logon server IP address: " $oStatus.ProtocolAddress ?
Next

Quote:

---

1. The best solution then would be what you already came up with. Awful? Who cares! ... Well, ok, an ini-file would fit better to prevent file lock issues!! See read/writeprofilestring functions.

2. What makes you think that the scope of KiXtart.org is reduced to KiXtart scripts?

---

Thank you for the tip about the ini-file, that's what I'll use.

Oops, I meant to say thread ofcaurse , not forum

Quote:

---

Have a look at the KiXtart builtin macros.

@IPADDRESS0 will do in most cases.

---

Quote:

---

Well, ok, an ini-file would fit better to prevent file lock issues

---