similar to: Setting up Samba with broadcast based name resolution (not WINS)++++++++++++++++++++

Hi, I've got a strange problem with address resolution in a mixed Network with Samba on Linux as Server and Win2k / XP clients. At first my setup: - SuSE Linux 8.1 - Samba Version 2.2.5-SuSE on SuSE 8.1 (smd.conf attached) - nmbd is configured to act as a WINS server. - DHCP is installed (dhcpd.conf attached) - No DNS is installed Everything worked fine until a temporary Server-Down-Time,

Hi, I have been searching around and trying for a few days but still can''t get it works. Hopefully the highhand here can give me hints!! I have 3 adsl connections, 1 is using hardware broadband router to connect and the other 2 are using my debian linux pc to connect. I hope to setup a route policy so that all users except user1 and user2 will use the broadband router connect (eth0),

I've set up my Samba PDC to act as a WINS server, because I need remote access to it (through a VPN connection). I put "wins support = Yes" into the smb.conf file. As far as I know, WINS doesn't use a unique port number, so enabling the usual NetBIOS ports (137/udp, 138/udp, 139/tcp) on the firewall should be enough to make WINS work. I did this already. I tried to connect to a

Hi everyone, I'm trying to set up a Windows XP Pro client to connect to a Samba server (version 2.2.8) on a Redhat 8.0 linux box, but have been having trouble for the past 3 days. I have gone through Troubleshooting Samba at [http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf] but I can't figure out how to fix the problem. I suspect that the broadcast address may not be the same on both

I am currently trying to use WINS exclusively to resolve host names for our desktops. Somebody 'architected' a desktop host naming convention that works for NetBIOS names but is not supported by our DNS configurations. There are too many desktops to put in a hosts file and the only data structure that has both the IP and host names is WINS. However, it appears that WINS still

Hi there. This is with regards to samba-3.0.23c, on FreeBSD 6.0-RELEASE-p12 Previously I had Samba up and running without any problems. Then I decided to do a tiny upgrade by simply switching to a new motherboard, while keeping all other hardware and software aspects the same. However, after the upgrade, netbios name resolution seems to have stopped working somehow. \\servername lookups no

I wonder how to configure the name resolution on the Windows network. I am puzzled by the "Wins Support" section of the smb.conf man page: " You should not set this to yes unless you have a multi-subnetted network and you wish a particular nmbd to be your WINS server " Does that mean that on my subnet, broadcast is as performant as direct acces to the Name Server, even if

Hello I happen to have two network interfaces on my new, up-to-date, CentOS 6.2, named eth0 and virbr0 (3 of them if I include the lo interface). However the system APIs like getaddrinfo() only return the address for the virbr0 interface (which was created by the CentOS installation), when I would like to have them both. Even if I give the configured eth0 address explicitly to getnameinfo(),

I do get problems with name resolution accross subnet bounderies. I have a working and wins server and to demonstrate the problem I paste the debug output of mount /smbhome/ opts: uid=1000 opts: gid=1000 mount.smbfs started (version 2.2.2debian-2) added interface ip=192.168.6.2 bcast=192.168.6.255 nmask=255.255.255.0 resolve_lmhosts: Attempting lmhosts lookup for name Tri-st-s001<0x20>

Hi all, Can someone explain exactly how Windows does naming resolution ? Here's my setup and my problem ... Windows 95 / Solaris 7 network with Samba 1.9.18 Windows PC with local IP and DNS servers defined and WINS turned off. I have NetBIOS using DNS for name resolution. I have a samba server X which about 50 PC's in our dept use. I want to move the services to machine Y so that I

> Maybe there isn't a glibc version (although > it shouldn't be hard to port the Solaris version to >glibc). I will try to port nss_wins to glibc. I made some changes to smb.conf and follow the tests described in Samba diagnosis (www.samba.org/samba/docs/diagnosis.html) smb.conf [global] workgroup = NETMANAGER server string = Deltacom Samba Server printcap name =

I have a samba domain with a Samba 3.4.x PDC (compiled from source on Solaris 10) and two Samba 3.0.x BDC's (Sun-bundled Samba on Solaris 10.) XP clients use DHCP. When on the LAN, DHCP includes WINS server (the WINS server is one of the Samba 3.0.x machines.) We also have a VPN for remote client access for Windows XP machines. XP machines could include home PC's (not in the domain)

I am using Samba release 3.0.7-2 on a Fedora Core 2 box. I am unable to receive proper name resolution for a machine because my client seems to be requesting resolution for the machine by its workstation service aliased name rather than its file server registered name. Here are the machines registered names: NetBIOS Remote Machine Name Table Name Type

I know this is an older version, but we're currently working on a project that has encountered some broadcast storms and fingers have begun to point to samba. I don't believe this is the case, but I find my knowledge of the resolution mechanism for nmbd to be sorely lacking. I know later versions than ours (1.9.16p11) included a "name resolution" parameter in smb.conf, but I

I have built from sources Samba4 4.4.4 version operation at Ubuntu 14.04 x64. There are three daemons are started: nmbd, smbd, winbindd. I excluded 'dns' from /etc/nsswitch.conf, 'host' line and added 'wins' . When I try ping some of Lan host by NetBios, I get ping: unknown host xxxxxx. So, how is to make possible to ping host at Ubuntu 14.04 by NetBios name which can be

Smbclient worked fluently to create tar compatible backups of all files on an SMB/CIFS share. For which I used an Ubuntu 8.04 LTS Server Edition configuration with LAMP, OpenSSH, Samba and BackupPC packages installed. Testing with smbclient \\\\win-pc\\share -U administrator -d 3 (debugging level 3) returns: (...) name_resolve_bcast: Attempting broadcast lookup for name win-pc Got a positive

I am hoping someone can help here. I noticed a really odd issue. WINS resolution doesn't seem to work between my PDC and BDC, both Samba 3.0.14a boxes running on Debian. I have nsswitch.conf configured properly, I think. Here are the nsswitch.conf settings. PDC: hosts: files dns wins BDC: hosts: files dns wins On the BDC, I have the parameter wins server = 192.168.0.2, the address

Hi, all. I've always assumed that there's a way to do transparent WINS-based hostname resolution, but I'm durned if I can figure out how. In other words, I imagine that you could just add another entry to /etc/resolv.conf (eg., "hosts: files dns wins") that would allow me to ping foo and have it attempt to resolve through each in turn. Does this exist, and I've just

Le 06/03/2011 00:14, "Hung-Sheng Tsao (Lao Tsao ??) Ph. D." a ?crit : > question to solaris forum > http://forums.oracle.com/forums/search.jspa?objID=c300&q=Solaris Since you have been (and you alone) kind enough to try and help me, I will give you in writing a detailed explanation on how this mess came to be : however, as I explained, I have only known the Solaris OS, or

Folks, We have a setup where each mobile node connects with 1 or more tinc instances (over different links) to a central node. tinc is running in switch mode. The link is chosen by setting the IP address on the active link's interface, and the central node sees this after the first packet on the link, and moves the MAC address to a different 'ethernet port' (link). This works really