Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Unreliable network bridge - Windows Server 2008 R2 Web Edition

Posted on 2011-03-11
3
Medium Priority
?
1,711 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 2000 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

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
How to fix a SonicWall Gateway Anti-Virus firewall blocking automatic updates to apps like Windows, Adobe, Symantec, etc.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…

972 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