i have an issue with getting my laptop to see my solo2 in the network browser of my windows 7 laptop.
i have the solo2 connected to my bb hub with ethernet cable and have internet access on the box.
i can ftp to the solo2 and access the webif in firefox browser on the laptop and also stream to the laptop using the webif.
i have installed nfs and samba server on the solo2 but i cant seem to get a share set up from the laptop to the solo2.
i have tried turning off the firewall on the hub/router but i cant see any settings for windows firewall in case this is whats causing the problem.
i previously could see the solo2 in the network browser on the laptop but that was a few s/w versions ago and i have done a couple of fresh installs to upgrade. also windows has done a few automatic updates since i was last able to see my box on the network on the laptop.
i have another pc which is also connected to the router with ethernet cable and i can see it ok.
any help appreciated
thanks
ham
Have you installed samba and NFS on the SOLO2 - its in the network menu
Have you installed samba and NFS on the SOLO2 - its in the network menu
yes samba and nfs installed on solo2 see paragraph 4 :)
Hi m8 ive been messing for a couple of weeks with raspberry pi and my solo2 same thing could'nt see vu in network. i have just seen enable Upnp in my router settings
mine now works. i had read your post and thought it could be something of the same for you
Hi m8 ive been messing for a couple of weeks with raspberry pi and my solo2 same thing could'nt see vu in network. i have just seen enable Upnp in my router settings
mine now works. i had read your post and thought it could be something of the same for you
cheers mate but i did check that Upnp was enabled in router settings.
i have installed min-dlna on the solo2 and can now see vusolo2:root in my network page but it is listed under media devices and when i click on it it opens windows media player but there are no paths to any directories on the solo2 just list of libraries of pictures video etc which are all empty.
i am a bit of an amateur when it comes to networking but i just cannot understand what is going on.
one further thing i have found is that in samba log on the solo2 is is listing the error:
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 1 (min password length), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 2 (password history), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to change password), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password age), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count minutes), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout attempt), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0
[1970/01/01 01:00:09, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0
[1970/01/01 01:00:13, 0] /home/vix/oe-alliance/builds/openvix/gb800solo/tmp/work/mips32el-oe-linux/samba-3.0.37-r5/samba-3.0.37/source/lib/pidfile.c:pidfile_create(112)
ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 339 is running.
[1970/01/01 01:00:14, 0] smbd/server.c:main(984)
standard input is not a socket, assuming -D option
[1970/01/01 01:00:14, 0] /home/vix/oe-alliance/builds/openvix/gb800solo/tmp/work/mips32el-oe-linux/samba-3.0.37-r5/samba-3.0.37/source/lib/pidfile.c:pidfile_create(112)
ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 339 is running.
[2013/03/23 09:11:43, 1] smbd/service.c:make_connection_snum(1042)
192.168.0.6 (192.168.0.6) connect to service Root initially as user root (uid=0, gid=0) (pid 511)
[1920/05/07 12:54:45, 1] smbd/service.c:make_connection_snum(1042)
192.168.0.6 (192.168.0.6) connect to service Harddisk initially as user root (uid=0, gid=0) (pid 511)
[1970/01/01 01:01:28, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[1970/01/01 01:01:28, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[1970/01/01 01:14:28, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[1970/01/01 01:14:28, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[1970/01/01 01:27:30, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[1970/01/01 01:27:30, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:42:48, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:42:48, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:42:48, 1] smbd/service.c:close_cnum(1239)
192.168.0.6 (192.168.0.6) closed connection to service Harddisk
[2013/03/23 09:42:48, 1] smbd/service.c:close_cnum(1239)
192.168.0.6 (192.168.0.6) closed connection to service Root
[2013/03/23 09:42:48, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:42:48, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:56:49, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:56:49, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:56:49, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 09:56:49, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 10:10:50, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 10:10:50, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 10:10:50, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/23 10:10:50, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
here is also the samba.conf file
[global]
load printers = no
guest account = root
log file = /tmp/smb.log
log level = 1
security = share
server string = Dreambox %h network services
workgroup = ViX
netbios name = %h
case sensitive=yes
preserve case=yes
short preserve case=yes
socket options = TCP_NODELAY
preferred master = no
local master = no
oplocks = no
[Root]
comment = Everything - take care!
path = /
read only = no
public = yes
guest ok = yes
[Harddisk]
comment = The harddisk
path = /media/hdd
read only = no
public = yes
guest ok = yes
i tried removing samba and re-installing but the result is the same but i dont know if thats where the problem is?
ham
Update
i managed to get to the bottom of why my laptop couldnt see my solo2 in my network browser even though i could webif into it ant ftp to it and ping it successfully.
it must have been to do with the way windows 7 deals with cifs shares using samba.
after many hours trawling the net i found this guide and changed the samba.conf file accordingly and restarted the box and hey presto the solo2 appeared instrantly on my network making it just a bit more straightforward, - for me anyhow, to access the hdd and share files etc between my laptop, pc and solo2.
i just couldnt understand why the solo2 appeared to be invisible even though i could browse into it etc.
maybe someone else can find this useful
ham
Problem 1:
Ubuntu sometimes has trouble browsing shares in workgroups that it is not a member of. It can help if you make sure that all the computers in your network belong to the same workgroup. However, even if this is not a problem it's not a bad idea (unless you have reason to do otherwise) to have your workgroup homogeneous because it can ease the difficulty of troubleshooting.
By default, Ubuntu is a member of the “WORKGROUP” workgroup, but not all Windows computers use this convention. In order to correct this problem, you’ll need to verify that all your Windows computers belong to the same workgroup. In order to check/change that, please see this Microsoft support document: http://support.microsoft.com/kb/295017
If you prefer to change Ubuntu's workgroup, please see "Problem 2".
= = = = = = = = = = = = = = = = = = =
Problem 2:
To fix this problem will require some editing of configuration files via CLI. There are easier ways to change the workgroup that Ubuntu belongs to, but many of these methods also tend to cause other problems.
The best and most reliable way to change Ubuntu's workgroup is by editing the /etc/samba/smb.conf file. This means that it may be easier to assign all of your Windows computers to the “WORKGROUP” workgroup (as outlined under "Problem 1"). Otherwise, use the following directions to edit /etc/samba/smb.conf in order to change the workgroup that Ubuntu is a member of.
Problem 2 - part 1
Open this file for editing with the following command:
Code:
gksudo gedit /etc/samba/smb.conf
Scroll down to the section that looks like this:
Code:
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
Change “WORKGROUP” in “workgroup = WORKGROUP” to match your Windows workgroup.
Problem 2 - part 2
It may also help to add netbios name = computer-name just below "workgroup = WORKGROUP".
Your "computer-name" can be anything, but common convention is to use the name you gave it when you installed Ubuntu (everything after the "@" symbol on the CLI prompt).
For example, here's my CLI prompt:
Code:
dmizer@shinkansen:~$
And here's my smb.conf file:
Code:
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
netbios name = shinkansen
Now, save the file by clicking on "File" > "save", close gedit, and restart samba with the following command (Pre Jaunty):
Code:
sudo /etc/init.d/samba restart
= = = = = = = = = = = = = = = = = = =
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.