BackupPC-users

[BackupPC-users] Connection failed, nt status bad network name

2013-03-08 16:49:22
Subject: [BackupPC-users] Connection failed, nt status bad network name
From: "Jeff Boyce" <jboyce AT meridianenv DOT com>
To: "BackuPC Mailing List" <backuppc-users AT lists.sourceforge DOT net>
Date: Fri, 8 Mar 2013 13:35:23 -0800
Greetings -

I am setting up BackupPC for the first time and it is failing to connect to 
the first test client.  The error that BackupPC is giving me is shown below.

Error:
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Then later I see this at the top of the Host Summary Page:
Pings to jab-opti755 have failed 23 consecutive times.

I have done a fair amount of Google searching over the last two days, and 
reviewed some of the mailing list archives.  I think I understand what my 
problem is, but don't have the knowledge to identify the proper solution. 
So I am looking for an expert here for advice.  I will explain below my 
network setup, and the what I have tried, to understand the problem.  This 
may be a little long, but I want it to be complete.

My hypothesis, is that I do not have proper NetBios name resolution (or 
caching) occurring within my network.

Servers:
   Sequoia = Samba File Server (192.168.112.50)
   Taxa = DNSmasq and DHCP Server (192.168.112.51)
   Bacteria = BackupPC Server (192.168.112.52)

Approx. 8 desktop systems running Windows Vista or 7, to be backed-up
   jab-opti755 = test backup desktop (192.168.112.125, static address from 
DNSmasq)


>>From Bacteria I can ping jab-opti755

[root@bacteria ~]# ping -c3 jab-opti755
PING jab-opti755.mei.lan (192.168.112.125) 56(84) bytes of data.
64 bytes from jab-opti755.mei.lan (192.168.112.125): icmp_seq=1 ttl=128 
time=0.228 ms
64 bytes from jab-opti755.mei.lan (192.168.112.125): icmp_seq=2 ttl=128 
time=0.237 ms
64 bytes from jab-opti755.mei.lan (192.168.112.125): icmp_seq=3 ttl=128 
time=0.229 ms


However, from Bacteria I can't get a listing of NetBios names.

[root@bacteria ~]# findsmb

                                *=DMB
                                +=LMB
IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION
---------------------------------------------------------------------


My Samba configuration file on Sequoia includes settings for WINS support, 
and DNS proxy.  See portion of samba config file immediately below.

#----------------------------- Name 
Resolution -------------------------------

# Windows Internet Name Serving Support Section:

# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

#

# - WINS Support: Tells the NMBD component of Samba to enable it's WINS 
Server

#

# - WINS Server: Tells the NMBD components of Samba to be a WINS Client

#

# - WINS Proxy: Tells Samba to answer name resolution queries on

#   behalf of a non WINS capable client, for this to work there must be

#   at least one   WINS Server on the network. The default is NO.

#

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names

# via DNS nslookups.


;               wins support = yes

;               wins server = w.x.y.z

;               wins proxy = yes

;               dns proxy = yes

wins support = yes

dns proxy = yes



My DNSmasq configuration file on Taxa include settings for NetBios.  See 
portion of DNSmasq config file immediately below.

# The following DHCP options set up dnsmasq in the same way as is specified

# for the ISC dhcpcd in

# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt

# adapted for a typical dnsmasq installation where the host running

# dnsmasq is also the host running samba.

# you may want to uncomment some or all of them if you use

# Windows clients and Samba.

#dhcp-option=19,0           # option ip-forwarding off

#dhcp-option=44,0.0.0.0     # set netbios-over-TCP/IP nameserver(s) aka WINS 
server(s)

#dhcp-option=45,0.0.0.0     # netbios datagram distribution server

#dhcp-option=46,8           # netbios node type

dhcp-option=44,192.168.112.50     # Wins (samba) Server is on Sequoia

dhcp-option=45,192.168.112.50     # Wins (samba) Server is on Sequoia

dhcp-option=46,8



The IP configuration on my desktop system (Win Vista) has NetBios over 
TCP/IP enabled.  See desktop IP config immediately below.

Windows IP Configuration

   Host Name . . . . . . . . . . . . : jab-opti755

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

   DNS Suffix Search List. . . . . . : mei.lan



Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : mei.lan

   Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network 
Connection

   Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : xxx::xxxx:xxxx:xxxx:xxxx(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.112.125(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : Thursday, March 07, 2013 3:22:10 PM

   Lease Expires . . . . . . . . . . : Sunday, April 13, 2149 10:37:32 PM

   Default Gateway . . . . . . . . . : 192.168.112.11

   DHCP Server . . . . . . . . . . . : 192.168.112.51

   DHCPv6 IAID . . . . . . . . . . . : 251666843

   DHCPv6 Client DUID. . . . . . . . : 
00-01-00-01-18-BB-89-74-00-21-9B-32-4F-E7

   DNS Servers . . . . . . . . . . . : 192.168.112.51

   Primary WINS Server . . . . . . . : 192.168.112.50

   NetBIOS over Tcpip. . . . . . . . : Enabled



In general, my Samba file server appears to be doing everything properly for 
the file server.  Windows desktops are able to connect and browse Samba 
shares.  The same Samba configuration has been in place for more than a 
year, without a problem.  Also my DNSmasq/DNS server seems to be working for 
a while now without any problems.  As I mentioned above, I believe that 
there is something mis-configured on my network such that NetBios names are 
not being resolved or cached, so that Bacteria (BackupPC) can use them 
properly.

If there is any additional information that is needed to help pinpoint the 
problem, or identify a solution, let me know.  My knowledge of NetBios 
naming is pretty limited, so I am looking for some expert guidance to 
resolve this issue.  Please CC me directly with any responses, as I only get 
the daily digest of the mailing list.  Thanks.

Jeff Boyce
Meridian Environmental
www.meridianenv.com


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/