New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 593574 link

Starred by 7 users

Issue metadata

Status: Duplicate
Merged: issue 676195
Owner:
Closed: Oct 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome
Pri: 2
Type: Feature



Sign in to add a comment

No DHCP hostname in Windows DHCP server

Reported by matthew....@wf.catholic.edu.au, Mar 10 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36

Steps to reproduce the problem:
1. Join wireless network - check DHCP service on Windows server

What is the expected behavior?
See a hostname

What went wrong?
No hostname

Did this work before? No 

Chrome version: 48.0.2564.109  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

There are numerous reasons a network administrator may wish to identify a device on the network if you the IP.

For example from my router I can see which IP's are consuming internet bandwidth.

From the DHCP server I can't see a hostname but I can get a mac address - but a mac address isn't searchable in the Chrome management console.

Either we need to set the default hostname as a chrome management console searchable field eg. serial number 

or 

we need to be able to search by MAC on the console.

This is sort of similar to issue # 126802 but rather than being able to add a hostname I would be happy to at least have the serial number as the default/advertised hostname so I can identify a device which will give me the user so I know who to yell at.

Thanks
Matt
 
Components: Blink>Network
Status: Untriaged (was: Unconfirmed)
As the issue is of feature request marking it as Untriaged to get more inputs from dev team.

Thanks,
Cc: pstew@chromium.org
Components: -Blink>Network OS>Systems>Network Enterprise
Labels: OS-Chrome

Comment 3 by pstew@chromium.org, Mar 16 2016

Cc: -pstew@chromium.org jleong@chromium.org
Not sure who should take this.  Historically there are multiple requests of this kind.  Most of them don't take into account the possible privacy implications of broadcasting unique information about the device on connecting to a network.  Presumably this could be done per-network via some enterprise policy.  b/24162121 covers all the infrastructural items needed in the connection manager.  Further work in Chrome (presumably enterprise) will need to be done to fulfill this request.

Comment 4 by jleong@chromium.org, Mar 16 2016

Cc: snanda@chromium.org
Owner: dskaram@chromium.org
Thanks, Paul! David, how do you feel about this feature?
We had a similar request from a customer that wanted to do DHCP fingerprinting. Their DHCP servers were seeing Chromebooks as Linux machines and they had no way to add network privileges by differentiating Chromebooks from e.g. Linux printers.

So I definitely see value in introducing an enterprise knob for this. pstew@ helped us add the groundwork but we never got the cycles to put it into Chrome.
Status: Assigned (was: Untriaged)
Any timeline on adding this feature?  I have many chromeboxes deployed in an enterprise environment, and it would be a huge help to have hostnames on these boxes, and be able to see them in DHCP (for in turn dynamically updating DNS).  Right now to effectively monitor the devices we must create DHCP reservations or statically assign IPs.  With a hostname feature the Chromeboxes could just be monitored by hostname, which makes it much easier to provision these boxes.  Thanks for any info!

Comment 8 by dskaram@google.com, Apr 18 2016

Cc: saswat@chromium.org aghuie@chromium.org gbirtchnell@chromium.org dskaram@chromium.org sdavern@chromium.org
 Issue 597859  has been merged into this issue.

Comment 9 by si...@annear.org, May 29 2016

At the moment the device name shows in the DCHP server as a blank.... it would a significant step better if the hostname was "chromebook" or similar (perhaps from the DeviceType value in about://system.  This would at least allow you to identify the machines that are chromebooks without having the check the MAC address... slightly more helpful, and probably not that difficult to implement :-)

Cc: cernekee@chromium.org
Cc: -saswat@chromium.org
Owner: marcuskoehler@chromium.org
Labels: Hotlist-Enterprise-Networking
Mergedinto: 676195
Status: Duplicate (was: Assigned)

Sign in to add a comment