No Samba access since 4.4.2 update

[Justin Addison]

Hi all.

I have a Samba server at home, running from my router's USB port. I access files on this drive from my Nexus 4, my Nexus 10, my Windows computer and my iPad. Up until very recently, this was all working swimmingly, with no problems.

However, since the most recent Android update, i have been unable to access the Samba server from either of my two Android devices. The Android devices can see other devices on the network (via ES File Explorer), but no longer the USB device attached to the router, via the Samba server.

This isn't a problem with ES File Explorer as the exact same issue is found when using other remote file viewers. And this isn't a problem with the router, as I called the manufacturer, who also acts as my ISP, to check the settings remotely, and they said that they're optimised (as you would expect, as the other devices are still working fine).

I tried to access the server using AndSMB, failing again, but getting this error message:

smb://yourserver:445/ java.net.UnknownHostException: yourserver
PWD
smb://yourserver:445/ java.net.UnknownHostException: yourserver

I have trawled the internet and no-one seems to have the same issue, and I'm not smart enough to know what the above error means.

Can anyone please help with this?

Many, many thanks.

 

[Sicily1918]

I tried to access the server using AndSMB, failing again, but getting this error message:

smb://yourserver:445/ java.net.UnknownHostException: yourserver
PWD
smb://yourserver:445/ java.net.UnknownHostException: yourserver

I have trawled the internet and no-one seems to have the same issue, and I'm not smart enough to know what the above error means.

Can anyone please help with this?

Many, many thanks.

Very odd -- I have a similar setup (shares on the router as well as real Samba shares on Linux) and have had no issues.

From the error above, it seems that port 445 (CIFS (ActiveDirectory) -- still part of SMB) is what's giving you issues (SMB also uses 137 - 139), but.... the app you're using is very old (it has not been updated for over a year) -- it's possible the way KK handles CIFS calls has changed, in keeping with Linux. The following call could be what's messing you up:

Linux CIFS mount syntaxes:

Old Way:
mount -t cifs -o username=xxx -o password=1234 popcorn:/share/Video /mnt/Popcorn

New Way:
mount -t cifs -o username=xxx -o password=1234 //popcorn/share/Video /mnt/Popcorn

If you look, the pointer to the server ('popcorn', in this case) you originally used server:/share whereas now you use //server/share , if AndSMB is passing the old command, the new os may not like it (Linux distros have been warning old-style mounters that the command is deprecated and will be removed -- this may have just happened.)

OK, Linux lesson over. Try this program:
https://forums.androidcentral.com/e...s?id=com.lonelycatgames.Xplore&token=vlrq3h45
It lets you add local SMB servers and will show you all the shares available -- see if it works for you (it does for me on every device).

 

[Justin Addison]

Very odd -- I have a similar setup (shares on the router as well as real Samba shares on Linux) and have had no issues.

From the error above, it seems that port 445 (CIFS (ActiveDirectory) -- still part of SMB) is what's giving you issues (SMB also uses 137 - 139), but.... the app you're using is very old (it has not been updated for over a year) -- it's possible the way KK handles CIFS calls has changed, in keeping with Linux. The following call could be what's messing you up:

Linux CIFS mount syntaxes:

Old Way:
mount -t cifs -o username=xxx -o password=1234 popcorn:/share/Video /mnt/Popcorn

New Way:
mount -t cifs -o username=xxx -o password=1234 //popcorn/share/Video /mnt/Popcorn

If you look, the pointer to the server ('popcorn', in this case) you originally used server:/share whereas now you use //server/share , if AndSMB is passing the old command, the new os may not like it (Linux distros have been warning old-style mounters that the command is deprecated and will be removed -- this may have just happened.)

OK, Linux lesson over. Try this program:
https://forums.androidcentral.com/e...s?id=com.lonelycatgames.Xplore&token=AkNpVAEo
It lets you add local SMB servers and will show you all the shares available -- see if it works for you (it does for me on every device).

Sicily,

Thanks for your reply.

What's the easiest way to change the mount syntax? The device isn't rooted.

I downloaded xplore but am facing the same issue with this as with all other remote file viewers, I.e. cannot connect to server.

Thanks,

Justin

 

[Sicily1918]

Sicily,

Thanks for your reply.

What's the easiest way to change the mount syntax? The device isn't rooted.

I downloaded xplore but am facing the same issue with this as with all other remote file viewers, I.e. cannot connect to server.

Thanks,

Justin

No prob.

There isn't any way that I know of, since the program's passing this info. I presume it's a hard-coded command (that just makes sense).

Did you add the server's IP manually in X-plore? If so, and it's still screwed up, try rebooting the router and, failing that, unsharing the USB drive (through the router) and then setting it up again -- the problem could be coming from that, and other devices on your network are just more tolerant and allowing you to browse?