One Way Samba-Solved

Fri Feb 22 08:37:58 UTC 2008

--- NoOp <glgxg at sbcglobal.net> wrote:

> On 02/21/2008 03:06 PM, Leonard Chatagnier wrote:
> 
> > But it's not mounting now as shown above refering
> to
> > the wrong IP ADDR. Using the right IP, 192.168.1.
> > 65 works.  If anyone can offer some suggestions to
> get
> > my hostname to refer to the current IP and not the
> one
> > before I reconfigured the maching when it was
> > "kubuntu-desktop" and hard wired, I'd be most
> > grateful.
> > Thanks, NoOp for trying. I appreciate it,
> > 
> 
> Here are a couple of general rules that I typically
> follow when setting
> a small home/business DSL network - they may be of
> help, or maybe not &
> others will certainly have their own preferences.
> 
> 1. I ensure that all the fixed computers have fixed
> IP's that are not on
> the same subnet as the gateway router. If for
> example the gateway is
> 192.168.0.1, then my machines would be say
> 192.168.2.100-110 and the
> gateway would be 196.68.2.1. Many routers/modems use
> 192.168.1.1, so I
> make sure to avoid the 192.168.1.x subnet
> altogether. It just makes life
> easier & avoids any possible mistakes in the subnet.
> 
Greek to me. MY IP's are wlan0-192.1268.1.65(was
192.168.1.64 when wired, eth0), eth0-192.168.1.66 and
is hard wired and gateway is 192.168.1.254. That's
what they are on my side of the router/modem combo and
are different on 2WIRE's side but translated to my
assignments(fixed) on their side. When I visit
http:/gateway.2wire.net it shows my netword as listed
above and another set of IP's for the gateway, dns
servers, etc. Hope this makes sense to you, doesn't to
me. They do show a lower range of IP's, don't remember
the range, for static IP's which my IP's are just out
of range. Haven't tried assigning numbers in that
range yet as am afraid to lose connection. Will listen
to any howto suggestions but remember I'm a network
dummy.

> 2. I use the routers dhcp server to issue dhcp for a
> visiting laptop
> etc., but I make sure that the dhcp ranges it issues
> are defined to be
> outside of the range of my fixed machines. In this
> case, I would allow
> it to issue dhcp addresses from 192.168.2.111 to
> 192.168.2.121 for
> example. This avoids the problem of the router
> issuing a dhcp address in
> the 192.168.2.100-110 range when a laptop is
> connected and one of the
> other 'fixed' machines is off at the time. This is
> particularly critical
> if you are running VNC's.
> 
Will not affect me; have no laptop. What's a VNC?

> For your existing problem(s) I'd recommend that you
> check your router
> settings and clear out any previous dhcp address'
> that have been
> previously issued. If the router still has the mac
> address & IP of one
> of your newly reassigned fixed IP's, then there will
> be a conflict.
> 
Sorta what I assumed. But as a network dummy, I don't
know how. Need a guide for my 2WIRE 1701hg gateway, or
a howto, to show me what/how to do it. I've looked for
things like this on 2wire's site and didn't find or
recognize it. I'd like to fix this issue soon, if I
knew how.

> 3. I normally rely on my router for dhcp, firewall,
> fqdn updates, etc.,
> so I also generally put the DSL modem in bridge mode
> depending upon the
> type of DSL modem. For example a Speedstream 5100B
> can cause all sorts
> of problems with dhcp & links when VNC's are used.
> Setting to bridge
> mode and allowing the router to do it's job works
> considerably better.
> 
I have set my wlan0 via KWifiManager to managed and
saw a bridge setting on drop-down menu. KWifiManager
isn't installed on the wired ubuntu64 and Network
doesn't have a setting for this that I can find. I
could install KWifi on both and changed to "bridged"
whatever it means if it would help. The only vnc
component I find installed is xvnc4viewer with only
the apt setup configuration applied. Don't know if
that puts me as using vnc catagory. Should I used
"briged" or not under this circumstance?

> 4. On the Ubuntu machines; go into each one on the
> network settings and
> actually enter the IP Address & Alieses of each of
> the fixed machines
> (System|Administration|Network|Hosts|Add). If
> necessary, check the
> /etc/host file and add them there, example (modified
> for the purposes of
> this post of course):
> 
> 127.0.0.1 localhost mycomputer.mshome
> 127.0.1.1 mycomputer
>
I have did this and rechecked it multiple times just
since this posts. I have entries for 127.0.0.1,
127.0.1.1 and the static IP for each machine. This has
been checked on all the gui's installed on each
machine and in /etc/hosts.
> 
> # The following lines are desirable for IPv6 capable
> hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> ff02::3 ip6-allhosts
> 192.168.2.101 myothercomputer
> 192.168.2.102 my-laptop
> 192.168.2.105 mytestserver
> 192.168.2.103 mywindowsmachine
> 192.168.2.106 myserver
> 
I'll even add the extra IP's(only one on each machine
for me, of course). This is new to me.

> 5. For Gutsy machines: remove & purge apparmor - at
> least until the bugs
> with cups & pdf-printer etc., are worked out.
> Besides, apparmor is
> primarily an enterprise security application & I've
> found that (for now
> anyway) that it is much more trouble than it is
> worth in a small home
> network.
> 
Ok. Is this why I can't print from the remote computer
to the shared printer or is it most likely a setup
issue?

> 6. Don't mess with command line automount smbf
> unless you actually have
> a reason to do so. I have all of my machines set to
> automatically show
> the neighbor shares icon on the desktop and in
> Nautilus & if the other
> machine is alive it automounts just by clicking on
> the icon or the
> machine folder in Nautilus.
> 
Just using the mount cmd to learn. I prefer the
nautilus or dolphin gui also when working and I think
I have that solved.  At least I now have it on both
machines if it sticks. How do you get the desktop
icons? Just drag them from the file browser window to
the desktop?

>   It's really quite easy to do, all you do is
> Places|Connect to
> Server|Windows Share| then:
> 
> Server: 192.168.2.104 (example)
> Name to use for connection: MyOtherMachine
> - Connect
> Bingo, I now have a desktop icon to MyOtherMachine
> and in Nautilus I
> have a network MyOtherMachine network folder.
> 
Ooops, spoke too quick. I could use ubunti-desktop if
I have to but do you know the k-menu command? 
> If I reboot or logout, the icon and network folders
> come up automatically.
> 
> 7. If I have a problem connecting to a
> smb://machinename then I can
> almost always connect using the machine IP address.
> If it's failing on
> machinename, then I go back and check #4.
> 
I wish I could truthfully say I haven't did this yet.

> 8. For connecting to a Windows drive (reboot or
> otherwise), follow the
> instructions in
>
https://help.ubuntu.com/community/ComprehensiveSambaGuide
> pretty much to
> the letter. Works for me.
> 
Thanks Gary. This should get me more progress and is
much appreciated.  I will keep this post in my Debian
folder for reference. I also just spent 3-4 hours on
the gateway.2wire.net support site searching for info
on howto do the router and emailing them for support.
I did eventually find some needed info.  The only
problem is entering a search term gives you 10-15
pages of hits most of which is unrelated. Not
efficient to find answers. After, I devour all this,
I'll try it out and report the results. Appreaciate
your excellent tutorial, I needed it,


Leonard Chatagnier
lenc5570 at sbcglobal.net