DMA2100 extenders all stopped working

Troubleshoot and discuss the XBOX 360, XBOX One, Linksys, and other extenders.
mrphil

Posts: 80
Joined: Thu Jun 23, 2011 8:22 pm
Location: United Kingdom

HTPC Specs: Show details

#21

Post by mrphil » Fri Jul 20, 2012 8:19 pm

Haven't tried the dns change yet, but of my 3 extenders one dma2100 is badly affected and locks up every time without fail, another dma2100 is occasionally locking up, and dma2200 in bedroom is completely fine. :eh:

Make of that what you will.

MikeSin

Posts: 38
Joined: Fri Aug 03, 2012 12:15 pm
Location: Kent

HTPC Specs: Show details

#22

Post by MikeSin » Sun Aug 05, 2012 9:53 am

In case it helps anyone else I had the selfsame problem but after reading post and trying the suggestion I realised that my router had not updated automatically the change in PDNS and SDNS servers addressesthat my ISP had seen fit to make - my router was set to static not auto update.ooops.. Curiously though the DMA2100 that uses wireless LAN resolved itself to the new addresses much easier than the wired router? I had to change from wired to wireless and then back again to get the second one working.
After a couple of days the wired 2210 stops but the wireless carries on. Both have same firmware level both have same setuo save their on Ip adresses and wired versus wireless. The PDNS has been automatically set to 191.168.0.1 with SDNS as 0.0.0.0. Any ideas as to why the wired one keeps freezing ?
Thanks

MikeSin

Posts: 38
Joined: Fri Aug 03, 2012 12:15 pm
Location: Kent

HTPC Specs: Show details

#23

Post by MikeSin » Mon Aug 27, 2012 3:26 pm

In July this year I too experienced the problem of "frozen" extenders. Changing the DNS server address did not work but changing from wired to wireless did. However the wirelesss peformance can be erratic and I would like to get back to wired. However the change back to wired brings almost immediate freeze. I have downloaded and used the microsoft network analyser tool for both a wireless and wired connection.

This shows the trace for wireless:
08:02:46 27/08/2012 60.5837646 192.168.0.8 239.255.255.250 SSDPSSDP:Request, NOTIFY * {HTTP:3, UDP:2, IPv4:1}

My DMA2100 192.168.0.8 is trying to contact 239.255.255.250 and does this 16 times every 5 mins but does not cause a "freeze" on the extender. There is no other activity either before or after this type of message.

For wired I get this (followed by the type of trace shown for wireless as above)

08:58:30 27/08/2012 89.7259078 Unavailable 192.168.0.11 192.168.0.6 UDP UDP:SrcPort = 1028, DstPort = 64374, Length = 319 {UDP:2, IPv4:1}
08:58:30 27/08/2012 89.7432983 192.168.0.11 192.168.0.6 ARP ARP:Response, 192.168.0.11 at 00-1D-7E-A4-0F-E2
08:58:30 27/08/2012 89.7470035 Unavailable 192.168.0.11 192.168.0.6 TCP TCP:Flags=...A..S., SrcPort=3391, DstPort=59909, PayloadLen=0, Seq=3731713282, Ack=2014106095, Win=5840 ( Negotiated scale factor 0x0 ) = 5840 {TCP:3, IPv4:1}
08:58:30 27/08/2012 89.7508246 Unavailable 192.168.0.11 192.168.0.6 TCP TCP:Flags=...A...., SrcPort=3391, DstPort=59909, PayloadLen=0, Seq=3731713283, Ack=2014106284, Win=6432 (scale factor 0x0) = 6432 {TCP:3, IPv4:1}
08:58:31 27/08/2012 89.9671727 Unavailable 192.168.0.11 192.168.0.6 HTTP HTTP:Response, HTTP/1.1, Status: Ok, URL: {HTTP:4, TCP:3, IPv4:1}
08:58:31 27/08/2012 90.0749521 Unavailable 192.168.0.11 192.168.0.6 HTTP HTTP:HTTP Payload, URL: {HTTP:4, TCP:3, IPv4:1}
08:58:31 27/08/2012 90.1872348 Unavailable 192.168.0.11 192.168.0.6 HTTP HTTP:HTTP Payload, URL: {HTTP:4, TCP:3, IPv4:1}
08:58:31 27/08/2012 90.2954169 Unavailable 192.168.0.11 192.168.0.6 HTTP HTTP:HTTP Payload, URL: {HTTP:4, TCP:3, IPv4:1}
08:58:31 27/08/2012 90.4053115 Unavailable 192.168.0.11 192.168.0.6 HTTP HTTP:HTTP Payload, URL: {HTTP:4, TCP:3, IPv4:1}
08:58:31 27/08/2012 90.5152760 Unavailable 192.168.0.11 192.168.0.6 TCP TCP:Flags=...A...F, SrcPort=3391, DstPort=59909, PayloadLen=0, Seq=3731718134, Ack=2014106284, Win=6432 (scale factor 0x0) = 6432 {TCP:3, IPv4:1}
08:58:33 27/08/2012 92.7165857 Unavailable 192.168.0.11 192.168.0.6 UDP UDP:SrcPort = 1028, DstPort = 64374, Length = 319 {UDP:2, IPv4:1}
08:58:36 27/08/2012 95.6873985 Unavailable 192.168.0.11 192.168.0.6 UDP UDP:SrcPort = 1028, DstPort = 64374, Length = 319 {UDP:2, IPv4:1}


Thi is the same DMA2100 but with a different IP adress (192.1681.0.11) "talking" to another PC (192.168.0.6) on my network - the extenders are serviced by a different PC for media center purposes.
The second non-media center PC is running Vista but I have uninstalled any reference to extenders, stopped the media center service , restored the DMA2100 to factory setting and even switched the second PC off but still get the DMA2100 locking up when using a wired LAN connection ?

Can anyone explain to me what is going on ?? Thanks

Mike

phv211

Posts: 1
Joined: Thu Oct 11, 2012 1:14 pm
Location:

HTPC Specs: Show details

#24

Post by phv211 » Thu Oct 11, 2012 1:20 pm

Hello

Thank you for the solution. I'm in France with a DMA2100 (lan) and DMA2200 (wifi). I applied your advice:
- Reset DMA
- IP Manual
- Gateway real (important)
- 0.0.0.0 for DNS

Impeccable and it works again.


Another question: How to flash the firmware without internet (server not responding for a long time for that matter), I downloaded it from the Cisco website? thank you

Post Reply