Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Here's a weird one. I had my server up and running nicely. I was using Comcast for my Internet connection. My DNS-323 was connected directly into my wireless router (using a static IP address) which was connected directly to my cable modem. Two weeks ago I switched from Comcast to Verizon FIOS. Their broadband modem has a wireless router built in so I just plugged the DNS-323 directly into it. I used the same static IP address. Now it works for 5-10 minutes and then drops off. Fiddle with it a while and it will reconnect and then do the same thing. This of course makes it completely useless as a media server (I am using the Squeezebox Duet which I love).
What could possibly be happening? Any ideas or suggestions?
Thanks,
Lloyd
Offline
Read the FIOS Q&A. It states that you MUST use their router and that other routers will not work. This tells me that they have something proprietary in there. My solution would be to connect your old router's WAN port to the FIOS router and set your network up as you always had in the past. Let FIOS think there is only 1 computer present (the WAN port on your router).
Offline
I was wondering if you resolved this.
First, a couple of things to know. Fios does, in fact, require you to use their router. It's (unless things have changed) an Actiontecmodel running customer firmware for Verizon. They claim a couple of things, such as this allows them to troubleshoot remotely, it's the only router that will work correctly etc. Most of this is exagerration - although it is absolutely true that they are able to troubleshoot remotely. You CAN use other routers with Fios - you can find examples of people doing it all over the place.
So, to address your specific problem. First, we need to get a better idea of what is happening when the failure occurs. When it goes down can you ping it? I don't know how technically inclined you are, but if I were troubleshooting the same issue (as I do everyday - I'm an escalation engineer for VPN routers and ethernet routing switches) I'd start by looking at a trace of the traffic before and after the problem occurs, and at both ends. To do that you'd need a hub on the DNS-323 side and another PC (or another switch that does port-mirroring, though I'd be surprised if you had one). In a basic sense, we don't know where the problem even lies yet.
Evidence for the Fios router - the problem started when you introduced it. However, this is not enough to conclusively prove the problem is with the new router. I have literally seen issues where everything pointed to one new router, until detailed testing showed that the new router used a different chipset (Marvel instead of Broadcom, for example) which was less tolerant of low signal strength from the innocent-looking router. So, just because the problem started when the Fios router was put in does not mean it is the source of the problem.
That being said, my money would be on the Fios router anyway. But to know for sure you should start with traces to see if you can figure out what happens when the DNS-323 becomes unreachable.
Offline