 STN join:2004-12-29 Canada | reply to soulrain
Re: SagemCom 2864 + PS3 Media Server Trouble Thinking about this further, I wonder if some of these devices and protocols may use different broadcast addresses. I know if you wanted to reach all the clients on your LAN in theory you could broadcast advertisement messages to 255.255.255.255 or 192.168.2.255 (assuming a 192.168.2.0/24 network).
Is it possible that one type of broadcast is getting through but another type is not? For example 192.168.2.255 packets are being switched between WLAN/LAN but 255.255.255.255 is not?
From Wiki: »en.wikipedia.org/wiki/Broadcast_address
quote: The broadcast address for an IPv4 host can be obtained by performing a bitwise OR operation between the bit complement of the subnet mask and the host's IP address.
Example: For broadcasting a packet to an entire IPv4 subnet using the private IP address space 172.16.0.0/12, which has the subnet mask 255.240.0.0, the broadcast address is 172.16.0.0 | 0.15.255.255 = 172.31.255.255.
A special definition exists for the IP broadcast address 255.255.255.255. It is the broadcast address of the zero network or 0.0.0.0, which in Internet Protocol standards stands for this network, i.e. the local network. Transmission to this address is limited by definition, in that it is never forwarded by the routers connecting the local network to other networks.
Anyone have packet captures of working or non-working examples? |
|
 STN join:2004-12-29 Canada | reply to soulrain I think your problems may be caused by the same issue I report on here:
»Bell Connection Hub + AirPlay = broken |
|
 | reply to soulrain it is still working for me !!!!!!!!!!! added more movies .. downloading more movies  |
|
 | reply to soulrain 2 days -- same issue, cracked my head no luck .
just gave up fibe 6 and upgraded to fibe 25 sagemcom ..
right now i feel no god, but much luckier than all you people out there ..
atfirst it showed me bell connection hub, no luck upon going inside.. showed no titles ..
did media servers search no luck -- no luck ..
would recognize the bell connection hub but thats it ..
restarted the hub, connected my 1 tb WD hd
started by going into photo's -- saw lucky with it recognizing the pics ..
had no music .. so jumped straight to movies -- and VOILA !!!!!!!!!!!!!!!!!!!!!!!! i am viewing gone in 60 seconds with my new bose home theater system --- vroom !!!!! off it goes .. all through my hd
really i guess am LUCKIER than all you here lol |
|
 Reviews:
·Bell Fibe
| I do not know what is messed up on your end but have fibe with sagemcom and my ps3 is being streaming everything perfect from my pc running win7
I did not change any setting on the routers only changed my passphrase but working perfect since day 1.
Double check that your allowing streaming in Windows Media Player and make sure file sharing is enabled in Windows. |
|
 | its not an issue with connecting router to the ps3 .. windows media streaming is working fine (seemingly for everyone) ..
the sagemcom router has 2 usb ports on it .. if you attach your hard drive to any of the ports .. and if you scan for media servers on ps3 .. it should detect in bell icon there on ps3 .. once you go into movies section and into bell folder it should scan your movies on the hdd which is attached to the modem (example -- could be pictures and songs too) ..
they cannot view any of the data associated with the hdd on ps3 thru the bell folder |
|
 | I was having the same problems of connecting PS3 wirelessly to the SagemCom 2864. -Bell tech told me to contact SONY!!!
Played around and resolved it as follows: In Connection Hub Wireless Settings, go to MAC Filtering. Under "MAC Addresses allowed", add the MAC Address of your PS3. Save the settings.
PS3 connected over wireless!
Hope this helps anyone else with the same issue. |
|
 | well the way i resolved it was by continuously clicking on search for media servers .. thats when it use to load it all .. also try to click on triangle and select display all once you have the bell connection hub highlighted ..
this is what i have done .. i formatted my harddrive from ntfs to fat32 .. the entire hdd is 1gb and its formatted to fat32 using 2tware fat32 sw (if you have windows 7 .. use this sw) and you can connect your hdd to the ps3 .. as ps3 only recognizes fat32 and not ntfs .. do not make a mistake of creating 32 gb size of volumes as ps3 will recognize only the first volume and not the rest .. so make sure the entire size of the hdd is formatted to just one volume of fat32 .. once you connect to ps3 it will recognize your hdd and all your videos on it .. voila .. no streaming issues and it works perfectly fine ..
i had a lot of issues with streaming with the bell hub .. it buffers a lot |
|
 | reply to mikalal Have been going insane with this. Can't get the Sagecom to properly talk to my PS3 with PS3 Media Server. I opened Port 5001 in the Sagecom and even put the MAC ID of the PS3. Nothing...
If anyone finds a fix for this, please let me know at homer_simpson@sympatico.ca |
|
 | Got it to work on wired ethernet. Notice the differences between wireless and wired. Something is definitely wrong with the routing of WLAN to LAN.
wireless:
[main] INFO 13:45:44.786 Scanning network interface TP-LINK 802.11b/g Wireless Adapter (net3) [main] INFO 13:45:44.787 Using address /192.168.2.4 found on network interface: name:net3 (TP-LINK 802.11b/g Wireless Adapter) [main] INFO 13:45:44.788 Created socket: /192.168.2.4:5001 [main] INFO 13:45:45.132 Using the following UUID configured in PMS.conf: 017ae718-6ff4-3bd6-8c0d-6ec7d283161d [main] INFO 13:45:49.721 The server should now appear on your renderer
wired:
[main] INFO 13:39:05.895 Scanning network interface Realtek RTL8101E Family PCI-E Fast Ethernet NIC (NDIS 6.20) (eth3) [main] INFO 13:39:05.896 Using address /192.168.2.2 found on network interface: name:eth3 (Realtek RTL8101E Family PCI-E Fast Ethernet NIC (NDIS 6.20)) [main] INFO 13:39:05.896 Created socket: /192.168.2.2:5001 [main] INFO 13:39:06.191 Using the following UUID configured in PMS.conf: 017ae718-6ff4-3bd6-8c0d-6ec7d283161d [New I/O server worker #1-1] INFO 13:39:08.711 No IP filter specified, access granted to /192.168.2.3 [pool-4-thread-1] INFO 13:39:08.733 Checking ip:192.168.2.3 for Playstation 3 [pool-4-thread-1] INFO 13:39:08.757 Renderer Playstation 3 found on this address: new-host-16.home (192.168.2.3) [pool-4-thread-1] INFO 13:39:10.812 Address /192.168.2.3 has an estimated network speed of: 93 Mb/s [main] INFO 13:39:11.013 The server should now appear on your renderer [New I/O server worker #1-2] INFO 13:39:38.361 Checking shared folder: C:\Users\XXX\Videos [New I/O server worker #1-2] INFO 13:39:38.363 Checking shared folder: C:\Download [New I/O server worker #1-2] INFO 13:39:38.364 Checking shared folder: C:\Tracktor MP3 [New I/O server worker #1-2] INFO 13:39:38.365 Checking shared folder: C:\MP3 [New I/O server worker #1-2] INFO 13:39:38.366 Checking shared folder: C:\Signals & Systems [New I/O server worker #1-2] INFO 13:39:38.367 Checking shared folder: C:\Users\XXX\Music [New I/O server worker #1-2] INFO 13:39:38.368 Checking shared folder: C:\Users\XXX\Pictures [New I/O server worker #1-1] INFO 13:40:18.150 The file C:\Download\08-maetrik-crush_on_me.mp3 was badly parsed. It will be hidden [New I/O server worker #1-4] INFO 13:40:25.244 Starting transcode/remux of maxhd-catfa-1080p.mkv |
|
|
|
 STN join:2004-12-29 Canada | said by silverdroid :Got it to work on wired ethernet. Notice the differences between wireless and wired. Something is definitely wrong with the routing of WLAN to Yes, Multicast packets are not passed from LAN to WLAN.
It is possible some protocols for Windows sharing or otherwise may use Broadcast packets. Broadcasts are forwarded from LAN to WLAN. UPnP however appears to not use Broadcast, and instead uses Multicast to announce and discover. This could impact you since the Multicast announces will not be sent from LAN to WLAN.
Now, someone mentioned that they put the PS3 MAC into the MAC filtering page:
Played around and resolved it as follows: In Connection Hub Wireless Settings, go to MAC Filtering. Under "MAC Addresses allowed", add the MAC Address of your PS3. Save the settings.
This is interesting because perhaps this allows Multicast to flow from LAN to WLAN to that specific MAC? I haven't tested that, so I can't comment. It may be a work-around, but I'm unsure. |
|
 | reply to soulrain Hi soulrain.
Were you finally able to solve the PS3 media server problem with the Bell Fibe Sagemcom 2864 modem? Two days ago I also did the upgrade to Bell Fibe, and I had the same problem, the PS3
media server, latest version 1.50.1 and previous, refused to see the PS3.
I have a temporary walk-around solution, until a new PS3 media server version solves the problem, or until somebody find the proper setting(s) in the PC or in the modem.
Before the Fibe upgrade, I had the Speedstream 5200 modem connected to the Internet input of a D-Link DIR-628 router (wireless + 4 wired RJ-45 ports). The PS3 and others PCs were connected
to the 4 ports, and the PS3 media server used to run OK on all PCs.
Now with the Bell Fibe Sagemcom 2864 installed, one of its RJ-45 ports is connected to the Bell Fibe Motorola VIP1232, one other to the PS3 and the two others to desktop PCs LAN input;
laptops use the wireless link. With this configuration, the PS3 is not seen by any computer.
Today I unplugged all the wires on the 2864 RJ-45 input/output connectors, except the RJ-45 cable going to the VIP1232. A RJ-45 cable was then installed between one of the free 2864 port
and the D-Link Internet RJ-45 in/out port. The PS3 and other desktop PC use the 3 other D-Link router ports. The wireless LAN, sets 2 days ago to use the 2864 wireless connection, is using
back the D-Link DIR-628 wireless signal.
With this modem/router/PCs configuration, all the desktop and wireless laptop PCs can now execute the PS3 media server with no problem as before.
Hope it can help you.
Bye. |
|
 | reply to STN said by STN:Now, someone mentioned that they put the PS3 MAC into the MAC filtering page: First, that MAC filtering section is only applicable for wireless connections. My PS3 is wired to my SagemCom, so would be non-applicable. Regardless, I tried it anyways and it still yielded no results.
The problem is simply as described by the Multicast issue above. The SagemCom in its present state cannot translate from WLAN to LAN. And unfortunately, this is not a priority for Bell Fibe TV to fix anytime soon. |
|
 | I was using the white Bell router without an antenna for my Fibe 16 previously, just upgraded to fibe 25 and they gave me this crappy sagemcom connection hub. On the white router my wireless printer and NAS worked right out of the box with no configuration needed. In this sagemcom, it seems to be blocking the LAN traffic from speaking to each other. Have tried almost everything and it just simply does not allow me to print from my laptop to wireless printer or for my media box to access the NAS. The media box and the PS3 just show bell connection hub. When i disable the UPnP on the connection Hub, the media box as well as PS3 claim no media is connected. All the boxes can access internet without issue. Really frustrating, gave bell tech support a piece of my mind. We no longer just use these boxes for internet so they have to provide support for such issues. |
|
 | by the way, my NAS, PS3 and media box are all hardwired to router and my laptop and as name suggests, wireless printer are both wireless connections. I can ping all the boxes sometimes yes and sometimes no from my laptop. I have tried to forward ports but no luck. |
|
 kovy join:2009-03-26 kudos:4 | reply to soulrain I don't know how you setup your wireless printer... but it works for me ...
And it was pretty easy...from the printer just connect to your wireless network name, put the password and after install the software/drivers on your PC and voila.
Edit: It's not on the wirless guest, but on the primary one. |
|
 | reply to AnotherONE I too am completely frustrated with my "new" Sagemcom 2864 and getting a printer to work and to share on the USB. The Sagemcom sees the printer and identifies it, but there appears to be no way to make it work. I will try my office tech support guy on Monday, which brings me to my point.
If Bell is going to supply a product, - ok - I understand they don't want half a million support calls on how to configure a TCP/IP port, BUT AT THE VERY LEAST, PROVIDE THE SOLUTION IN THE DOCUMENTATION WITH THE DISCLAIMER THAT THEY TAKE NO SUPPORT CALLS.
I am also having an issue with the hub recognizing my various machine names in the network. It sees them all, captures their MAC and IP, but continues to name them "computer-2" etc. except for a very few. Both the chat and call in tech support had me re-name, re-boot, and re-set, to no avail. AGAIN, IF YOU PUT A PRODUCT INTO CONSUMER HANDS, PROVIDE THE NECESSARY DOCUMENTATION.
That's my beef ! |
|