Multiple MN-740s System Link Problem

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Greetings,

I recently bought a second xbox and added it to my network
with a second MN-740 wireless bridge, so both of my units
are connected to the network with their own MN-740 bridge.

They both work fine independently, but I cannot get them
to communicate together for system link play, when BOTH MN-
740s are present on my network. I can start and see a
game between the units, but the connection will be
immediately lost, then back on, lost, and so on.

If I remove one of the MN-740s from the network, hook the
second xbox directly into a hub, it works fine, but as
soon as I add the second MN-740, the failures start right
back up, even if the MN-740 isn't even connected to the
xbox. Its sheer presence on the network immediately
causes failure. Like there is some sort of conflict
between the 2 units that confusing the network.

Can 2 MN-740s only work together, for system link play, in
ad hoc mode? Doesn't seem to make sense to me that this
would be the case, but I'm at a loss otherwise.

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

They're 2 floors apart, so unforunately, this isn't an
option for me.

Actually, I didn't mention this in my post, but the second
MN-740 is on a switch, with my XBOX and Tivo hooked into
the switch as well. Though, in testing, regardless as to
whether the second MN-740 is connected in via a separate
port on the switch, or directly into the XBOX (with the
switch eliminiated), either way, attemping a system link
game fails.

Are you confirming, based on your reply, that System Link
won't work in infrastructure mode across 2 wirless MN-740
bridges?


>-----Original Message-----
>How close ar the 2 MN-740's? If they are close enough
you could use a
>switch or an evil hub between the wireless bridge and
them.
>
>John wrote:
>> Greetings,
>>
>> I recently bought a second xbox and added it to my
network
>> with a second MN-740 wireless bridge, so both of my
units
>> are connected to the network with their own MN-740
bridge.
>>
>> They both work fine independently, but I cannot get
them
>> to communicate together for system link play, when BOTH
MN-
>> 740s are present on my network. I can start and see a
>> game between the units, but the connection will be
>> immediately lost, then back on, lost, and so on.
>>
>> If I remove one of the MN-740s from the network, hook
the
>> second xbox directly into a hub, it works fine, but as
>> soon as I add the second MN-740, the failures start
right
>> back up, even if the MN-740 isn't even connected to the
>> xbox. Its sheer presence on the network immediately
>> causes failure. Like there is some sort of conflict
>> between the 2 units that confusing the network.
>>
>> Can 2 MN-740s only work together, for system link play,
in
>> ad hoc mode? Doesn't seem to make sense to me that
this
>> would be the case, but I'm at a loss otherwise.
>>
>
>.
>

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Hi Chris,

Thanks for your reply. I aplogize for my apparanet
ignorance, but I don't recall a direct 'System Link'
setting / option available via the dashboard (I'm not at
home right now to check).

I do recall selecting "infrastructure" versus "ad-hoc".
Are you equating "ad-hoc" to "system link" mode? This
would be a real pain in the butt if I have to change
between these each time...

>-----Original Message-----
>When you're on the Internet portion of the connection,
you're using
>Infrastructure as the setting, so you're getting Internet
feed to Xbox Live!
>Go into the Dashboard on each Xbox and set them to System
Link.
>--
>Chris H.
>Microsoft Windows MVP
>Tablet Creations - http://nicecreations.us/
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>
>"John" <anonymous@discussions.microsoft.com> wrote in
message
>news:1bf301c443f6$bd9cc440$3a01280a@phx.gbl...
>> Greetings,
>>
>> I recently bought a second xbox and added it to my
network
>> with a second MN-740 wireless bridge, so both of my
units
>> are connected to the network with their own MN-740
bridge.
>>
>> They both work fine independently, but I cannot get them
>> to communicate together for system link play, when BOTH
MN-
>> 740s are present on my network. I can start and see a
>> game between the units, but the connection will be
>> immediately lost, then back on, lost, and so on.
>>
>> If I remove one of the MN-740s from the network, hook
the
>> second xbox directly into a hub, it works fine, but as
>> soon as I add the second MN-740, the failures start
right
>> back up, even if the MN-740 isn't even connected to the
>> xbox. Its sheer presence on the network immediately
>> causes failure. Like there is some sort of conflict
>> between the 2 units that confusing the network.
>>
>> Can 2 MN-740s only work together, for system link play,
in
>> ad hoc mode? Doesn't seem to make sense to me that this
>> would be the case, but I'm at a loss otherwise.
>>
>
>
>.
>

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

I searched through the forums at Xbox.com and one of the suggestions is to
clone each Xbox MAC address to the respective MN-740. I haven't done this,
not having a second Xbox at the present time, and only using a System Link
cable previously.
--
Chris H.
Microsoft Windows MVP
Tablet Creations - http://nicecreations.us/
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone


<anonymous@discussions.microsoft.com> wrote in message
news:13c9f01c44410$ef618e10$a101280a@phx.gbl...
> Also, one other point, to confuse the matter worse, is
> that I don't have to change any values / settings, i.e. I
> always leave in standard infrastructure mode when
> connecting both xboxes in a wired environment, i.e. both
> connected to a switch, and it works just fine...
>
> Or, one wirless, via the bridge, one wired, it also works
> just fine. Just by powering up / adding the second
> bridge, all "heck" breaks loose...
>
>>-----Original Message-----
>>Hi Chris,
>>
>>Thanks for your reply. I aplogize for my apparanet
>>ignorance, but I don't recall a direct 'System Link'
>>setting / option available via the dashboard (I'm not at
>>home right now to check).
>>
>>I do recall selecting "infrastructure" versus "ad-hoc".
>>Are you equating "ad-hoc" to "system link" mode? This
>>would be a real pain in the butt if I have to change
>>between these each time...
>>
>>>-----Original Message-----
>>>When you're on the Internet portion of the connection,
>>you're using
>>>Infrastructure as the setting, so you're getting
> Internet
>>feed to Xbox Live!
>>>Go into the Dashboard on each Xbox and set them to
> System
>>Link.
>>>--
>>>Chris H.
>>>Microsoft Windows MVP
>>>Tablet Creations - http://nicecreations.us/
>>>Associate Expert
>>>Expert Zone - www.microsoft.com/windowsxp/expertzone
>>>
>>>
>>>"John" <anonymous@discussions.microsoft.com> wrote in
>>message
>>>news:1bf301c443f6$bd9cc440$3a01280a@phx.gbl...
>>>> Greetings,
>>>>
>>>> I recently bought a second xbox and added it to my
>>network
>>>> with a second MN-740 wireless bridge, so both of my
>>units
>>>> are connected to the network with their own MN-740
>>bridge.
>>>>
>>>> They both work fine independently, but I cannot get
> them
>>>> to communicate together for system link play, when
> BOTH
>>MN-
>>>> 740s are present on my network. I can start and see a
>>>> game between the units, but the connection will be
>>>> immediately lost, then back on, lost, and so on.
>>>>
>>>> If I remove one of the MN-740s from the network, hook
>>the
>>>> second xbox directly into a hub, it works fine, but as
>>>> soon as I add the second MN-740, the failures start
>>right
>>>> back up, even if the MN-740 isn't even connected to the
>>>> xbox. Its sheer presence on the network immediately
>>>> causes failure. Like there is some sort of conflict
>>>> between the 2 units that confusing the network.
>>>>
>>>> Can 2 MN-740s only work together, for system link
> play,
>>in
>>>> ad hoc mode? Doesn't seem to make sense to me that
> this
>>>> would be the case, but I'm at a loss otherwise.
>>>>
>>>
>>>
>>>.
>>>
>>.
>>