Same issue here.
No makes nor models. It's an assembled PC using purchased components. Intel i7 on a Gigabyte motherboard. I have an Intel Gigabit CT adapter as
LAN and an Bigfoot Killer as METRO connection.
A third virtual adapter (PPPoE) tunnels over METRO connection and the connection is shared via
LAN.
The connection is shared, connected, and APPEARS in order, but will not route. As per usual.
a) Disable sharing the connection.
b) Hit OK to the warning that you need to reconnect.
c) Enable sharing the connection (Share to: LAN)
d) Disconnect and reconnect the internet link (PPPoE)
e) Magic!
And it will keep magicking until restarted.
This is a separate issue from the error when sharing the connection and separate from the pre-anniversary update, in which ICS would not work until connection was reconnected 10 minutes after system boot, when the sodding ICS services would finally get to
it.
Reconnecting the connection will NOT resume service, the connection needs to be un-shared and the re-shared.
Warning, rant.
ICS is a joke, has been since W8 and a base function of the OS is treated like an afterthought.
Linux: Masquerade
echo "1" > /proc/sys/net/ipv4/ip_forward
Restarting procedure: NONE. Just Works.
---------------------------------
Mac: Internet Sharing
Combobox: Share From (list of interfaces)
Combobox: Share To computers using: (List of interfaces)
<OK>
Restarting procedure: NONE. Just Works.
---------------------------------
Windows:
* Right click in tray, open Network and Sharing Center
OR
Win+I, Network, Status, Network and Sharing Center
OR
Win, n, e, t, w, o, r, k, space, a, n, d, space, s <enter>
* Change Adapter Settings
* Find your adapter (I have 9)
* Right click, Properties.
* Select "Sharing"
* Check "Allow other blah blah"
* Select your other connection from the combobox. (Hope you named them. No MAC, IP or identifier is used. Network 1, Network2, Network 3)
* Click OK.
* Won't work.
* Disable the connection
* Enable the connection.
* Go back to properties and marvel at the comobobox now being an edit box.
Restart procedure:
1) Sigh heavily.
2) Restart PC
3) Notice wifi/HTPC/IoT/devices are all dead.
4) Physically go to the PC, you can't do this remotely because it requires manual reconnect (Step 29).
5) Win+I
6) Network and stuff
7) Status
8) Network and Sharing Center (Hop to old UI)
9) Change Adapter Settings.
10) Select Adapter
11) Right Click
12) Properties
13) Sharing tab
14) DISABLE sharing.
15) OK.
16) OK (warning, you need to reconnect to blah!)
17) Right Click
18) Properties
19) Sharing tab
20) ENABLE sharing.
21) OK
22) OK (warning, you need to reconnect to blah!)
23) Right click
24) Connect/disconnect
25) Marvel at the Metro interface being open with the VPN tab, because reasons.
(Hop back)
26) Click Dial-up
27) Select the connection you wish
28) Click Disconnect
29) Click Connect <<< CANNOT BE DONE THROUGH THE INTERNET REMOTELY
30) With a bit of luck, your ICS is up and running again.
31) You need some updates/You need to restart/This is Windows Home so **** you, I'm restarting anyway. Next morning, it's all dead again.
So just follow these easy 30 steps and Internet Connection Sharing, one of the easiest things to do, can be yours in a jiffy.
Here's a simpler version, however:
1) Install VMWare, VirtualBox or any other emulation software.
2) Quick-deploy an image of Linux(Masquarade), MacOS(Internet Sharing), or Windows before 8 (ICS).
Done. I'm not even joking. My old W7 license is still relevant today, as I can donate 512M of RAM out of my i7, 5GHz PC with 8G of RAM to a VM that sits in the tray and works as a router, connection sharer, firewall, resource monitor and many others. For
the price of a tab in Chrome. Less if it's YouTube.
This is ridiculous. Microsoft, please.
"Hi, son? It's mum. Wifi's down"