Probably because I don't really know what I'm doing. I even tried installing Avahi through entware but that didn't work either. Hmm I tried using smb:// and it didn't connect. So on Android/Linux/iOS you have to use the IP address of the Router/NAS Starting end of December builds have the new ksmbd, no netbios discovery any more but only windows discovery service. The problem seems to be connected to the recent BS builds as neither earlier kong builds, on the AC1450, or stock netgear firmware, on the r9000, had this problem.Īnyone else notice anything like this. Example 192.168.5.135 and 192.168.5.255 may show up in the scan but the actual router(192.168.5.1) that acts as the AP and samba server on the network doesn't.Ī wired connection to the router through windows 10 finds and maps the the smb shares just fine. Strangely other device's on the network may show up when I scan for the router. I can use either router as a wireless AP Internet connection is good but if I try to wirelessly scan for the smb server on either router I can't find it. I also updated the AC1450 to 44483 at about the same time.Īfter some testing I realized that neither router's smb shares are visible to my android devices. I recently switched my router from an AC1450 using a later version of Kong (37985) to a R9000 running BS 44483. I have been using it to access the samba shares on my router for years. I use a file browser on my phones and tablets called Mixplorer it works quite well for universal file browsing of SMB, FTP, Sftp etc. I noticed an odd problem with samba shares. Posted: Wed 12:14 Post subject: Unable to see samba shares from android devices with BS44483
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |