| Autor | Nachricht | 
  
    |  | 
        
					| Titel: Samba & net connection boot probs  Verfasst am: 21.08.2006, 16:57 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 21. Apr 2006
 Beiträge: 152
 Wohnort: Ice and Snow
 
 |  | 
        
          | I have finally got winxp box and Linux box seeing and working with each other, but I have a glich. Now, every time I boot the L box, I have to reconfigure the network IP address via kcontrol from 169.254.124.0 to 192.168.7.0 and restart samba. That must mean samba is not loading properly and and something is reconfuring my IP address. I no longer have avahi-daemon or resolvconfig which were mucking up things before, but something else is going to town now. This all started when I found how to configure smb.conf so that the M$ box could see the L box. That part works fine now (except for the fact I have to figure out how to access files I have move from my L box to my M$ box). It will take me a few hours to work on any solutions because I am away from my box all day today.
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel: RE: Samba & net connection boot probs  Verfasst am: 21.08.2006, 18:32 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 16. Aug 2004
 Beiträge: 1905
 
 
 |  | 
        
          | cat /etc/network/interfaces 
 (samba doesn't mess with ip setting, but has to take them in consideration)
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel: RE: Samba & net connection boot probs  Verfasst am: 21.08.2006, 18:45 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 09. Jan 2006
 Beiträge: 1720
 
 
 |  | 
        
          | It is not a pronlem with samba or linux at all, it is a problem how M$ handles the dhcp for private addresses. Specialy when no router is available. |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel: RE: Samba & net connection boot probs  Verfasst am: 21.08.2006, 20:34 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 25. Mar 2005
 Beiträge: 2133
 
 
 |  | 
        
          | 192.168.7.0? Is this the IP address of your machine or the low end of a range of IP addresses? What if you configure your Kanotix box to be the router, give it a static IP address (192.168.7.1) and start dnsmasq + masquerade?
 |  
          | _________________
 And I ain't got no worries 'cause I ain't in no hurry at all (Doobie Brothers, "Black Water").
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel: RE: Samba & net connection boot probs  Verfasst am: 22.08.2006, 04:23 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 21. Apr 2006
 Beiträge: 152
 Wohnort: Ice and Snow
 
 |  | 
        
          | Zitat: 
cat /etc/network/interfaces
 
 iface eth0 inet static
 network 192.168.7.0
 broadcast 192.255.155.255
 address 192.168.7.151
 netmask 255.255.255.0
 gateway 192.168.7.1
 Accually I should learn that obscurity begets obscurity. I am behind a router, and the 2 boxs are connected via a hub. Both boxes are intended to have static IPs. The M$ keeps its IP no prob. The L box is the one having a prob keeping its static IP. Everytime the last two days (the only change other then upgrade that I have done is made changes to smb.conf to get the two boxes comunicating, and I just remembered, ran lisa deamon setup wizard for local network browsing) te IP has  gone to 169.254.124.0 and inorder to get the 2 boxes to comunicate I have to restart samba. I presume that that means smb.conf isn't booting properly at bootup and also there is another apt that I have that is insisting that my IP should be 169.254.124.0. It only takes a couple of minutes to get everything inorder, but the bummer is that it is happening at all.
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 22.08.2006, 08:19 Uhr |  | 
  
    | 
        
          | Team Member 
  
  
 Anmeldung: 04. Apr 2006
 Beiträge: 153
 Wohnort: Melbourne, Australia
 
 |  | 
        
          | Samba may not be 'turned on" at boot up 
 in console as root
 
 unfreeze-rc.d
 rcconf
 
 a blue box comes up, arrow down to samba and use the space bar to put in an "*" (asterisk)
 
 tab to OK
 hit enter
 
 freeze-rc.d
 
 Samba should now commence on boot-up
 |  
          | _________________
 Kanotix Easter RC4 on a dual boot P4 and a production box  Desktop KDE::
 Kanotix 2006 Easter RC4 on a P2 and  Production Box , Desktop KDE::
 Kanotix EasterRC4 on a MMX 199Mhz lappy
 and  a  Production Box,  Desktop ICEWM::
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 23.08.2006, 03:38 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 21. Apr 2006
 Beiträge: 152
 Wohnort: Ice and Snow
 
 |  | 
        
          | Thank You bluewater. Got samba toggled, found lisa on the list, got that toggled, rebooted and man, no more IP probs checked out the M$ box, and for the first time could immediately open up into the folder in the L box that I wanted and could import and export and edit those files, which I have never been able to do. Also I found a couple of other apts that I wanted to check out that I have never been able to look at before. There is no way I will ever return to M$. For the things you have to give up, I tell you the help forums more then make up for it. |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 23.08.2006, 05:30 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 21. Apr 2006
 Beiträge: 152
 Wohnort: Ice and Snow
 
 |  | 
        
          | OOPS. Just checked the L box (M$ box is working fine). I had made some changes in smb.conf that I haad found in onther forum,but now the L box can still ping the M$, but whereas before I got samba and lisa working at boot I could get into the M$ box from the L box, now I cannot get into the M$. Is there something I might have done wrong in smb.conf that would have caused this prob? Noticed there are 2. I had modified /usr/share/samba/smb.conf [global]
 workgroup = ######
 server string = %h server (Samba %v)
 ;   hosts allow = 192.168.7.151 192.168.7.150
 ;   wins support = yes
 ;   wins server = w.x.y.z
 dns proxy = no
 ;   name resolve order = lmhosts host wins bcast
 ;   interfaces = ####### eth0
 ;   bind interfaces only = true
 log file = /var/log/samba/log.%m
 max log size = 1000
 ;   syslog only = no
 syslog = 0
 panic action = /usr/share/samba/panic-action %d
 ;   security = share
 encrypt passwords = no
 passdb backend = tdbsam
 obey pam restrictions = yes
 ;   guest account = nobody
 invalid users = root
 ;   unix password sync = no
 passwd program = /usr/bin/passwd %u
 passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
 ;   pam password change = no
 ;   domain logons = yes
 ;   logon path = \\%N\profiles\%U
 ;   logon path = \\%N\%U\profile
 ;   logon drive = H:
 ;   logon home = \\%N\%U
 ;   logon script = logon.cmd
 ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
 ;   load printers = yes
 ;   printing = bsd
 ;   printcap name = /etc/printcap
 ;   printing = cups
 ;   printcap name = cups
 ;   printer admin = @ntadmin
 ;   include = /home/samba/etc/smb.conf.%m
 socket options = TCP_NODELAY
 ;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
 ;   domain master = auto
 ;   idmap uid = 10000-20000
 ;   idmap gid = 10000-20000
 ;   template shell = /bin/bash
 [homes]
 comment = Home Directories
 browseable = no
 writable = no
 create mask = 0700
 directory mask = 0700
 ;[netlogon]
 ;   comment = Network Logon Service
 ;   path = /home/samba/netlogon
 ;   guest ok = yes
 ;   writable = no
 ;   share modes = no
 ;[profiles]
 ;   comment = Users profiles
 ;   path = /home/samba/profiles
 ;   guest ok = no
 ;   browseable = no
 ;   create mask = 0600
 ;   directory mask = 0700
 [printers]
 comment = All Printers
 browseable = no
 path = /var/spool/samba
 printable = yes
 public = no
 writable = no
 create mode = 0700
 [print$]
 comment = Printer Drivers
 path = /var/lib/samba/printers
 browseable = yes
 read only = yes
 guest ok = no
 ;   write list = root, @ntadmin
 ;[cdrom]
 ;   comment = Samba server's CD-ROM
 ;   writable = no
 ;   locking = no
 ;   path = /cdrom
 ;   public = yes
 ;   preexec = /bin/mount /cdrom
 ;   postexec = /bin/umount /cdrom
 The other one I found which I hadn't touched is /etc/samba/smb.conf and it has
 
 [
 [global]
 
 netbios name = #######
 
 security = share
 map to guest = Bad User
 username map = /etc/samba/smbusers
 socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
 unix charset = ISO8859-1
 printcap name = cups
 printing = cups
 guest ok = yes
 restrict anonymous = no
 domain master = no
 preferred master = no
 max protocol = NT
 acl compatibility = winnt
 ldap ssl = No
 server signing = Auto
 
 [#####]
 path = /home/#####
 read only = no
 
 [DOCUMENTS]
 path = /home/#####/Documents/
 read only = no
 case sensitive = no
 strict locking = no
 msdfs proxy = no
 
 [DOWNLOADS]
 path = /home/#####/Downloads/
 read only = no
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 23.08.2006, 09:29 Uhr |  | 
  
    | 
        
          | Team Member 
  
  
 Anmeldung: 04. Apr 2006
 Beiträge: 153
 Wohnort: Melbourne, Australia
 
 |  | 
        
          | LRC 
 see if this helps in the first instance, to get a grasp of whats happening
 
 http://kanotix.com/FAQ-id_cat-141.html
 |  
          | _________________
 Kanotix Easter RC4 on a dual boot P4 and a production box  Desktop KDE::
 Kanotix 2006 Easter RC4 on a P2 and  Production Box , Desktop KDE::
 Kanotix EasterRC4 on a MMX 199Mhz lappy
 and  a  Production Box,  Desktop ICEWM::
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 24.08.2006, 18:08 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 21. Apr 2006
 Beiträge: 152
 Wohnort: Ice and Snow
 
 |  | 
        
          | Figured out that it is am IP prob and not samba. Once I can get the Ips fixed after bootup (another posting) samjba is working great. Thanx for your input anyway. |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
  
    |  |