XP Bridging

Soldato
Joined
18 Oct 2002
Posts
21,547
Location
Cambridge, UK
Hi,

So as per the diagram I'm trying to move from a setup where I use ICS to bridging the two networks together. At the moment the Xbox360 lives on a seperate logical network using ICS and this is causing some problems with using the 360 as an extender.

xpb.jpg


The problem is when I bridge the two connections together (one is wireless the other wired) and set the IP of the bridge to be 192.168.2.2 (or anything else for that matter) XP complains and tell me there are "IP conflicts" which there aren't :confused:

HEADRAT
 
Last edited:
Well this is exactly what I have done, static addresses on the PC and Xbox but I get a "duplicate IP" warning and it doesn't work!

From 192.168.2.2 I can't ping 1921.168.2.1 (Router) or 192.168.2.3 (Xbox).

HEADRAT
 
I know there is nothing else on the network with the IP specified and the DHCP server is off, I'm not using Internet Connection Sharing I'm using bridging they are different things.

ICS = Alllows one machine to connect through another if they are on logically seperate networks.

Bridging = Making two seperate physical networks (e.g. wired ethernet + wireless) into one network.

HEADRAT
 
Phnom_Penh said:
AFAIK they need to be on the same subnet. What's the IP of the modem?

Well everything up to and including the router (not the modem itself) is in 192.168.2.0 255.255.255.0.

Yep one is down in the lounge, the router is upstairs, I followed the instructions I have found exactly but I'm still getting coflicting IP (whatever IP I set it to) and its doesn't work :confused:

HEADRAT
 
Something like that, the router will take care of that, the problem is that I keep gettting duplicate IP warnings and I'm not able to ping the default gateway of 192.168.2.1 or the Xbox on 192.168.2.3.

HEADRAT
 
But I've manually set the IP's :-

Router 192.168.2.1
MCE 192.168.2.2
Xbox 192.168.2.3

there is no DHCP on, everything is manually assigned.

HEADRAT
 
Sorry I don't follow you, at the moment I've deleted the bridge, every time I try and set the bridge it doesn't work and complains about dupl. IP's

HEADRAT
 
Well I've got to leave the Media Center in the equation as it's how the 360 derives it connectivity but I had already done just that, turned everything else of other than.

Cable Modem >---- Router >---- Media Center >---- 360 no joy :(

I can make it work with ICS but then that kills the extender functionality of the 360 so this is why I want to use bridging instead of ICS.

HEADRAT
 
Exacty the same thing it complains about a conflciting IP whatever IP I put it on, this is driving me potty ;)

HEADRAT
 
In the bridge miniport settings, you can't change the IP in either of the NIC's as they are part of the bridge.

HEADRAT
 
zen62619 said:
Your going about it the wrong way, theres no need to use ICS, buy a 4 port hub for about 5 quid or even less from ebay if your lucky.

Well I'm not using ICS I'm using bridging and I need to use wireless as the MCE is downstairs and the AP is upstair!

HEADRAT
 
just_grass said:
double check the new bridge is also set for dhcp.

then add the one connecting the router.

Not sure what you mean here, basically you set the bridge up by ctrl clicking on each of the NIC's and selecting "bridge" so how do I then "add the one connecting the router."?

HEADRAT
 
OK they say a picture speaks a thousand words so here is me trying to setup a bridge with my wireless NIC:-


1.jpg


Working wireless connection to AP so all looks good there.

2.jpg


Briding the two connections together

3.jpg


As you can see no DHCP address has been found as miniport adapter as 0.0.0.0 (later goes to 169.xxx.xxx.xxx) :(

4.jpg


Compatability mode definately set.

Now I've tried the same thing using two wired NIC's in another PC with the 360 and its works fine and as you would expect so it got something to do with the wireless NIC IMHO.

HEADRAT
 
Windows IP Configuration

Host Name . . . . . . . . . . . . : loki
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Network Bridge (Network Bridge) 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 02-13-D4-30-C3-DF
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.169.93
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

If I manually set the IP on the miniport this is when I get the duplicate IP errors.

just_grass said:
also try setting the IP of the bridge to another SUBNET say 10.2.0.49/255.255.0.0 - see what that says. (yes it wont work but see whether it accepts it)

So I tried 10.10.10.1 (255.255.255.0) and I get duplicate IP errors, there is no way this can be as I've never used the range for anything!

I've just tried it turning the Router off and I don't get any duplicate IP errors, if I turn it back on I do so it seems to be something between the AP and the way the briding works not the wireless NIC itself!


HEADRAT
 
Last edited:
To be honset I'm going to admit defeat on this and I'm just going to run a network cable downstairs, I've been theatening to do it for ages and this the "straw the broke the camels back". I'm copying extremely large files down to my MCE so I think I'm going to go the GigE route as even a Pre-N wireless network isn't fast enough when you're copy files that are 10GB ;)

HEADRAT
 
Back
Top Bottom