File Browser Authentication Failed

[kcchesnut]

I go to Folders - Browse the Local Network - it says Authentication Failed, enter username and password. I have no clue why? My LAN is not password protected. Is it automatically trying to connect to another computer or NAS ... if so, how can I tell which one?

What I'm expecting it to do : I go to Folders - Browse the Local Network, it lists my networks, then when I select a group, it lists the NAS and computers, and when I select a device then it prompts for username and password (if needed).

Or is there a place for me to manually enter SMB/NFS paths?

Before failing to browse, it does see a Windows Home Server with UPnP and a Windows computer (not sharing any files). Ultimately it should browse 3 NAS devices running both SMB and NFS, and that same Windows Home Server running SMB.

Its on a LAN and has the latest firmware.

I have an XBMC and Popcorn Hour. They can both browse the network without any issues.

Thanks,
casey

[HeadHodge]

Originally Posted by kcchesnut

I go to Folders - Browse the Local Network - it says Authentication Failed, enter username and password. I have no clue why? My LAN is not password protected. Is it automatically trying to connect to another computer or NAS ... if so, how can I tell which one?

What I'm expecting it to do : I go to Folders - Browse the Local Network, it lists my networks, then when I select a group, it lists the NAS and computers, and when I select a device then it prompts for username and password (if needed).

Or is there a place for me to manually enter SMB/NFS paths?

Before failing to browse, it does see a Windows Home Server with UPnP and a Windows computer (not sharing any files). Ultimately it should browse 3 NAS devices running both SMB and NFS, and that same Windows Home Server running SMB.

Its on a LAN and has the latest firmware.

I have an XBMC and Popcorn Hour. They can both browse the network without any issues.

Thanks,
casey

I don't know if my experience is useful for you. But I've had a lot of the same problems you seem to have.

When I use the HD200 to access Shared Directories from my VISTA pc's on my LAN, I was getting authentication failed messages too.

After a lot of experimenting, I finally figured out there is some sort of symbiot like relationship between the file security settings set for the directory and the directory sharing security settings set for the directory.

It appears that the file security settings take precedence over the sharing security properties for a directory. So no matter what you set the sharing security to, it may not give you the results your expecting.

For example, if I set my Shared Directory "MEDIA" to the user "Everyone" with full access and then I set the file security on the same directory "MEDIA" to only allow the "Administrators" access to the directory, you can only access this directory from the HD200 by providing the HD200 with a user id and password that has Administrator rights for that computer.

If I then add the user "Everyone" to the file security settings for the directory "MEDIA" and give this user read-only rights, I can then access the directory from the HD200 without providing a user id, but can only read the files in the directory. I can't delete any files even though the Sharing permissions for the directory is set to give full access to the user "Everyone".

If I change the file security setting on the directory "MEDIA" to allow the user "Everyone" to have full access rights to the directory I can then access the file from the HD200 and delete files without having to provide a user id.

If I change the Sharing security rights on the "MEDIA" directory for the user "Everyone" to read only, I cannot delete a file on that directory from the HD200 even though the security file access rights is set to full access on the "MEDIA" direcotry for the user "Everyone".

So to get around all this, the security rule I made for my VISTA pc's on my LAN is to set the security setting for every Shared Directory with only one user "Everyone" with full access to the shared directory.

Then I set the file security settings on the directory to suit my security needs as desired. So for my Shared Directory "MEDIA" I have multiple users in the file security settings including the user "Everyone", which has read-only rights. For another Shared directory "DOCUMENTS", I don't have the user "Everyone" included in the file security settings, so no one can access that directory unless they can log on as an authorized user.

So just when I think I've got it all figured out, I purchased a NAS server that uses SIMBA SMB for file sharing. The NAS security appears to work exactly the opposite as does the security for VISTA. It seems that whatever you set the Shared Directory permissions to, that takes precedence over any individual settings you may have set for that directory.

For example if I set the security setting for the Shared Directory "MEDIA" for the user "USERS" with full access, I can delete files on that directory from the HD200 even if I give a more restrictive access right to individual users for that directory.

Also it seems that the user group "USERS" refers to only users that are set up on the NAS server. In order to get the VISTA equivalent of the user "Everyone" on the NAS server I had to enable the "Guest" user on the box. So now the user "USERS" refers to Everyone accessing the box.

On hind-sight, it all seems so obvious to even the most casual observer. Too bad I haven't gained any hind-sight yet.

(EDIT: I forgot to say, I think that a majority of these types of problems would be eliminated if the HD200 standalone "SERVER" setup option provided a way to use a default UserID and Password. That way I wouldn't have to jump through a lot of hoops to properly set up my networks security to make Sage happy.)

[kcchesnut]

My problem doesnt seem to be file/directory permission related;
instead the problem seems to be with having multiple network workgroups.

I ended writing Sage support directly, whom told me how to turn on debugging.
So I turned on debugging and also enabled the HD200 to act as a Windows File Server in Workgroup (to copy the debug log).

At that point, when I went to browse the network, it actually listed both my networks. And I could drill into the 'Workgroup' network and see all the devices, play videos, etc ... that part worked as expected One of those devices is actually password protected, but it doesnt prompt me for the password until I actually select the device ... and that works as expected.

Anyway, my guess is that by putting the HD200 into the 'Workgroup' network is what made it see and work with the other devices in that workroup.

But my other network is still unusable. As soon as I select the other workgroup name 'FOO', it gives the authentication failed message, before it even lists the devices, one of which could potentially be password protected (although they aren't).

So I moved one of the NAS devices from 'FOO' to the 'Workgroup' network, and it shows up and works perfectly without changing any file or directory permissions.

That makes me think that the HD200 just has problems with devices that aren't in the Workgroup domain? But there isn't anything special about my network, the XBMC and Popcorn Hour handle the 2nd domain without any issues.

Also tried the beta firmware, it didn't fix the problem either.

Thanks,
casey

[HeadHodge]

Originally Posted by kcchesnut

My problem doesnt seem to be file/directory permission related;
instead the problem seems to be with having multiple network workgroups.

I ended writing Sage support directly, whom told me how to turn on debugging.
So I turned on debugging and also enabled the HD200 to act as a Windows File Server in Workgroup (to copy the debug log).

At that point, when I went to browse the network, it actually listed both my networks. And I could drill into the 'Workgroup' network and see all the devices, play videos, etc ... that part worked as expected One of those devices is actually password protected, but it doesnt prompt me for the password until I actually select the device ... and that works as expected.

Anyway, my guess is that by putting the HD200 into the 'Workgroup' network is what made it see and work with the other devices in that workroup.

But my other network is still unusable. As soon as I select the other workgroup name 'FOO', it gives the authentication failed message, before it even lists the devices, one of which could potentially be password protected (although they aren't).

So I moved one of the NAS devices from 'FOO' to the 'Workgroup' network, and it shows up and works perfectly without changing any file or directory permissions.

That makes me think that the HD200 just has problems with devices that aren't in the Workgroup domain? But there isn't anything special about my network, the XBMC and Popcorn Hour handle the 2nd domain without any issues.

Also tried the beta firmware, it didn't fix the problem either.

Thanks,
casey

The problem is obvious. The workgroup 'FOO' needs to be renamed to 'FOOBAR'. (Just kidding)

I've sorta had that problem as well. Even if I power plug reboot the box, it still exhibits the problem. But then I did like you did and moved each device to another workgroup "one at a time" and tested. And they all showed up and worked in the new workgroup fine.

Since you have two "real" Workgroups instead of one. It would be interesting to try moving some of the devices to a third workgroup to see what happens. (I've never tried that)

Then when the original workgroup disappears from the list, start moviing them back to the original workgroup and they continue to work ok.

It's totally a mystery to me, but I was able to resolve my problem that way.

[HeadHodge]

Originally Posted by kcchesnut

Or is there a place for me to manually enter SMB/NFS paths?

I forgot to mention in my last post that when I couldn't access or find a shared network by browsing, I discovered that if you use the HD200 in extender mode to access a Sage server, the Sage server has an option to manually enter the network path of the Directory Share instead of browsing.

I used that successfully to access shares that weren't listed (for whatever reason) in the browser funtion.

However it seems to only be available on a Sage Server. It would really be nice if that feature was enabled on the HD200 in standalone mode as well.

[kcchesnut]

Interesting.
The only thing i've tried so far is changing the HD200 to be in the 'FOO' network, instead of 'WORKGROUP'. When I did that, it still worked with the devices in 'WORKGROUP', but 'FOO' still failed.

Thanks for the tip about entering paths directly with Sage Server. That will motivate me to get one setup.

casey

[Vaskill]

Originally Posted by kcchesnut

Interesting.
The only thing i've tried so far is changing the HD200 to be in the 'FOO' network, instead of 'WORKGROUP'. When I did that, it still worked with the devices in 'WORKGROUP', but 'FOO' still failed.

Thanks for the tip about entering paths directly with Sage Server. That will motivate me to get one setup.

casey

I seem to be having the same problem after upgrading to the latest firmware.

Can't find a resolution, but found this similar thread.

http://forums.sagetv.com/forums/show...ug+mode&page=2

Beginning to wonder if something got broke.