Unable to Browse Network in Service Mode

[mlw123]

Running version 7.0.21.244 and in service mode it cant browse the network and see network mapped drives. In GUI mode all it works fine.
I have set the service to local on as the same account that the computer logs on with that has access to the network but it still is unable to see the network share.

The error 'invalid directory' shows when I click on Network in the Media Import dialog.

Sage running on Windows 7
The network share its trying to access is also Windows 7.

Thanks for any help
Mark

[gplasky]

Make sure network discovery is turned on for Win 7. Make sure it is designated as the Home or Private network. Make sure the user account has a password when running the service. I would also put the user account in the Administrators group.

Gerry

[mlw123]

Yep all those are set, also made a home group and add both computers, still will not work in service mode.

Thanks
Mark

[TwistedMelon]

This has been an issue since v6 and I can report I also see it every now and then in both XP and Win7. It hasn't yet been fixed.

On my system I can reproduce it any time I want by simply power-cycling my NAS without restarting the Windows machine.

The issue is that Sage's folder browser is sitting with one of the folders on the NAS as the "current folder" - restarting the NAS, while it doesn't make the whole network disappear obviously, somehow causes Sage to flip out and stop showing the Network browse option at all. The only way to fix the issue is to restart the Windows machine.

I think I've reported it twice to Sage, the last time it was supposed to be fixed in the next version. I can still see the issue now though. I suppose I should send another email...

[Opus4]

Originally Posted by mlw123

Running version 7.0.21.244 and in service mode it cant browse the network and see network mapped drives.

Don't forget that mapped drive letters (if that's what you meant) are not visible to a service.

- Andy

[TwistedMelon]

I don't know about anyone else, but I don't use mapped drive letters in Windows, so it's definitely not what I was talking about. Whatever the case, if there's a network available,then Sage should allow browsing to the network, even if no shares are present. In my case there are always shares on the network.

[dinki]

I _think_ it was possible to browse network shares on v6 but I'm not seeing that on v7. I am able to browse the sage server as well as the import and tv directories through the search function, but I'm not seeing a way to browse the network.

I am running win7 on the sage server as well as the network machine I'd like to browse. I'd prefer not to add this as an import directory. Matter of fact, I wasn't able to add the UNC path to the network machine as an import directory (said directory didn't exist even though I could see it from windows explorer). I am running sage in service mode. I am also using an hd200 as my frontend.

Any ideas?

*EDIT* Somehow missed the earlier thread. I guess this could be merged with that thread as it appears our problems are the same.

[mlw123]

Just to confirm I can see both mapped drives and browse the network in gui mode but in service mode clicking on network after about 5 secs shows the invalid directory error.

Thanks
Mark

[GKusnick]

Make sure you have the service configured to run as a user with appropriate network permissions. LocalSystem (the default) does not have such permission and cannot access network resources.

[nyplayer]

Originally Posted by dinki

I _think_ it was possible to browse network shares on v6 but I'm not seeing that on v7. I am able to browse the sage server as well as the import and tv directories through the search function, but I'm not seeing a way to browse the network.

I am running win7 on the sage server as well as the network machine I'd like to browse. I'd prefer not to add this as an import directory. Matter of fact, I wasn't able to add the UNC path to the network machine as an import directory (said directory didn't exist even though I could see it from windows explorer). I am running sage in service mode. I am also using an hd200 as my frontend.

Any ideas?

*EDIT* Somehow missed the earlier thread. I guess this could be merged with that thread as it appears our problems are the same.

I also do not see where to browse the network on SageTV7 and I am not using the local file system... using a user with full access. I can browse the network outside of sage. I was able to do this in Sage 6.

[mlw123]

I have the service configured as the user who logs in and can map drives and access the network.

Thanks
Mark

[nyplayer]

Well obviously there is something wrong.... with the way Sagetv 7 is doing browsing.... Heck there isn't even a way to browse the network from search... I cannot even browse the network from within sageclients. Yet I can go into network neighborhood and browse all the network computers... from all my clients.

All my clients and Server use the Administrator login with the same password... so network rights is not a problem.


Maybe somebody can post exactly how they browse the network from a inside a sagetvclient maybe even post a screenshot.

[toricred]

Does the user for the service have a password? It will cause problems when in service mode if the user account has a blank password.

[nyplayer]

Yes It logs on as user "administrator" and has a password. Same password and logon on my clients too. Maybe someone can explain why I do not get the option to browse the NETWORK either in my server or clients this was not a problem in version 6... When I can click on network neighborhood and browse all my networked computers without any problems.



Edit

Finally got the browse network and it works. I recently changed to a hardcoded IP on my server... I had my clients connecting by PC name it connected fine and played fine etc... but I could not browse the network.

What I did was change my clients to connect by IP# and not PC name... maybe the users that are having the same problem can try this.

I am sure that just enabling Netbios over tcpip would have fixed it since it is using a hardcoded IP

Thanks to all for your patience.