Hi I have a strange problem since moving from Vodafone to TrustPower ADSL with my previous configuration working flawlessly.My symptoms are that with my new TrustPower-supplied desktop wired to the ADSL router (Netcomm NB604N-NZ) I have no problems connecting to and surfing the web" alt="PC wired to Netcomm">If I plug in my Linksys EA6500 (running as a WAP in bridge mode dishing our addresses via DHCP in a separate subset to the DSL router) into one of the Netcomm LAN ports, after about two minutes the internet on my wired PC (and WiFi devices slows to a halt. See below for a trace route to www.google.com from my wired PC. You'll see it's flying along nicely @ ~22ms and it starts slowing at about the 130th ping iteration and then times out" alt="Linksys plugged into Netcomm LAN port">Reply from 131.203.2.42: bytes=32 time=22ms TTL=59Reply from 131.203.2.42: bytes=32 time=24ms TTL=59Reply from 131.203.2.42: bytes=32 time=24ms TTL=59Reply from 131.203.2.42: bytes=32 time=23ms TTL=59Reply from 131.203.2.42: bytes=32 time=23ms TTL=59Reply from 131.203.2.42: bytes=32 time=43ms TTL=59Reply from 131.203.2.42: bytes=32 time=56ms TTL=59Reply from 131.203.2.42: bytes=32 time=25ms TTL=59Reply from 131.203.2.42: bytes=32 time=25ms TTL=59Reply from 131.203.2.42: bytes=32 time=56ms TTL=59Reply from 131.203.2.42: bytes=32 time=49ms TTL=59Reply from 131.203.2.42: bytes=32 time=24ms TTL=59Reply from 131.203.2.42: bytes=32 time=23ms TTL=59Reply from 131.203.2.42: bytes=32 time=22ms TTL=59Reply from 131.203.2.42: bytes=32 time=23ms TTL=59Reply from 131.203.2.42: bytes=32 time=22ms TTL=59Reply from 131.203.2.42: bytes=32 time=26ms TTL=59Reply from 131.203.2.42: bytes=32 time=35ms TTL=59Reply from 131.203.2.42: bytes=32 time=75ms TTL=59Reply from 131.203.2.42: bytes=32 time=23ms TTL=59Reply from 131.203.2.42: bytes=32 time=391ms TTL=59Reply from 131.203.2.42: bytes=32 time=865ms TTL=59Reply from 131.203.2.42: bytes=32 time=636ms TTL=59Reply from 131.203.2.42: bytes=32 time=640ms TTL=59Reply from 131.203.2.42: bytes=32 time=894ms TTL=59Reply from 131.203.2.42: bytes=32 time=1055ms TTL=59Reply from 131.203.2.42: bytes=32 time=1348ms TTL=59Reply from 131.203.2.42: bytes=32 time=1713ms TTL=59Reply from 131.203.2.42: bytes=32 time=2281ms TTL=59Reply from 131.203.2.42: bytes=32 time=2995ms TTL=59Reply from 131.203.2.42: bytes=32 time=3759ms TTL=59Request timed out.Ping statistics for 131.203.2.42: Packets: Sent = 140, Received = 139, Lost = 1 (0% loss),Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 3759ms, Average = 142msI also have a Yealink W52P VOIP handset and similar behavior occurs plugged into the Netcomm with or without the Linksys.I have not changed the config on the Linksys or the Yealink. The Netcomm is out of the box as per TrustPower's supply. What is strange is I cant ping the 'external' interface of the WAP (the Netcomm side) but I can see the Netcomm DHCP server has successfully dished out an IP address.I'm beginning to this I should give both the VOIP handset and the WAP static IP addresses. Other than that, any clues?thanks in advance!
↧