Recent content by MikeAndSal

Simply by trawling through web page after web page reporting the same issue. Most were of no use, but one or two had the '\\' instead of the '/'. Figured it was worth a shot. Still, it's very odd that the command I've used for over a year now suddenly failed and that no one else...

SOLVED! (For me at least). No idea why it failed in the first place, but by changing from this: mount -t cifs //192.168.1.2/Movies "/media/My Video/Movies" -o username=Mike,password=**** to this: mount -t cifs //192.168.1.2\\Movies "/media/My Video/Movies" -o username=Mike,password=****...

Here's what I get this time. humax# smbclient -L diningroompc -I 192.168.1.2 -U mike added interface ip=192.168.1.15 bcast=192.168.1.255 nmask=255.255.255.0 Password: Domain=[WORKGROUP] OS=[Windows 8.1 9600] Server=[Windows 8.1 6.3] Sharename Type Comment ---------...

Net share gives me the list of the shares available and, yes, I can access those shares from other Windows devices (and Android devices for that matter).

Which implies that 192.168.1.2 is not available, but I can ping it. humax# ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes 64 bytes from 192.168.1.2: seq=0 ttl=128 time=1.901 ms 64 bytes from 192.168.1.2: seq=1 ttl=128 time=0.961 ms 64 bytes from 192.168.1.2: seq=2 ttl=128...

OK. I get this: humax# smbclient -L 192.168.1.2 added interface ip=192.168.1.15 bcast=192.168.1.255 nmask=255.255.255.0 session request to 192.168.1.2 failed (Called name not present) session request to 192 failed (Called name not present) session request to *SMBSERVER failed (Called name not...

I'm close to do a factory reset and starting again from scratch, but that seems like a drastic option with no guarantee that it'll sort the problem. :-(

Previously the CIFS package was installed but the Samba package wasn't. (After reinstalling the CF all the previously installed packages were still there.) However, I installed Samba but it made no difference. I'm not much a of a linux person I'm afraid. Anyone know of any diagnostic...

Yes, it's pingable. Nothing changed on the router, server, etc. The only change is the reinstall of the latest CF.

I tried a cold boot of both the Humax and the PC. didn't try the fix flash packages, but just tried that, cold booted and still can't connect.

No joy, same error - "No such device or address"

Like a few people, I didn't protect myself against the OTA update on Thursday and lost the custom firmware. I've since re-installed the latest 2.22 CF and my webif and telnet access are back. But, no I can longer access my Windows shared folders. I had a few shared folders mounted - following...