Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, December 13, 2016 12:28 PM | 1 vote
Am I correct that the Windows feature "Bridge connections" that enables to bridge two Ethernet adapters, does not support DHCP for the machine sharing the adapter?
When I configure it, DHCP no longer seems to work.
Is this a limitation of the bridge?
All replies (5)
Wednesday, December 14, 2016 1:55 AM | 1 vote
Hi,
Your thought is reasonable, from my survey, Network Bridge is very similar to the Internet Connection Sharing (ICS) feature, but they're not the same.
When we use Internet Connection Sharing (ICS), we will convert our computer into a router, which uses a built-in DHCP server to assign IP addresses to computers participating in ICS. It also offers Network Address Translation (NAT) that allows multiple devices to connect to the network using the ICS host as the middle man.
On the other hand, Network Bridge doesn't turn the host computer into a router and you won't get Network Address Translation. It only provides a medium (bridge) in which other devices can connect directly to the network and obtain the same IP address scheme every other computer connected to the network is using.
In addition, please refer to this documentation for more information.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, December 14, 2016 12:27 PM | 1 vote
I don't want to do Internet Connection Sharing (ICS), I would like to bridge two small local networks using a dual port Ethernet on the bridging PC. One of the networks has a DHCP server, the other does not.
Is my observation correct that the bridging PC can no longer gets an IP address from the DHCP server when its two Ethernet ports are in bridging mode? It seems a bit strange, as it can be easily configured, in fact it is the default and it does not work. but e.g. http://www.windowscentral.com/how-set-and-manage-network-bridge-connection-windows-10 also states it works only with fixed IP addresses.
Regards
Friday, December 16, 2016 9:29 AM | 1 vote
Yes, I think your conclusion is correct, bridging PC can’t gets an IP address from the DHCP server. As the link you mentioned, the configuration is simple, but in that link the scenario doesn’t involve DHCP server.
Reagrds
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Sunday, October 29, 2017 6:26 PM | 1 vote
Yes, I think your conclusion is correct, bridging PC can’t gets an IP address from the DHCP server. As the link you mentioned, the configuration is simple, but in that link the scenario doesn’t involve DHCP server.
I don't want to do Internet Connection Sharing (ICS), I would like to bridge two small local networks using a dual port Ethernet on the bridging PC. One of the networks has a DHCP server, the other does not.
Is my observation correct that the bridging PC can no longer gets an IP address from the DHCP server when its two Ethernet ports are in bridging mode? It seems a bit strange, as it can be easily configured, in fact it is the default and it does not work. but e.g also states it works only with fixed IP addresses.
Regards
I'm sad I lost my original post that I spent almost an hour typing - I decided to take a screenshot on my PC, and then I bluetoothed it to my phone to show proof of the setup, and thats when I lost the post. This will also be my first constructive / non-abusive post... in comparison to the MS Answers forums, where I slag off on clueless people with MSFT tags... you will see below why I am easily annoyed with unhelpful answers ;) (sfc /scannow is not a one solution fix all)
Here goes trying to rephrase everything..
====================
Hello Teemo and mooiweergezicht,
I wanted to reply to you both, and say that you are both correct, but also misinformed.
I'm not an IT Professional, I'm just a older student now, but I learned this while I was in highschool to circumvent the school network so our class could play network games on the school computers, and I wanted to share it with you both.
When a network bridge first starts, it assigns itself an IP address. Any devices connecting to the bridge must use the correct address range and subnet for valid transmission.
If a bridge has active ports when it starts, it counts the ports, then requests an address. If there is no response, it will assign itself an address. If there are multiple ports active and the device receives multiple requests to assign an address, it will either assign the first address given, or ignore all requests, and assign itself an address. If a response is received from a connected DHCP, an address is assigned to the bridge and the bridge then uses this configuration to allocate the rest of the available ports.
You will almost never be in a scenario where you have a computer that is hard-wired to two different networks, without it being connected to one server. If it is, that is poor network architecture.
You also can never have (you can, but they need to communicate with each other to know which addresses are available) more than one DHCP on a network, if there is, it's also poor networking structure.
Knowing this, you can manipulate the sequence of events to your advantage.
A user will always be in control of when a port on the bridge can be connected or disconnected.
If a bridge has a port connected to a network with a DHCP, when the bridge starts, the DHCP will assign the bridge an address. You can then connect devices to the bridge, and depending on how you set up the bridge, the devices connecting can either use the bridge as a passthrough to the DHCP or the bridge can act as a mediator for the DHCP and assign the devices an address and validate it with the DCHP, or the bridge can act as a gateway to another network. For general purpose home networking without any major need for security, you can assume that one of your networks could be to a mobile device, and then pre-configure the bridge to accept the default IP range and subnet for the mobile.
For example: Android uses 192.168.43.X / 255.255.255.0
You can then have this address range as secondary address, for the bridge to act as the gateway to other networks. As I mentioned above, there should only be one DHCP, so the DHCP could also be set up to give the bridge a fixed address, or if an address range is known, the bridge can be configured with the address range for the DHCP network, and also, the address range for the external network. There's a limit to the number of internal switching the bridge can do - off the top of my head I can't remember, but if you're trying to do more than 4 networks on that single software bridge... you're probably not doing anything in a commercial environment, and you're doing some crazy tinkering like this:
I have a Network bridge for Hyper-V, Wireless, Ethernet, Bluetooth, Thunderbolt Ethernet, and at the same time also have a DLNA host on my laptop. I can either use Wireless to connect to the internet, or have it tethered from a phone, or use the Bluetooth to tether an internet or... actually anything in any order I want. Then I have my Xbox running to my laptop's ethernet, and I have a NAS connected by Thunderbolt GBE, and this NAS has a Dual NIC... that if I really wanted to, could do exactly the same to another network... this is what it looks like when it all comes together
https://imgur.com/a/DxFRshttps://i.imgur.com/GJSYlP3.png
Now I don't have the Xbox turned on right now, but you're just going to have to trust me that it connects ;)
and now... after typing all that again, I actually know what that popup message said on my phone when I tried to add the picture, and it says, I cannot add pictures or links until I get verified ;)
Take that forum... workaround via quote.
NB FTW.
FYI It was no where near as easy as this when I did it at school to have Quake wars with people in the library, classroom and computer room - because advances in WinNT and CISCO
EDIT: PS. This is also a reason why when the iPhone first came out and people said... 'Nah you can't tether' .. I laughed... because I was tethering Symbian on Nokias. ;)
double edit: ooh i forgot to mention, on windows 10 with certain wireless cards, you can also put wireless-direct in to play.
You can also use it to bypass ... um xbox MHL/HDMI security to watch pirated game of thrones because foxtel sucks in australia. ;)
(now you know why the xbox is there huh :P )
triple edit: disclaimer: at least i'm honest.
Monday, October 30, 2017 1:16 AM
@NeoBeum,
Your detailed explanation is meaningful, but I advise you post a new case on TechNet Windows 10 Networking forum for discussing. Reply on the old case may lead to your thought can’t be found by forum users and communities.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].