2. tech-talk
  3. 155706-144095

TEAC NT-505 impossible connecting to WiFi router o such LAN: help me please?

Hello mates,
I got my NT-505 3 days ago.
It seems to be working correctly but in my opinion all software in not the same level than the device: too aged & often no relevant documentation or support about.
However my big trouble is the NETWORK interface:  since first time I switched on, the NT-505 remains "for ever"  into NET configuring blinking state until it goes in power stand by.
Summarizing:

1. RJ45 cable is ok - tested in several manners
2. the wifi router (1Gb fiber connection) is ok
3. the wifi router ether ports (4) are ok - I checked a bridged LAN configuration too

Testing the NT-505 Ether port It results:

1. the physical level of protocol seems working correctly just on-way: the interface recognizes correctly the bandwidth (Fast ot Giga in my case) end the packet coming from the router are buffered. No packet sent  to the router.

2. At protocol level no ARP session are involved hence impossible retrieve MAC address and trying to do something.


VERY STUPID ISSUES:

1. Being NET board logically split from MAIN board It's need a separate firmware(!!!): how can I upload the NET firmware if, as stated into documentation, I must use the mobile app and It's impossible connecting the device to such LAN?

2. NO menu interface to configure manually the net parameters.

May someone help me (tricks..., recovery sw,..., low level maintance menu...,...) 

Thank you a lot.


silvio66
kosta68k
11 posts
 
Quick update: Off the phone with Teac US support, and the consensus was it’s a defective unit. Opened a case for replacement and will keep you guys informed with the progress once I get the new unit.

Found a buddy of mine that purchased his from an European store in Germany, and his works as a charm every time.


On a related note... I was able to get a consistent result with the unit been able to get an IP within 15 secs of switching it over to Network mode, or just turning off/on in Network mode of waiting for been up (warm up) for 5 minutes. In my case it seems something is definitively wrong with it’s network module or power supply, OR who cares what as long as I get a working unit at the end of the day.
Silvio, have you tried having yours up for about 5 minutes to warm up before trying to connect/switch it over to Network mode? May be worth trying to see if that’s consistent with my experience?

Be safe!!!
big_greg
6,665 posts
 
I've been keeping an eye on this thread, because in this one or another I saw that there was a firmware update available that I hadn't installed.  After I did, I started having a ton of issues getting and staying connected to the NT-505.

My setup is a little different than most in that I have mine connected wirelessly, using a Wireless Access Point configured as a client and then connecting that to a four port switch that I have the NT-505, my Oppo BD player, my TV, and my Roku connected to.  I've been having some issues with my router (waiting for a replacement) and thought that might be the issue.  

I removed the switch and connected the NT-505 directly to the WAP and it seems to be functioning without any issues for about a day now.  I really like mine, but it's troubling to hear of so many issues.  I'm hoping the new router and a new WAP will fix my issues.  It did work OK when I ran a long ethernet cable directly from my router, so it may be that it's an issue with my home network.  I was also having issues streaming Netflix on the Roku, so I'm not convinced it's a problem with my NT-505 yet.
kosta68k
11 posts
 
Hi BG, Oh, I'm totally convinced mine is related to my NT-505. I have about 30 WiFi and another 15 LAN devices spread around my house and none of them show any such problems, so yeah, unfortunately I could positively say it's the Teac.

Hope you'll have better luck/experience once you get your new router installed. Good luck!
kren0006
1,859 posts
 
Sorry that you guys/gals are having trouble. Before this issue I’d never heard of any NT-505 trouble, but I guess it’s probably not that widely owned. Hope Teac gets it fixed or replaces the defective units.

Since I’ve not had any trouble in a year running version 1.21 firmware, I’m sticking with that and not flashing to the 1.22 version. Indeed, I have a lot more trouble with my Bluesound unit than I ever have with my Teac, which has been (knock on wood) flawless for me -
big_greg
6,665 posts
 
I had the 1.01 firmware, or whatever it was that it came with and other than some initial issues when I first got it, no problems until I upgraded the firmware.  I still think my issue might be network related though, so I'm withholding judgment for now.
More to discover