Hardware - Support > Network

network share drives me mad

(1/5) > >>

greenisland:
WOW - Thank you for those suggestions!

I will implement them and eventually report back!

Wirezfree:
Hi greenisland,

Sorry for the late follow-up, having a couple of issue with a new install.
On this new install, I followed my own guide, and all my networking/sharing worked out fine.
Here are a couple of things I do,
They maybe redundant legacy things from when I had Windows/Linux, but they still work for me.

Before I start on network setup and sharing I install various packages:

--- Code: ---sudo apt-get install system-config-samba cifs-utils libnss-winbind winbind gvfs-backends
--- End code ---

Then when doing the samba.conf file, I also add these 2 lines in the Global section
name resolve order = bcast host lmhosts wins
local master = no
This helps in name resolution & lookup, and stops various PC's competing for "who is master browser"

Then I do:

--- Code: ---gksu leafpad /etc/nsswitch.conf
--- End code ---
and change the hosts line, add the wins:

--- Code: ---hosts: files mdns4_minimal [NOTFOUND=return] dns
--- End code ---
To this:

--- Code: ---hosts: files mdns4_minimal [NOTFOUND=return] wins dns
--- End code ---
This helps in name resolution & lookup.

A couple of commands that I have found useful in checking everything is showing up.?


--- Code: ---smbtree
--- End code ---
and

--- Code: ---nmblookup -S <your_workgroup_name>
--- End code ---

like:

--- Code: ---nmblookup -S WORKGROUP
--- End code ---

Can't think of anything else

Dave

greenisland:
Thank you Dave, I feel quite sure also that this is not a Linux Lite issue.  The difficulties of mounting network drives (especially those on Windows computers) have plagued me for years across PCLINUXOS, Puppy, Solydxk, and now my new favorite distribution.  I read similar posts elsewhere and my pet theory is that this is one of those things that results from networking, and especially networking to windows machines, not being a first priority in the linux world itself.

Wirezfree:
Hi greenisland,

Thanks for the update and trials.
Hang in there, I find it hard to believe it's a LL issue.
I'm doing another install tomorrow/Saturday.
I will be using the rc.local method, I will reverify my steps,
just in case I have missed something to pass on to you.

Dave

greenisland:
Thank you Wirezfree and N4RPS for the suggestions. 

Along the lines of the above suggestions using sleep, someone (I think on the PCLINUX forum in the past) suggested this as a script in the rc.local file to make sure that the device was connected to the network before attempting to mount.  I used this is in the past with some success, so thought it might be worth adding here:

RC.LOCAL
       
        ( until ping -q -W4 -c1 google.com &>/dev/null; do
            sleep 5
          done
          mount /mnt/<servername>
        ) &
 
----------------------------------------

But that doesn't seem to be doing the trick for me this time, probably for the reason wirezfree says -- there's something about issuing the command once that makes it work the second time through, and I don't think it's because the wireless came up at that point. 

Just in case I wasn't clear before, this is a concern for me because I use some windows programs in Crossover/wine that don't seem to work properly unless the network drive is "mounted" to the file system.  I realize that's a kind of rare need, so it may not affect most people, who simply want a method of transferring files back and forth.  I think, that having fully mounted through fstab may be important for programs that hold files open for a long period of time (such as database programs, perhaps).

I did some more reading on the links I posted earlier about the bug reports on mount.cifs, and that does seem related to what I am experiencing.

Again, thanks to all, and if I figure this out I will report back.

Navigation

[0] Message Index

[#] Next page