| SagemCom F@st 2864 XBOX 360 Media Stream issues Hi Guys,
Hope someone can help me with the issue I am having:
I upgraded to fibe 25 and was given this sagemcom f@st 2864 modem. Since I upgraded, I cannot seem to stream media from my Desktop to XBOX. I setup according to xbox site and also followed their FAQ.
Here is how my setup looks like:
XBOX wifi
Laptop Wifi
Desktop Wired to modem directly, not using any routers
XBOX cannot find my desktop although it does work with the laptop fine. When I search for PC in xbox it only finds bell media hub and laptop but not the desktop.
I tried following so far:
Network setup as Home
Sharing Options set as:
Network discovery is on.
· File and printer sharing is on.
· Public Folder Sharing is on.
· Media streaming is on.
· Password protected sharing is off.
· HomeGroup Connections: Allow Windows to manage homegroup connections.
windows media player streaming is on and XBOX is allowed.
Windows Services as following:
Internet Connection Sharing Service: Stopped\Disabled
Media Center Extender Service: Started\Automatic
Network List Service: Started\Automatic
Quality Windows Audio Video Experience: Started\Automatic
SSDP Discovery Service: Started\Automatic
UPnP (Universal Plug and Play) Device Host: Started\Automatic
Windows Media Player Network Sharing Service: Started\Automatic
Router Setup:
UPnp enabled
All devices have static IP assigned
Mac Filters allows all three devices
Port forwared 53,80,88,3074
Cant connect XBOX via wire or Desktop via wifi since they are on different floors.
Any suggestions? your help would be greatly appreciated. |
|
| Is it working with media center? |
|
|
|
| reply to Jazz00
There are several other threads in this forum regarding shared drives, media servers, etc. on the Sagemcom devices. The general consensus is that the discovery doesn't work because there is filtering of some packets (broadcast/discovery) between the wifi and the wired segments on the LAN. I am unsure if someone has found a solution, but perhaps looking at the earlier threads will be helpful. There is one on the PS3 media server issue that is recent. |
|
| reply to phily316
said by phily316:Is it working with media center?
no it doesnt |
|
| reply to freejazz_RdJ
said by freejazz_RdJ:There are several other threads in this forum regarding shared drives, media servers, etc. on the Sagemcom devices. The general consensus is that the discovery doesn't work because there is filtering of some packets (broadcast/discovery) between the wifi and the wired segments on the LAN. I am unsure if someone has found a solution, but perhaps looking at the earlier threads will be helpful. There is one on the PS3 media server issue that is recent.
I did read those and applied some suggestions but will read it again to see if I miss something |
|
| I have the same problem. I use 2 Xboxes with a switch hardwired to the Sagemcom. If you check the Xbox network settings, you will see that the Xbox gets an external IP. Which it shouldn't. Since the Xbox is not getting a local IP (192.168.0.x), it is not seen as part of the network. I'm calling Bell today about this and will probably file a complaint and probably cancel my service if they can't change this. SagemCom sucks. |
|
| reply to Jazz00
I called Bell and one of their rep told me (unofficially) to try to disable Upnp and reboot the modem. I'll see tonight if that works. Apparently the Upnp gives the Xboxes external Ips for unhindered matchmaking. When disabled, the theory is that it should be seen on the network. |
|
| reply to Jazz00
I called Bell and one of their rep told me (unofficially) to try to disable Upnp and reboot the modem. I'll see tonight if that works. Apparently the Upnp gives the Xboxes external Ips for unhindered matchmaking. When disabled, the theory is that it should be seen on the network. |
|
| reply to Jazz00
Chatted with another one that says to enable DMZ. Every call, a different answer. |
|
| reply to Jazz00
Actually, I remember inputting the PPPoE info for Bell login into my Xboxes for online play (it removes any NAT restrictions). I'll set the Xbox back to factory default in network settings and see if that solves the issue. |
|
| reply to Morholt
said by Morholt:I have the same problem. I use 2 Xboxes with a switch hardwired to the Sagemcom. If you check the Xbox network settings, you will see that the Xbox gets an external IP. Which it shouldn't. Since the Xbox is not getting a local IP (192.168.0.x), it is not seen as part of the network. I'm calling Bell today about this and will probably file a complaint and probably cancel my service if they can't change this. SagemCom sucks.
I assigned static ips so my xbox do have an internal IP |
|
| reply to Morholt
said by Morholt:Chatted with another one that says to enable DMZ. Every call, a different answer.
dmz has no affect on wlan it applies to internet only. I enabled it but for different reason to open the NAT |
|
| reply to Morholt
said by Morholt:I called Bell and one of their rep told me (unofficially) to try to disable Upnp and reboot the modem. I'll see tonight if that works. Apparently the Upnp gives the Xboxes external Ips for unhindered matchmaking. When disabled, the theory is that it should be seen on the network.
did it work? I disabled upnp once but never did the reboot before enabling it again |
|
| Spent 35 minutes waiting to get to, and with level two support for Bell Fibe. Escalated to the senior associate, and demanded that a ticket be opened. Actually, referenced this exact thread! This guy wasn't familiar with the problem, but said based on this information he'd forward it to his managers.
Told them I'd follow up in a few days. I'll let you know how it works out! |
|
| reply to Jazz00
OK. I tried everything under the sun and I actually made it to work. The issue we all encountered is similar to the one reported in this thread »Bell Connection Hub + AirPlay = broken
I reset the Xbox to factory default in the network settings so that it was provided a local IP (you mentioned that you have static IP, so no issue there). You HAVE TO connect your PC/laptop to the gateway via Ethernet. You HAVE TO. It won't work over WiFi. As mentioned in the link provided, there seem to be a problem/safeguard between the exchange of packets between the WLAN and LAN. I can confirm that with an Xbox connected via Ethernet and a PC connected via Ethernet, the Xbox is recognized over the network and Windows Media Center works.
I am also using a Power Line network adaptor and I haven't been able to make it work yet with that set up but I have not had enough time to see if the Power Line was working properly. I'll try that again tonight.
It is disappointing that Bell would put such a safeguard (possibly to avoid WLAN flooding that could disrupt IPTV) and not tell their techs about it. I think I know more than any of the Bell techs I talked to regarding this issue. And now you do too!  |
|
| reply to duffent
I called Bell more times than I have fingers on one hand about this issue. Try connecting your PC and Xbox via Ethernet directly and see. Any device (whether PC or Xbox) connected via WiFi won't work with Windows Media Center or Vuze/Azureus. |
|
| reply to Jazz00
Yeah I figure it will work as you guys said if XBOX and the PC connected with LAN since it works with the laptop over wifi just fine. The problem we are having if one device is wired and one wireless. I made some changes and now PC is actually showing in PC list on XBOX but still cant connect I will try some more and report back if things work out. |
|
| reply to Jazz00
On the side note do any of you know how to get more line speed than 72mbs over wifi? I even tried placing the laptop beside the modem but 72 is the max I get. all the devices are using 802.11N. |
|
| reply to Jazz00
Just use the SagemCom F@ast 2864 as a bridge, instead of as a router. I was having problems with with my media server being detected until I did this. |
|
 STN
join:2004-12-29
Canada | reply to Jazz00
said by Morholt:It is disappointing that Bell would put such a safeguard (possibly to avoid WLAN flooding that could disrupt IPTV) and not tell their techs about it. I think I know more than any of the Bell techs I talked to regarding this issue. And now you do too!
Don't confuse the fact that this behavior exists with the thought that this was done on purpose. This is likely considered a bug and will be addressed in the future. |
|
