[VU+ Solo] VU+Solo + Latest OpenVIX version (Warning future users - Network issues)

[Deleted member 57049]

I was on Openvix 3.0.808 and decided to update to Apollo version (tried 098, 100, 108, 112 and 113) since the feeds were not working.
All worked perfectly EXCEPT the connection to my Network drive. Going through Network Browser (after installing samba and NFS), I could see the IP address from my Network Drive and also from my Laptop, but pressing OK to expand the tree wouldn't work.
I've installed everything more than 10 times, I spent countless hours around this issue.

Gladly I still have a copy of "openvix-3.0.808-vusolo_usb.zip". Reinstalled the old version and all is working again.

Just want to share this since it might help you in the future.

Since I don't have access to feeds, do you know where can I get them? Thanks

 

[judge]

There is no latest version of Apollo. What would that be in a weeks time or a months time to anyone reading this post then?
Please include the build number you currently use with any issue reported.

As for network mounts, all working fine here on various boxes, using NFS on Apollo build 113.

 

[Sicilian]

and moved to correct section, Please read this thread HERE

 

[Deleted member 57049]

Updated post with Apollo version. I guess windows shares don't use NFS, they use Samba. I just wanted to mention that I've installed both.

 

[Sicilian]

Updated post with Apollo version. I guess windows shares don't use NFS, they use Samba. I just wanted to mention that I've installed both.

Still no build version number ..... Menu > Information > About

 

[judge]

I just wanted to mention that I've installed both.

No need to install both if only sharing to Windows, shouldn't do any harm either but best to work with a minimal requirement & get it working using that first.
When you install Samba on the box, are you installing both the server & client?
After it installs Samba & reboots are both your Windows client & box using the same Samba Workgroup?

 

[twol]

As per Judge's comment, you need to ensure smb.conf contains your windows workgroup name

 

[Deleted member 57049]

I have default workgroup name "workgroup" and installed samba the same way I did using 3.0.808, by going into Samba setup, and then it installed from feed.

 

[twol]

I have default workgroup name "workgroup" and installed samba the same way I did using 3.0.808, by going into Samba setup, and then it installed from feed.

Silly question, but on both windows and E2, as "workgroup" was not the default for my windows machines.

 

[cactikid]

i also had an issue on 113 with samba now removed and using nfs when mounting the drives i got an x in red which did not look like it mounted but in going into mounts it showed with a green tick and in checking worked.not checked my nas yet

 

[Deleted member 57049]

I'm still trying to understand why is the 808 network working and not the Apollo.
I don't have any "smb.conf" file on my Vu+Solo, but my shares are working.
Can you help me understand how I have my Solo configured? I'm accessing the receiver via ssh.

 

[Deleted member 57049]

In mounts editor I see this:

FSTAB (mount at boot)
enable
"My Share Name"
CIFS share
"My IP"
"Share"
no
rw, utf8
username
*******


Is there any file in the filesystem with this configuration? Can I copy it to a new installation of Apollo?

 

[abu baniaz]

Have you tried a reflash without restores?

 

[Deleted member 57049]

What do you mean without restores? With Apollo, I never restored any settings, actually it's not even possible to use my 3.0.808 backup in Apollo.

 

[abu baniaz]

I have just installed Samba on my LX3 and I can browse my Reciver from PC with no extra settings setup.

There have been new drivers for the VU receivers. Not sure if this affects Networktivity adversely. Perhaps a fresh install of 115. Enable debug logs and then installing Samba may reveal details of what is going on.

 

[bbbuk]

I too can access my receiver (Solo2) from my laptop (running Win7 pro) without changing any settings on receiver or Samba once Samba was installed.

Within Win7, I've just mapped R: drive to my solo2 (root).

I'm running Vix 112 (just before the VU drivers were updated) but I doubt that would be an issue with latest drivers because VU claim latest drivers fixed multimedia playback or something.

 

[Deleted member 57049]

I guess I found it, this is the content of the "fstab" file which is working properly in my 3.0.808:

root@vusolo:/etc# cat fstab
rootfs / auto defaults 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
usbdevfs /proc/bus/usb usbdevfs noauto 0 0
tmpfs /var/volatile tmpfs defaults 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
//192.168.0.14/Armazem /media/net/Armazem cifs username=username,password=password,_netdev,rw,iocharset=utf8 0 0
//192.168.0.15/Armazem /media/net/Armazem cifs username=username,password=password,_netdev,rw,iocharset=utf8 0 0



Do you think I can just copy this file into a new installation with the new Apollo? Could that work?

 

[Deleted member 57049]

Ok, I've tried the Apollo 115 (01.01.2015) and added my Network drive manually using the configuration from the old version (OpenVIX 3.0 808).
I'm now able to use the network disk, PERFECT.

Note: Network Browser is still not working, must be some bug, it detects the Network Drive (the IP address appears), but when I "press OK to expand this host" nothing shows. Anyway, it's working now

Thank you all for your valuable inputs.