[Samba] multi-homed samba PDC and NetApp filers

Carl G. Riches cgr at u.washington.edu
Fri May 14 18:14:16 MDT 2010


We are having a problem getting a NetApp filer to re-join a samba
domain after a move to a new network.  The filer worked fine with
samba before the move.  Apologies in advance for the long missive.

I've tried the following:

  - re-running the CIFS setup program on the filer
  - removing the problem filer's samba account, replacing it, and
    re-running the setup program on the filer
  - creating a new machine account on the samba server and re-
    running the setup program on the filer

None of these worked.  I also looked through a number of mailing
list postings about NetApp filers and samba but didn't find any-
thing to help.

Has anyone gone through this before and provide insight into 
this problem?

We have the following:

  samba server:
    Red Hat Enterprise Linux 5.3
    kernel 2.6.18 i868
    samba 3.0.33
    multiple network interfaces: 10.142.36.64/27
                                                              10.142.36.96/27
                                                              10.142.36.192/26

  NetApp filer #1:
    NetApp Release 7.2.4L1
    connected through VPN to samba server network 10.142.36.192/26

  NetApp filer #2:
    NetApp Release 7.3.1.1
    connected through VPN to samba server network 10.142.36.64/27

Each filer can ping the samba server.  CIFS connections from each
filer are registered by the samba server and are logged in the file:
  0.0.0.0.log

Each of the filers moved to a new network.  Filer #1 rejoined the
domain but filer #2 can't.

A tcpdump of the unsuccessful transaction is:
10:42:38.137963 IP gcc-fs1.netbios-ns > mead.netbios-ns: NBT UDP
PACKET(137): MULTIHOMED REGISTRATION; REQUEST; UNICAST
10:42:38.138165 IP mead.netbios-ns > gcc-fs1.netbios-ns: NBT UDP
PACKET(137): WACK; POSITIVE; RESPONSE; UNICAST
10:42:58.270693 IP mead.netbios-ns > gcc-fs1.netbios-ns: NBT UDP
PACKET(137): REGISTRATION; NEGATIVE; RESPONSE; UNICAST
10:44:11.627124 IP gcc-fs1.netbios-ns > mead.netbios-ns: NBT UDP
PACKET(137): MULTIHOMED REGISTRATION; REQUEST; UNICAST
10:44:11.627292 IP mead.netbios-ns > gcc-fs1.netbios-ns: NBT UDP
PACKET(137): WACK; POSITIVE; RESPONSE; UNICAST
10:44:32.309202 IP mead.netbios-ns > gcc-fs1.netbios-ns: NBT UDP
PACKET(137): REGISTRATION; NEGATIVE; RESPONSE; UNICAST
10:45:45.665702 IP gcc-fs1.netbios-ns > mead.netbios-ns: NBT UDP
PACKET(137): MULTIHOMED REGISTRATION; REQUEST; UNICAST
10:45:45.665803 IP mead.netbios-ns > gcc-fs1.netbios-ns: NBT UDP
PACKET(137): WACK; POSITIVE; RESPONSE; UNICAST
10:46:06.312676 IP mead.netbios-ns > gcc-fs1.netbios-ns: NBT UDP
PACKET(137): REGISTRATION; NEGATIVE; RESPONSE; UNICAST

Part of the samba log 0.0.0.0.log related to filer #2 is:

[2010/05/14 16:54:52, 3]
nmbd/nmbd_winsserver.c:wins_process_name_registration_request(1138)
  wins_process_name_registration_request: Group name registration for
name UWT-15<00> IP 10.208.235.134
[2010/05/14 16:54:52, 3]
nmbd/nmbd_winsserver.c:wins_process_name_registration_request(1222)
  wins_process_name_registration_request: Adding IP 255.255.255.255 to
group name UWT-15<00>.
[2010/05/14 16:54:52, 4] nmbd/nmbd_packets.c:reply_netbios_packet(940)
  reply_netbios_packet: sending a reply of packet type: wins_reg
UWT-15<00> to ip 10.208.235.134 for id 39786
[2010/05/14 16:54:52, 4] libsmb/nmblib.c:debug_nmb_packet(112)
  nmb packet from 10.208.235.134(137) header: id=39786
opcode=Registration(5) response=Yes
      header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No
auth=Yes
      header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
      answers: nmb_name=UWT-15<00> rr_type=32 rr_class=1 ttl=345600
      answers   0 char ......   hex E0000AD0EB86
[2010/05/14 16:54:52, 5] libsmb/nmblib.c:send_udp(779)
  Sending a packet of len 62 to (10.208.235.134) on port 137


Thanks,
Carl
  



More information about the samba mailing list