Solved

Unreliable network bridge - Windows Server 2008 R2 Web Edition

Posted on 2011-03-11
3
1,666 Views
Last Modified: 2012-06-27
I have a server running Windows Server 2008 Web. The machine has two NICs, and I had them bridged. The bridge seems to more or less work fine, until I reboot the machine. After coming up from a reboot, the network bridge shows the machine with a 169 IP address on an unknown network. Attempting to renew the IP address fails with an unknown error. If I delete the bridge and recreate it, the new bridge will work fine once again until a reboot.

I deleted the bridge and rebooted the machine, and the individual NICs work fine.

Windows Firewall is disabled on the machine. It's currently just running inside my LAN. It's set to DHCP, with a DHCP reservation set with for the bridge's MAC address. Any ideas as to what causes this or how I can fix it?
0
Comment
Question by:elorc
  • 2
3 Comments
 
LVL 57

Accepted Solution

by:
giltjr earned 500 total points
ID: 35116922
First, are you sure you want to bridge these interface?  Bridging is used to connect two seperate networks together.

Typically people do not use a Windows box to bridge networks.  

They may team them so that to Windows it looks like there is 1 network interface with 1 IP address.  This allows for redundent connections to the network and provide extra bandwidth.

Which interface is connected to the network that has the DHCP server?

If you really want a bridge, normally you would configured it with a static IP address.

0
 
LVL 1

Author Closing Comment

by:elorc
ID: 35148514
I ended up just removing the bridge. It was being too weird and I decided it's not worth pursuing anymore. My understanding was that by bridging the NICs through Windows it would share the bandwidth. We've done this with a number of our Windows Server 2003 machines and never had an issue like this, so it is very strange.
0
 
LVL 57

Expert Comment

by:giltjr
ID: 35149863
Bridging will not allow you to share bandwidth, NIC bonding/teaming will allow that computer to use both NIC"s at the same time, which will increase the amount of bandwidth to/from that single computer.

If you understand a little bit about IP routing, a bridge is the same thing as a router, except a bridge works at layer 2 (Ethernet) instead of layer 3 (IP).

You can think of a bridge literally  like a real bridge.  That is you have two roads (networks in this case) that end on each side of a river and a bridge joins them together.  

NIC bonding/teaming is more like adding additional lanes to and existing road so it can carry more traffic.
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Let’s list some of the technologies that enable smooth teleworking. 
If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now