Michael,
It would be nice and useful to show in client not only the IP address of the client who is using the device but also the NETBIOS name and client username (if possible)
For example: 10.10.10.100 (username@DOMAIN at PCNAME)
Now it's quite hard to find out who is using the device especially when PCs get their IPs by DHCP and users are sitting in different rooms)
I took a look but its too
I took a look but its too complicated a change because the NETBIOS name resolution can be quite slow and windows networks need a reverse dns entry for the NETBIOS name and it wouldnt work with the client api correctly.
Just an idea: what if the
Just an idea: what if the client will send all the data on connect to VH server. So as far as client knows everything about himself (netbios name, current username, ip, domain, etc..) there is no need to make DNS request from server etc
.
If you type
nbtstat -A <ip address>
on your machine what does it say for the netbios name of that ip?in my network i've got
in my network i've got nothing (here is a MS active directory infrastructure with strict security policy via GPO)
Thats basically what the
Thats basically what the server would do so it wouldnt work...
mmm... seems we misunderstood
mmm... seems we misunderstood each other.
I mean: when client connects to the server it (client) know all the data: IP, it's name (NETBIOS), User Accoung name (under witch client is started up, IP address ...
So client could send to the server "Hello message" - XML structure or whatever format with all these data.
Server could store it in his memory and when another client tries to grab USB device (which has been already used by another client) server will send to client (who tries to use already used devices) all the info from his memory: IP, username, domain etc
That command i asked you to
That command i asked you to run would be similar to the commands i would call on the server to get the netbios name. Hence if it doesnt work for your client it wont work on the server either. The NETBIOS name cannot be implemented on the server because , 1. it cannot look it up, and 2. it takes too long, its a slow synchronous operation, if this was done on client connection it would slow down the connection greatly...
With the solution I'm
With the solution I'm proposing there is no need to execute any command on server side!!
Client! When client starts up it knos exactly all the data: is's name (hostname), IP, domain, user accoun name!
Next client connects to server to grab USB devices and send to server some data like:
Compname
10.10.10.10
MyDomain
Andrey
or any other datastructure.
Server saves this data into his memory and when it's needed (when another client with IP=10.10.10.20 connets to it and trues to reuse already used USB device) server informs that client that USB device has been already used and send all the data from XML structure above
May be NETBIOS is confusing
May be NETBIOS is confusing ...
On client there is no need to get it via network request! On client NETBIOS == hostname! and could be retrived via internal syscommand without and penalty or delay
Hello amatveev. I think, you
Hello amatveev. I think, you can use nmblookup -A 10.94.9.18 in your auth script to resolve IP->netbios name
Or you can scan your network
Or you can scan your network for map ip->netbios and save result to small database, then you can resolve ip from database without delay
I don't need a NETBIOS name
I don't need a NETBIOS name on server in auth script :)
I need it on Client2 when Client1 is using USB and Clinet2 tries to use the same device. Just to inform the user on Client2 that USB devices is used by: IP, PC NAME, USER NAME
Currently only IP address of Client1 is shown is info box on Client2
I think it possible make in
I think it possible make in auth script, you can send message (mail, jabber, etc) from auth script to client 2, when client 1 connect to same usb device
OK, i implemented this in 2.6
OK, i implemented this in 2.6.2 of the server, and 3.2.7 of the client.
Hostname is not displayed
Hostname is not displayed
In Use By: user (user) at 10.30.0.175
(hostname should be Sunlife-xxx) in me scenario
I would prefer the following
I would prefer the following format:
In Use By:
User: user [at] copr.domain (user[at]copr[dot]domain)
PC: Sunlife-xxx
IP: 10.30.0.175
You must use 3.2.6 for all
You must use 3.2.6 for all clients, if you mix the previous with the new version the hostname won't display
OK in version 3.2.8 of the
OK in version 3.2.8 of the client ,its neater when it shows in use devices similar to what you describe above.