Same here so I guess that's not correct approach in this context. Soo... just enable ICS (with NAT), choose adapter you like to share Internet through and, "Allow other network users to control... bla, bla..." is not really important unless someone has access to main pc. You could probably set up a share on main pc accessible from both client on NAT network and real network too... with some fiddling.
@Sajjo - Once the bridge was all set up it seemed a tiny bit faster than ICS with NAT on speed tests. Hardly enough to worry about. If you don’t get the bridge set up right it will indeed kill the internet on your main pc. Also, just for giggles, I installed openwrt as a guest on Virtualbox, and gave the guest 2 virtual nics bridged to my 2 physical nics. That was fun, and worked if I didn’t get the wan and lan settings crisscrossed. Slower by about 20% than with ICS.
But it worked for you? I was not so lucky, main pc got screwed so surfing was a nogo... Yeah, I might did something wrong here...
@CaptainKirk1966 Feel free to edit my post(s) too if needed, just so it makes sense for others. Does this thread deserves a "Solved" marker?
Solved?? - well. I'm not the OP, but I think he also got it working by setting up static ip's on one of his nics. The bridge setup seems tricky, since it is the bridge device itself that needs to have proper ip configuration, and not the individual nics in the bridge. The sharing approach - share intenet connected nic with another - and let Windows create a new NAT network - seemed easier to me.
But i agree. Topic was sharing through ICS, that seems to me solved. Bridge setup, far as i understand from Microsoft's tutorials, is not how it was intended regarding ICS, more like a deep dive into the topic with nerds on MDL. All hail new knowledge
An LTSC issue?? fwiw: I put 2024 Enterprise LTSC (26100.7840) into a vhdx today. When I boot my machine from that, I also have a devil of a time getting internet sharing to work.
This isn't fully solved for me yet. It seems every time I either restart my xbox or PC, I lose the sharing. I can't find a solution to this.
@jackching Since both Cap and I have played around this solution, could you expand on your current setup in details? The more details the better we can try replicate and understand this behaviour. Should be noted that I don't have a xbox 360 to test against, that could maybe limit our full understanding. (i do have some older Cisco hw floating around that could possible simulate a similare client connection to some extent)
https://forums.mydigitallife.net/th...sharing-between-two-ethernet-nics-ltsc.90103/ The usb to ethernet goes to the xbox 360. I dont know what else to expand on this. Sharing doesnt work correctly on windows 11 ltsc
So, if i install the Windows 11 LTSC (no tweaks) and with latest updates, ICS with default settings - dhcp on client, i would be in the ballpark of your setup? I have several brands of usb nic's to test as well (both usb 3 and 2) I will see if i'm "lucky" and loose connection...
Yes, it drives me nuts. Just when I think that ICS is working, I find it times out and/or doesn't survive a reboot of the host machine. The most reliable is no doubt using a separate physical switch or router, as Enthy suggested earlier. The second best is probably run router software in a virtual machine, and launch that vm as needed, or automatically on each reboot.
Did'nt bother to reinstall to Windows 11 LTSC yet, my Windows 11 25H2 Enterprise is so far good for this experiment. I get the same issue. Rebooting host and ICS's NAT looses some translations... the bugger is somewhere here. Both nic's are set to dhcp and ICS's dhcp works fine - 192.168.137.xxx/24 every time. Atm, this works: disable ICS sharing and save. Then set up share again and you are connected. Then reboot host and NAT is again not working. Not done yet... Not for me but I may not have waited long enough...
Yeah, I was doing exactly that after reboots to get it working again. Time outs may be with power plan settings, but I'm quickly losing interest in any of this. Openwrt in vmware guest, with bridged connections to the physical nics, works amazingly well, no perceptible speed loss. Openwrt in virtualbox guest, bridged to the physical nics, is quite slow by comparison.
That could very well explain your experience, did not test that putting to sleep or hibernate. I had it running overnight ~ 10 hours (I need my beauty sleep ) and no loss of connection during that time. Fyi.