[FIXED] HD-200 Arrived Today: Not a good start....

[gplasky]

Originally Posted by Slack

I have poked around in Frontview looking for anything that would make sense. There seems to be no config option for 'guest' access in any of the cifs configuration dialogs i can see. I will go search the ReadyNAS boards.

Perhaps a firmware update.

Then just create the guest account and give it access to the share.

Gerry

[stanger89]

If you weren't getting prompted for access without the Guest access enabled, then it sounds like you're not running the latest beta firmware on the HD200. That or Sage will want to know about it to see why it wasn't

[Slack]

I think something else is afoot.

I added a password to the share (something I have done in the past) and sure enough HD-200 asks for credentials as soon as I touch the passworded share in the Sage browser. So enter username and password, and I can continue browsing. Yet playback still fails.

The VERY SAME credentials work for the xbox running XBMC...



Yet fail for the HD-200. From the log....

Tue 1/1 0:27:59.338 [AsyncWatch] RequestLocalSMBAccess called smbPath=smb://Guest:xbox@READYNAS-99/share/Video/Movies/Keepers/Blade Runner/Blade Runner.avi
Tue 1/1 0:27:59.340 [AsyncWatch] Executing process: [sh, -c, mount -t cifs | grep -i "/tmp/sagetv_shares/readynas-99/share"]
Tue 1/1 0:27:59.475 [AsyncWatch] SMB Mount Path: //Guest:xbox@readynas-99/share /tmp/sagetv_shares/readynas-99/share
Tue 1/1 0:27:59.482 [AsyncWatch] Updated SMB path with IP address to be: //192.168.1.99/share
Tue 1/1 0:27:59.484 [AsyncWatch] Executing process: [/sage/mount.cifs, //192.168.1.99/share, /tmp/sagetv_shares/readynas-99/share, -o, username=Guest,password=xbox,iocharset=utf8]
Tue 1/1 0:27:59.767 [AsyncWatch] SMB Mount Failed res=-1
Tue 1/1 0:27:59.771 [AsyncWatch] processOptionsMenu optionsMenu=default:null|OptionsMenu:Video File Playback Error

I'm gonna go wash my car. This is getting a bit too tedious.

[bluenote]

Have you upgraded to the beta extender firmware? I believe I had this problem (similar) until I did.

Oops, looking back it sounds like you already have. Make sure your uppercase/lowercase credentials are being entered properly.

[Slack]

Originally Posted by cnovak

Make sure your uppercase/lowercase credentials are being entered properly.

You can see from the log file that the credentials are EXACTLY as they are for the xbox. Xbox works. HD-200 does not. Same share. Leads me to believe fault lies with HD-200.

It should not be this hard.

Sage support suggests upgrading to '1230' firmware. when I get back in town I will try this.

[stanger89]

First make sure you're running the beta firmware (should be 20090128 IIRC). If that doesn't fix it, submit a support request (http://sagetv.com/bugs.html), they were eager to get to the bottom of it when I was having trouble.

[Slack]

I am running 200901298 0.

Sage support suggestion for '1230' seems mis-guided.

[Narflex]

Can you telnet into the HD200; (login is root) and then run this command:

/sage/mount.cifs //192.168.1.99/share /tmp/sagetv_shares/readynas-99/share -o guest,iocharset=utf8

Then post whatever it prints out. Should be more detailed than the 'res=-1' error

[Slack]

Mount Error 13: Permission denied.

Now I tried this first with your code snippet, ad the ReadyNAS with NO PASSWORD on 'share'.

Next I added the password 'xbox' to the share.
Then I tried telnetting again with this...(I inserted 'Guest' and 'xbox' for credentials, syntax per the logs)

/sage/mount.cifs //192.168.1.99/share /tmp/sagetv_shares/readynas-99/share -o, username=Guest,password=xbox, iocharset=utf8

And the HD-200 prompted me for a password. Which I supplied....And still get Mount Error 13: Permission denied.

I tried again to make sure I didn't mis-type 'xbox'. caps lock was not on etc.... Same thing.

Some background.... The ready has 3 (maybe more) security modes

• Share
• User
• Domain

Share mode is what I have been using. And for the two share I have defined on the ReadyNAS - I have left the password blank. So all xboxes and pc can map drives and/or get to the data without supplying user and password.

If I add a password to the share definition, then the xboxes will work if I add 'Guest' as username, and 'xbox' as password into the source definition. I used this in the past when I granted a neighbor wifi access to my 'Music' share but wanted to prevent him access to my 'share' share.

I have never used the ReadyNAS's user mode security. Because frankly I think it's overkill for a home network in which I control all access. But In order to get the ReadyNAS to display the check box 'Allow Guest Access' it appears I have to revert to user mode security.

http://www.readynas.com/forum/viewto...p?f=23&t=25328

I will have to try that - but it will have to wait until I am back home. And I don't think I should have to. And will only do it to satisfy my curiosity. I bought the HD-200 to be a Sage extender (and it has worked great with my OTA-HD stuff) Standalone mode is gravy, but not in my long term plans (ATM).

Edit: Recall that when I have the password enabled in share mode. When I browse the network from the HD-200, as soon as I get to 'share' I am asked for credentials. If I enter them right, I can proceed to browse 'share'. Doesn;t that imply that the creds are good, and should be good to go when it comes time to mount?

[stanger89]

Try not using "Guest" as the username for your shares.

It's possible the permissions are hosed on your files, such that the samba Guest user has access to the directories but maybe not the files?

[Narflex]

Give this one a try too:

/sage/mount.cifs //192.168.1.99/share /tmp/sagetv_shares/readynas-99/share

And if you could ask in that other forum what options they think would be needed to pass to mount.cifs in order for it to mount correctly; that'd help out a bunch. We're VERY interested in fixing this so you wouldn't have to make any changes to your NAS config.

And the browsing/pic viewing on the HD200 uses a different piece of software then music/video playback does when accessing the network. It's for performance & API reasons. But that's why you're seeing different results with regards to the share access.

Thanks!

[Slack]

/sage/mount.cifs //192.168.1.99/share /tmp/sagetv_shares/readynas-99/share

resulted in a password prompt
leaving blank and hitting enter gets: mount error 13.

try again, enter 'xbox' gets: mount error 13.

Edit:
question asked in 'other forum' - but traffic there is considerably less there that here.

[Narflex]

They posted this in their forums:

/sage/mount.cifs //192.168.1.99/share /tmp/sagetv_shares/readynas-99/share -o username=share,guest

Can you give that a try and let us know? I read in another thread on their forums where they mentioned using 'share' or the name of the share as the username in this case.

[Slack]

/sage/mount.cifs //192.168.1.99/share /tmp/sagetv_shares/readynas-99/share -o username=share,guest

No errors
Just another prompt "STP-HD200[/]#"

Do I need to unmount it now? No one is using the HD-200 in my absence. At least I don't think the wife and kids are up to speed on it.

[Narflex]

Cool. So now if you do:

ls /tmp/sagetv_shares/readynas-99/share

do you see a listing of what's on that share?

[Slack]

Will have to wait until Saturday to answer that one.

I just remoted in, and the HD-200 is not responding to pings, and opening it in telnet results in a timeout. Can't be sure what's going on till I am back home.

[Slack]

Originally Posted by Narflex

do you see a listing of what's on that share?

Yeah I see a listing of every dir on 'share'.



So what is next.

[Narflex]

We'll make a new beta firmware w/ this issue fixed in it. I'll have an update for you later on when that'll be.

[Narflex]

OK, we've got a new beta firmware available for the HD200 which should address this specific issue. Just type 'beta' on your remote when you're on the System Update screen. Let me know the results please.

[Slack]

Sorry out of town again. Will know something Friday.

Originally Posted by Narflex

OK, we've got a new beta firmware available for the HD200 which should address this specific issue. Just type 'beta' on your remote when you're on the System Update screen. Let me know the results please.