.NET (29) Archiving (10) ASP.NET (9) Books (3) C Sharp (30) Code Generation (3) Dasblog (16) Design Patterns (4) Development (37) Exchange (14) Family (10) GPS (7) Hardware (10) mixuk07 (1) Mountaineering (7) MSCRM (6) Office (3) Outlook (13) Personal Development (4) PHP (4) PowerShell (7) Productivity (9) RSS (15) Running (2) Scripting (20) SCRUM (3) Service (3) Software (60) Support (17) TaHoGen (2) Technical (50) Tools (13) Twitter (5) Web (16) Windows 7 (4) Windows Mobile (10) WS* (1)
Sign In
So before Christmas I bought an Xbox 360 (60GB HDD version). Reasoning was "it will be good for the kids hand eye coordination" which in reality was a thinly veiled "I want one and the kids might like it too" (as it turns out they don't)...
Anyway, one of the first tasks was networking it -linking it to the home PC and DSL router. I read a bunch of stuff online about the Xbox wireless adapter being over the top and the same could be done with any old wireless router that you had lying around around - so, having an old WRT54G lying around that was my first step.
It was pretty successful in that I already had reflashed it with DD-WRT firmware and it was pretty simple getting the wireless side acting as a client to my Linksys WAG160N and the unit bridging connections from the LAN side. Now this configuration requires that you set the LAN side side up on a different subnet to the existing (wireless) network - otherwise the routing gets screwed up. i.e. The LAN side might be on 192.168.2.X while the existing router is on 192.168.1.x (this is what routing is all about - Xbox gets an address of 192.168.2.x and a default GW of 192.168.2.1, the router bridges any data sent to 192.168.2.1 over to the wireless side which has an address of 192.168.1.xxx and a default GW of of 192.168.1.1 that then bridges it over to the WAN side of the DSL connection that then routes it to the Internet...
This worked fine initially, I could connect to Xbox Live and the like, but where it fell down was on the connection to the Media Centre PC - for some reason any Media Centre PC must be on the same segment as the Xbox (which is not the case here as Xbox = 192,168.2.x and MCPC = 192.168.1.x). It does this to make 'discovery' of the MCPC easy fro an Xbox, but I am surprised (read disappointed) that there is not an advanced / manual setting that allows the user to specify the IP address. I reckon this is around needing a good quality network connection between the devices (which is generally the case if they are on the same subnet, but not always when on different subnet's), but a simple disclaimer could have sufficed.... It forces users into either running an Ethernet cable, buying a wireless adapter or living without media centre capability.
Anyway I caved and bought an Xbox wireless adapter, but the speeds are still not up to streaming HD TV, so now I'm considering powerline adapters (Homeplug) - be glad to hear of any experiences you have with this...
Remember Me
a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u