I have the same issue with ethernet, It won't connect when I set a static IP.
I'm on the normal version 59

Clarification - in addition to not seeing a "Save" option, I tried to simply exit Settings after changing to a fixed IP. When I returned, Automatic was enabled again.

The same happens with all chromebooks in my school, you can not connect new users with static ip address. You can not configure new chromebooks in our school network. The error started when you upgraded to version 59. Our network does not use DHCP, all are static addresses. Which is bad, we just bought 55.

9460.60.0 (Official Build) stable-channel land
Firmware
Google_Terra.7287.154.80
Channel
Currently in stable
CHANGE CHANNEL
ARC version
4059099
Blink
537.36 (? 0)
V8
5.9.211.31
User agent
Mozilla / 5.0 (X11; CrOS x86_64 9460.60.0) AppleWebKit / 537.36 (KHTML, like Gecko) Chrome / 59.0.3071.91 Safari / 537.36
Command line
/ Opt / google / chrome / chrome --ppii-flash-path = / opt / google / chrome / pepper / libpepflashplayer.so --ppap-flash-version = 26.0.0.102 --ui-prioritize-in-gpu-process --enable-logging --log-level = 1 --use-cras --enable-wayland-server --arc-availability = installed - -user-data-dir = / home / chronos --max-unused-resource-memory-usage-percentage = 5 --login-profile = user --has-chromeos-keyboard --default-wallpaper-large = / usr /share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small = / usr / share / chromeos-assets / wallpaper / oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large = Usr / share / chromeos-assets / wallpaper / guest_large.jpg --guest-wallpaper-small = / usr / share / chromeos-assets / wallpaper / guest_small.jpg --enable-prefixed-encrypted-media --enable- - -modinus-limit = 19 -login-manager -first-exec-after-boot -vmodule = * arc / * = 1, * Chromeos / login / * = 1, auto_enrollment_controll / = 1, power_button_observer = 2, webui_login_view = 2, lock_state_controller = 2, * zygote * = 1, * / ui / ozone / 2, webui_screen_locker = 2, screen_locker = 2 --silent-launch
Compilation date
Monday, June 5, 2017

Experiencing the same thing.  Got out of it using a method I found elsewhere on the web, don't remember where exactly so can't give credit where it's due, but:

1. Allow the machine to acquire a DHCP address, in our case we did that by allowing it to connect to the router instead of the device we really wanted to connect to.
2. After the machine acquires a DHCP address, turning off the 'automatic IP' slider sticks, and typing in a manual address also stick.

Thanks for response aeh... but your method worked before upgrade to ver 59.
I powerwashed one cb and follow this method to connect to static ip:
1) new user: google mail & pass
2) select dhcp network (net1) & password. Connection OK. Internet connection OK.

Same chromebook, net1 is active. Now connecting to a non DHCP network
3) select new network from list (net2)
4) check preferred network & automatic connection
5) Advanced: network: uncheck automatic connection
6) set static ip address, mask & gateway
7) set automatic or Google DNS name servers
8) proxy: set to manual
9) proxy ip & port
10) save
The system ask for network password, write the password, connecting...... ask password again, connecting..... 
System doesn't save network configuration and back to an automatic ip address and show error searching dhcp.

<triage>: Steven, could you please triage this? Thanks!

Might be the same as  issue 733426 , it is next on my plate to investigate.

Thanks for the detailed repro.

You may be able to work around this by using the old settings at chrome://settings-frame for now.

 Issue 733426  has been merged into this issue.

I figured out what is going on here. Thanks for the workaround descriptions, that helped debug this.

The fix shouldn't be too difficult, working on it now.

We're going to want to merge this to 59 if possible...

Hi Steve,

I just tried the trick of going to chrome://settings-frame and that really does seem to work.  Thanks for that.

Thanks also for working on the fix.  I imagine this issue will show show when you're done with the fix.  How will we know when the fix makes it to the auto-update world?

Thanks again,

- Adam

At minimum I hope to get the fix into M-60. We will have to decide whether or not to merge it to M-59 at this point. Star this issue to receive updates.

Thanks Steve!

CL is in the comit queue:
https://codereview.chromium.org/2958833002/

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/aff0615b647e2250ae368dc8a808e615fba4e3e8

commit aff0615b647e2250ae368dc8a808e615fba4e3e8
Author: stevenjb <stevenjb@chromium.org>
Date: Mon Jun 26 22:50:26 2017

Settings: Network: Specify a default IPCofig when not set

This prevents an invalid static setting with empty values, and
fixes the logic to send an update any time the 'automatic'
setting is toggled.

BUG= 733848 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2958833002
Cr-Commit-Position: refs/heads/master@{#482444}

[modify] https://crrev.com/aff0615b647e2250ae368dc8a808e615fba4e3e8/chrome/browser/resources/settings/internet_page/network_ip_config.html
[modify] https://crrev.com/aff0615b647e2250ae368dc8a808e615fba4e3e8/chrome/browser/resources/settings/internet_page/network_ip_config.js

I verified this locally; the fix is CrOS specific and pretty small / isolated.

Starting with Merge-Request-60. I'd kind of like to merge it to 59 too in case we do another 59 update, but there is a work around so it is not the end of the world if we don't merge it to 59.

This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Ping? This is a very isolated CrOS specific fix that is critical to a handful of users.

Changing the milestone to M-60 to make it clear that this is a merge to 60 request.

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cae8f7fefc24b6294e6347efeedc4dc077d9864c

commit cae8f7fefc24b6294e6347efeedc4dc077d9864c
Author: Steven Bennetts <stevenjb@chromium.org>
Date: Fri Jul 14 17:33:12 2017

Settings: Network: Specify a default IPCofig when not set

This prevents an invalid static setting with empty values, and
fixes the logic to send an update any time the 'automatic'
setting is toggled.

BUG= 733848 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
TBR=stevenjb@chromium.org

(cherry picked from commit aff0615b647e2250ae368dc8a808e615fba4e3e8)

Review-Url: https://codereview.chromium.org/2958833002
Cr-Original-Commit-Position: refs/heads/master@{#482444}
Change-Id: Ib3a7c82ad75063d48e1f59f326229b35f9503194
Reviewed-on: https://chromium-review.googlesource.com/572029
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/branch-heads/3112@{#608}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
[modify] https://crrev.com/cae8f7fefc24b6294e6347efeedc4dc077d9864c/chrome/browser/resources/settings/internet_page/network_ip_config.html
[modify] https://crrev.com/cae8f7fefc24b6294e6347efeedc4dc077d9864c/chrome/browser/resources/settings/internet_page/network_ip_config.js

I don't think it is safe to merge this to 59 at this point. We will have to direct users on 59 to the workaround (using the chrome://settings-frame UI).

This still doesn't work, and chrome://settings-frame is no longer recognized.

Google Chrome	69.0.3497.95 (Official Build) (64-bit)
Revision	e3a5f87b64d44c4b311d2458f16b9f469e2597fb-refs/branch-heads/3497@{#931}
Platform	10895.56.0 (Official Build) stable-channel cave
Firmware Version	Google_Cave.7820.384.0
Customization ID	ASUS-CAVE

The original repro for this is no longer valid. Neither is chrome://settings-frame.

Please create a new issue with a bug description / repro describing your specific problem, thanks!