Beyonwizs networked, but cannot see each other
Beyonwizs networked, but cannot see each other
I've had a DP-S1 for ages, just got a new DP-P2. DP-S1 is using 1.05.350 firmware, DP-P2 is using 1.07.350. DP-S1 is using it's WLAN as always (WEP). I got a Netgear WNCE2001 plugged into the ethernet of the DP-P2 - it's hooked up to my ICE account no problems, and retrieved recording settings, so I know it's working - plus both can see my laptop windows share, and play a movie file ok. All hook up to a Linksys WAG120N wireless router.
The problem is the Beyonwizs seeing each other so I can stream stuff recorded on one to the other. I've got the WizPNP settings on each set to enable client and server, got one called upstairs, the other downstairs. Ports on both are still 49152.
When I do a network scan on the DP-P2, it doesn't find anything. It will find my laptop if I plug in it's IP address, but it won't find the DP-S1 if I do the same thing. Vice-versa for the DP-S1 in finding the DP-P2, although it will scan and find my laptop.
I'm stuck. I've turned both off and on of course (including the WNCE2001), and disabled/enabled the WizPNP settings. WizFX will find both beyonwizs when I plug in their IP addresses, and I can see the file listings on both.
Help please?
The problem is the Beyonwizs seeing each other so I can stream stuff recorded on one to the other. I've got the WizPNP settings on each set to enable client and server, got one called upstairs, the other downstairs. Ports on both are still 49152.
When I do a network scan on the DP-P2, it doesn't find anything. It will find my laptop if I plug in it's IP address, but it won't find the DP-S1 if I do the same thing. Vice-versa for the DP-S1 in finding the DP-P2, although it will scan and find my laptop.
I'm stuck. I've turned both off and on of course (including the WNCE2001), and disabled/enabled the WizPNP settings. WizFX will find both beyonwizs when I plug in their IP addresses, and I can see the file listings on both.
Help please?
Hi Griffyn,
I had this problem all of a sudden when I replaced my router/modem. Worked for years then stopped as soon as the new modem provided the network.
Went back to the old one (turns out it wasn't dead like I thought) and it worked again straight away, no changing of settings. So I doubt it's your settings, just your modem.
Sorry can't give any detail on how to check beyond trial and error.
For the record, the modem that didn't work was a Netcomm NB9WMaxxN and the one that does work is a Billion...7404VGP ( something like that anyway).
Good luck!
Rob
I had this problem all of a sudden when I replaced my router/modem. Worked for years then stopped as soon as the new modem provided the network.
Went back to the old one (turns out it wasn't dead like I thought) and it worked again straight away, no changing of settings. So I doubt it's your settings, just your modem.
Sorry can't give any detail on how to check beyond trial and error.
For the record, the modem that didn't work was a Netcomm NB9WMaxxN and the one that does work is a Billion...7404VGP ( something like that anyway).
Good luck!
Rob
Some WAP's have a security/efficiency setting to control broadcast/multicast traffic over the WLAN.
WizPNP discovery requires multicast traffic to be forwarded.
:edit: Make the pedantic people happy
_
WizPNP discovery requires multicast traffic to be forwarded.
:edit: Make the pedantic people happy
_
Last edited by IanB on Wed Apr 27, 2011 09:34, edited 1 time in total.
- tonymy01
- Uber Wizard
- Posts: 6373
- Joined: Fri Jun 01, 2007 15:25
- Location: Sydney, Australia DP-S1-1TB, DP-P2-2TB, DP-T4-2TB, DP-T4-BB... too many!
- Contact:
I wrote a little app some time ago to mimic the 2nd part of the wizPNP protocol between two wizes such that it would allow them to discover each other. It runs on the pc however, but may only need to be run once (not sure actually given I only have one Wiz so not sure of the finer points about how long each wiz stays in the other wiz table).
I am in another country now though for a bit...so hope you can find my posts from way back:)
I am in another country now though for a bit...so hope you can find my posts from way back:)
Tony
I presume this app is wizmongoose? It doesn't seem to be on your website any more. Does anyone have it? Perhaps you could upload it to rapidshare or something for me?tonymy01 wrote:I wrote a little app some time ago to mimic the 2nd part of the wizPNP protocol between two wizes such that it would allow them to discover each other.
- tonymy01
- Uber Wizard
- Posts: 6373
- Joined: Fri Jun 01, 2007 15:25
- Location: Sydney, Australia DP-S1-1TB, DP-P2-2TB, DP-T4-2TB, DP-T4-BB... too many!
- Contact:
No, it was born out of Wizmongoose, as I learnt how the WizPNP protocol did its thing, and this simply "pretended" to be another Wiz to advertise "hey, this is my IP address" to the first Wiz (which is using unicast rather than multicast protocol). I think I knocked it up for someone, dunno if I published it. When I do the remote access thing to my home PC next, I will see if I can dig it up if I didn't make it public.
Tony
So, I borrowed a large ethernet cable and plugged it into my DP-P2, to take the Netgear WNCE2001 out of the equation, and up popped my DP-S1 in the network list - awesome!
Unfortunately, when I put back the WNCE2001, the DP-S1 had disappeared, so there's no memory being kept of the connection that was. I've got an old linksys wireless router that I'll see if I can hook up as a WAP and see how that goes.
Unfortunately, when I put back the WNCE2001, the DP-S1 had disappeared, so there's no memory being kept of the connection that was. I've got an old linksys wireless router that I'll see if I can hook up as a WAP and see how that goes.
Hi Griffyn,
Regards,
Ian.
It sounds like it is time to refer the issue to Netgear. If this unit can't handle this basic task then some of their other models should handle it with ease.Griffyn wrote:I've had a look at the advanced options for it, and no. There's pretty much nothing configurable about it except for it's IP address and the wifi connect settings.
Regards,
Ian.