Computer Hardware Forum

After hours of trying to get the Windows Media Connect or Media Center
Extender to function properly... I have finally blindly stumbled onto a
fix.

If you are getting the error message "Xbox 360 Not Found" when you try
to get the www.xbox.com/pcsetup configured... make sure that your
network card is not configured to use multiple IP addresses.

It blows me away that this was the cause of the problem and not some
third party bug, application or firewall related issues. What is even
more interesting is the fact that its NOT MENTIONED anywhere that I
could find, (and believe me I know how to use Google, and crawl under
every single rock to find the answers I need) that using multiple IP
addresses assigned to a single NIC will make it impossible for the
pc/360 to communicate.

Interestingly, this was not a problem with the older Extender Manager
Software or the first generation Media Center Extender for Xbox Kit, as
I had used it on the same computer with 10 IP's mapped to a single
NIC without a problem.

I have not tried the scenario of using multiple NICs each with a single
IP yet (as the case would be if you have both a 100mbit wire and 54mbit
wifi, as I do) but a using a single NIC with multiple IPs will NOT WORK
GUARANTEED.

Report this post to a moderator

[  Post Follow-up to this message ]

"horia.lambrache@gmail.com" wrote:

> After hours of trying to get the Windows Media Connect or Media Center
> Extender to function properly... I have finally blindly stumbled onto a
> fix.
<snip>
> I have not tried the scenario of using multiple NICs each with a single
> IP yet (as the case would be if you have both a 100mbit wire and 54mbit
> wifi, as I do) but a using a single NIC with multiple IPs will NOT WORK
> GUARANTEED.

I would just like to add that this is the case for me, as well as many other
360 users.  I would very much hope that a fix for this will be forthcoming i
n
a new version, as it seems like a very basic issue to overlook.

Report this post to a moderator

[  Post Follow-up to this message ]

I'll forward this on to the Dev Lead for WMC.

N ow, there must be something more to this than simply having multiple IP
addresses.  That was true for me the entire time that WMC v2 was in
development. I had two network cards in every one of my development
workstations and test machines.  From the first check-in to the day we
shipped to the possible QFE's that I coded and checked in that aren't
released yet there were two active network cards on my computer.  One NIC
was connected to corpnet and another connected to a private network on a NAT
router on my desk.  This was also the standard dev configuration for WMC v1.
In addition to multiple netowrk interfaces we also did a bunch of work to
support IPv6.  So at least one of the network cards had both an IPv4 address
and an IPv6 address.  So, networking issues were at the front of our minds
as we worked on this.

So, in light of that, could you provide some more details on your exact
setup?  How many network cards?  How many IP addresses per card? How was
each configured?  Who made them?  What version of the drivers do you have
installed?  What EXACTLY did you do to get it working again?  What else did
you do that the same time that you changed the network configuration?  Did
you change it back to the "broken" state to confirm the cause?

Regards,

--
Alan Ludwig
Lead Software Development Engineer
Windows Core Operating System
Microsoft Corp.

This posting is provided "AS IS" with no warranties, and confers no rights.

"Robbo" <Robbo@discussions.microsoft.com> wrote in message
news:4621F447-25FE-4D9D-925B-BE16E88837FC@microsoft.com...
>
>
> "horia.lambrache@gmail.com" wrote:
> 
> <snip> 
>
> I would just like to add that this is the case for me, as well as many
> other
> 360 users.  I would very much hope that a fix for this will be forthcoming
> in
> a new version, as it seems like a very basic issue to overlook.

Report this post to a moderator

[  Post Follow-up to this message ]

I'm sitting here after a reboot waiting for WMC to trawl through my 60-odd G
B
of mp3s (it couldn't just save whatever database of file info, then just
check for changes next time?  I have to wait every time I reboot?  I suppose
that's for another thread.), so I'll reply straight away.

"Alan Ludwig" wrote:

> Now, there must be something more to this than simply having multiple IP
> addresses.  That was true for me the entire time that WMC v2 was in
> development. I had two network cards in every one of my development
> workstations and test machines.  <snip>

For me, the problem was having two IPv4 addresses on one NIC.  After banging
my head against everything I could think of, I thought I may as well remove
one and see what happened - the 360 found the PC straight away.

> In addition to multiple netowrk interfaces we also did a bunch of work to
> support IPv6.  So at least one of the network cards had both an IPv4 addre
ss
> and an IPv6 address.  So, networking issues were at the front of our minds
> as we worked on this.

I'm glad to hear that was the case.  It's heartening to be engaging in
conversation about this with MS, and I'm glad that you're keen to deal with
the issue, so thanks in advance for that.

I don't even have IPv6 support installed on my NICs, so please assume
everything I say is all IPv4.

> So, in light of that, could you provide some more details on your exact
> setup?

As I said above, I'm still waiting for WMC to finish indexing or whatever
it's doing, after which I'll be able to say a bit more about the 2 NIC
situation.

> How many network cards?

One

>How many IP addresses per card?

Two

>How was each configured?

I have a home network on the 192.168 range, with a DSL router connected to
it, acting as a gateway.  I have a small (255.255.255.248) public IP subnet.

Configuration:

IP Addresses:

192.168.0.123
My public IP

Default gateway:

Router (192.168 address)

DNS:

Router (192.168 address)

> Who made them?

I have confirmed the above with both onboard NICs on my motherboard.  An
nForce 4 nvidia NIC, and a Marvell NIC.

> What version of the drivers do you have installed?  4.8.2.0 and 8.41.1.3  respecti
vely.  Both are WHQL certified.

> What EXACTLY did you do to get it working again?

Removed my public IP from the NIC.

> What else did  you do that the same time that you changed the network configuratio
n?

Nothing afaik.

>Did you change it back to the "broken" state to confirm the cause?

Yes, re-adding the IP stops the 360 from being able to connect.

Hope the above helps.  I'll post again with more configurations' results
when I'm able to.

Jon

Report this post to a moderator

[  Post Follow-up to this message ]

"Robbo" wrote:

> Hope the above helps.  I'll post again with more configurations' results
> when I'm able to.

Just to add to the above, I've since tried using both NICs, with the 192.168
address on one, and the public IP on the other, and WMC worked fine.

So for me, having two IPv4 IPs on one NIC consistently stops the 360 from
finding WMC.

Let me know if you require any more information from me.

Cheers,

Jon

Report this post to a moderator

[  Post Follow-up to this message ]