Nils Østbjerg wrote:
> Hi,
>
> On Mon, Jan 19, 2009 at 12:49:24AM +0100, Harm wrote:
>
>> Hi,
>>
>> please verify the workings through connecting on IP. You should also
>> check logfiles and try the login from another workstation.
>>
>> CIFS is the protocol used since XP/2K3 and NetBIOS is just plain old...
>> I use a plain simple smb config here and connect to a public share using
>> cifs and the dns name of my fileserver without any problems (so no need
>> for that modified etc/master).
>
> Problem is that dns resolve to 130.225.62.250, where as NetBIOS resolv
> to diffrent ip's depending on which network the client is on. This is by
> design, and works fine when using NetBIOS name resolution.
>
> I would prefere to use cifs, but then I need to get the libnss_wins.so
> module into the initrd, not to mention getting it working.
you can also use DNS to provides specific resolving order depending on
the client's network and then have the same comportment than NetBIOS
(that you could forget).
If you use ISC Bind DNS server:
$ cat /etc/named.conf
<snip>
options {
##
## sorlist: the DNS server answer depend on the client network
## IP addresses are returned in the order of the network listed
## below.
## It has an effect only for entries that have multiple A records on
## the different networks listed here.
## This multiples records are usefull for network services
## that must be localized, such as infra.mycorp.net, etc.
## All DNS servers MUST HAVE the same sortlist.
## The 2 concerned networks are 192.168.50.0/24 and 192.168.72.0/24.
sortlist {
{ 192.168.50.0/24; { 192.168.50.0/24; 192.168.72.0/24;}; };
{ 192.168.2.0/24 ; { 192.168.50.0/24; 192.168.72.0/24;}; };
{ 192.168.6.0/24 ; { 192.168.50.0/24; 192.168.72.0/24;}; };
{ 192.168.7.0/24 ; { 192.168.50.0/24; 192.168.72.0/24;}; };
{ 192.168.11.0/24; { 192.168.11.0/24; 192.168.50.0/24;
192.168.72.0/24;}; };
{ 192.168.155.0/24; { 192.168.155.0/24; 192.168.72.0/24;
192.168.50.0/24;}; };
}; # sortlist
<snip>
}; # options
<snip>
Then "distributed" DNS name must have A records:
$ nslookup foo.mycorp.net
Server: 192.168.50.1
Address: 192.168.50.1#53
Name: foo.mycorp.net
Address: 192.168.50.68
Name: foo.mycorp.net
Address: 192.168.72.1
But depeding on the client's network, the first IP address (that is
effectively used ) is always ruled by the "sortlist" option of BIND
configuration:
[192.168.50/24 client] $ host foo.mycorp.net
foo.mycorp.net has address 192.168.50.68
foo.mycorp.net has address 192.168.72.1
[192.168.72/24 client] $ host foo.mycorp.net
foo.mycorp.net has address 192.168.72.1
foo.mycorp.net has address 192.168.50.68
my $0.02
Pierre Bourgin
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel
