DMA2100 'network issue' warning

[La Laja]

After 1 or 2 hours running the DMA2100 (video playback / life TV) the video starts to breakup and a warning 'network issue' is displayed in the upper right corner.
This happens whether I use wireles N or wired 1000Tbase with plenty of speed according to the 'tune network' utilty.
Microsoft suggests a speed problem but that can hardly be the case. Also why doesit only happen (sofar.. ) after such a long time? Is there some kind of buffer overrun?
Any suggestions?

[La Laja]

I received a new firmware for the WRT350N from Linksys. I will report back if that helps.

[coma]

I get the same problem on my 2xDMA2200's both wired.
I have tried throttling the VMC back to 100mb - no joy.
Interested to hear how you go.
coma.

[jansen]

I have the same problem with the wireless connection between my LinkSys DMA 2100 and LinkSys WRT350N reporting a network issue. When I checked the signal strength on the DMA2100 graph view it is very low, however when I switch to the DMA2100 network settings menu the signal strength is reported good at more than half.

I initially thought it might be a network connection with the DMA2100 but the wireless connection to the laptops in our house (all wireless-G) also drop out. I also noted that the only way to fix it seems to be to power off and on the WRT350N, hence I'm guessing that there will be a WRT350N firmware update to fix this.

UPDATE:
Although I have only purchased my WRT350N in the last 6 weeks, it had outdated firmware v 2.00.10 instead of the current v 2.00.17. The label on my WRT350N indicates that it is version 2, however the LinkSys Australia tech support only has firmware update for WRT350N version 1. After contacting LinkSys international support via their webchat interface they directed me to the LinkSys UK site where they have the WRT350N version 2 driver: http://www-uk.linksys.com/servlet/Sa...#versiondetail


I've now installed the updated WRT350N driver and taken La Laja's advice to change the WRT350N wireless security setting to WPA2 with AES encryption (otherwise wireless-G is used instead of wireless-N). Using the network tuner and moving the DMA2100 and WRT350N by only 10cm away from power cables, metal brackets, tv and sitting on the amp seems to have given me maximum strength on the graph.

I will let you know if this resolves the drop out issues.

UPDATE 2:
No it still drops out, very irritating and hope someone can solve this...

[Penfold]

I get this issue too and I also have a 2100 via ethernet cable (100Mbps) but its doesn't happen that often maybe once a week but I find that stopping the live TV then going back into it fixes it. Otherwise try stopping the Live TV running a video file (Either MPEG or DivX) then use the Live TV again that seems to reset the video playback. There's obviously a bug in the 2100 and possibly the 2200 but this is the downside to early adoption. I'm sure the next firmware will have it fixed.

[La Laja]

I finally solved the network issue ! It is related to the microsoft issue kb929707. It describes the streaming problems between a (wired ofcourse) gigabit network adapter and a gigabit switch/router. It offers two possible solutions and because the Linksys Addendum of the DMA2100 recommended method 2 (manual flowcontrol) I had it setup like that. However that didn't solve the problem in my case!! I then used the other method (reducing the networkadapter speed to 100mb/s duplex) and ... that did it.
(Of course it is a shame that the overall network speed is down to 100mb/s)
Further remark : The addendum is a bit confusing. It states if you have connected your Media Center Extender to your computer with a wired connection .... I first had a wireless connection between the router/access point and the DMA. It resulted in the network issue. So I thought the kb929707 was not the problem. However I had the connection between PC and router (WRT350N) wired using the gigabit speed. And that's where the problem lies. Another confusing thing is that the addendum talks about Method 2: Manually enable flow control in the receive (Rx)direction while the MS article talkes about the transmit (TX)direction. Even more confusing is that the described setup in my case there was no way to choose either receive or transmit direction, just manual flowcontrol.