samba - Jan 2000 - SAMBA digest 2385 / setting samba when you are a dhcp client

Evan Panagiotopoulos wrote:
>Last year I used samba as my Linux file server and my students and I were 
very happy with it. Now >"they" have connected the lab to the
district's
WAN and they haven't provided us with a file server. I >install
Red
>Hat Linux 5.2 with dual boot on a computer just to see if it can be done 
and I don't have a lot of success >with it.
>When Linux boots up and it starts the smb and nmb processes it waits there 
for a very long time. I read >the address it is given and I can ping it 
from a computer but the  same computer when I click on
Network
>Neighborhood I get an error message that a network doesn't exist, or 
something close to that.
>Do you have any suggestions?
Hi,

If I understood you correctly, your Samba server receives its IP-Address 
from a DHCP server. To use Samba in such an environment you have to use 
Samba 2.0.6. It can deal with logical interface names instead of physical 
IP-Addresses. You have to specify "interfaces = net0" in your
smb.conf,
assuming that net0 is the logical name of your network interface.

Best regards,

Axel Neumann

Evan Panagiotopoulos wrote:
>Last year I used samba as my Linux file server and my students and I
were
very happy with it. Now >"they" have connected the lab to the
district's

WAN and they haven't provided us with a file server. I >install
Red
>Hat Linux 5.2 with dual boot on a computer just to see if it can be
done
and I don't have a lot of success >with it.
>When Linux boots up and it starts the smb and nmb processes it waits
there
for a very long time. I read >the address it is given and I can ping it
from a computer but the  same computer when I click on
Network
>Neighborhood I get an error message that a network doesn't exist, or
something close to that.
>Do you have any suggestions?
Hi,
    I ever met something similar. My suggestion is to update the file
"/etc/hosts" in you linux everytime after you get an IP address from
the
DHCP server. Because the samba will look the host mapping (IP and
host.domain) by default. And you are a DHCP client, so everytime you
boot up, it may get different IP address from your previous boot (and
you don't have a real host.domain in the LAN). So the samba couldn't
find the current map from linux or LAN. It will take long time to boot
in start samba.
    You can add a script to update the "/etc/hosts" in the boot
sequence. (Of course, before the samba start script) So the
"/etc/hosts"
always contains the current host mapping information. Then the problem
will gone. :-)
Regards

Vincent Kuo




_________________________________________________________
 pchome §K¶O¹q¤l«H½c¡A¥Ó½Ð½Ð¦Ü: http://www.pchome.com.tw