We own an old CNC milling machine with a NUM control unit. It's connected to a Windows NT PC over Ethernet, they communicate via NetBIOS Frames . We now want to modernise the PC and can run the control software on modern Windows systems, but NBF is only supported up to Windows 7. We've been thinking to use a small linux system (e.g. a Raspberry) to "translate" the NetBIOS Frames to TCP/IP encapsulated packets to make sure the NUM controller can talk to more modern systems. As we'll likely only need the name- and datagram services, we should be fine with UDP packets and without session handling. Alternatively we could run the name server and fileserver on the linux machine and make sure to sync the files another way. Is it possible to do what we're looking for on linux and if so how?

My friend has a PC that uses Windows, and I want to know the name of that computer. All I know now is that his IP address is 10.0.0.2, how can I get his computer's name from my Linux box?

I'm experiencing problems configuring samba on my Fedora machines. Everything has always worked great on CentOS but identical configurations are having problems with Fedora. I have three computers on the same network, lets call them: A, M, and L. All computers have identical [global] entries in their smb.conf. 'A' is running CentOS 7, has no problems, and can see all hosts and shares for A, M, and L according to smbtree. Both 'M' and 'L' are running Fedora 30 but cannot resolve any NETBIOS names (I can't ping the other machines by hostname), and see nothing on smbtree, not even its own shares. Interestingly, there is also a Windows machine on the network. Lets call this machine 'W'. All of the Linux systems can resolve this machine by its hostname and ping it. The problem is with the Linux machines talking with each other. smb.conf (all machines): [global] workgroup = WORKGROUP security = user passdb backend = tdbsam printing = cups printcap name = cups load printers = yes cups options = raw hosts allow = 127. 10.0.1. ntlm auth = yes Firewall open services (all machines): samba ntp dhcpv6-client ssh samba-client Note that the Fedora machines also allow the mdns through the firewall. That's it. It should be simple but it's not working. What's going on?

There's a Windows machine called SUSAN on my network. From a Windows VM on my Linux box I can simply: C:\>ping susan I've followed this guide (and looked at several other similar ones) for resolving NETBIOS names from my Linux box itself. I installed samba and samba-winbind. I edited this hosts line in /etc/nsswitch.conf from: hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname to hosts: files wins mdns4_minimal [NOTFOUND=return] dns myhostname Apparently I should now be able to ping SUSAN by her name (I can already ping her by her IP). But I'm getting: user@localhost:~ $ ping susan ping: unknown host susan

Assuming a Linux system has both hostname (/etc/hostname) and NetBIOS (/etc/samba/smb.config) enabled. My questions are: 1. Are these 2 names synchronized somehow by default settings? (for example, after installing the samba, does the netbios name = something setting get changed in (/etc/samba/smb.config) to the same value of hostname (/etc/hostname)?) 2. When the Linux system is pinged by its name, Would it be looked up by the name in its /etc/hostname or /etc/samba/smb.config?

So I have a Ubuntu 14.04 server that I'm trying to get to run as a Domain Controller for a set of Windows machines. I've set up a Bind9 DNS and it works fine, pinging the nameserver gives the correct IP: 192.168.0.3. However pinging the Netbios name gives 192.168.0.255 which is wrong, I saw a similar problem on the Unix and Linux stack exchange which said to run nmblookup -U 192.168.0.3 -R 'NETBIOS_NAME' This gives: 192.168.0.255 Arc 192.168.0.3 Arc 192.168.1.1 Arc The last two records are correct, but the first... I don't even know why or how that got there. I have no idea where that record is, my only WINS server is samba, but even if I set: wins support = no That entry (.255) doesn't go away.

I have a Debian:stretch installed in my Docker container. I want use smbclient with my shared dir. Dir is shared on a host (Windows 10 x64). I created a user and permitted the access to that dir like this: I try to connect like this: root@0b54a022bb9e:/# smbclient -L //10.0.75.1 -U=dockeruser WARNING: The "syslog" option is deprecated Enter dockeruser's password: Domain=[DESKTOP-SNC8BC2] OS=[Windows 10 Enterprise 17134] Server=[Windows 10 Enterprise 6.3] Sharename Type Comment --------- ---- ------- ADMIN$ Disk Удаленный Admin C$ Disk Стандартный общий ресурс D$ Disk Стандартный общий ресурс E$ Disk Стандартный общий ресурс F Disk F$ Disk Стандартный общий ресурс G$ Disk Стандартный общий ресурс H$ Disk Стандартный общий ресурс hlds Disk IPC$ IPC Удаленный IPC Connection to 10.0.75.1 failed (Error NT_STATUS_IO_TIMEOUT) NetBIOS over TCP disabled -- no workgroup available I guess the issue is in the NetBIOS setup on my host. I set it in my adapter's WINS settings but still I see that my NetBIOS over TCP is enabled when I check it using ipconfig /all. So the questions are: 1. Can I smbclient-ing without NetBIOS use? 2. If not then how should I turn it on my host?

I just installed debian and samba my debian computer name is "debian" but after installing samba it is showing like this(in windows network places) "Samba 4.1.17-Debian(Debian)" How can I edit/change this description "Samba 4.1.17-Debian" ?

Immediately after installing Debian 9 Stretch, the avahi-daemon has already been installed, so it is working to send a ping between Linux with avahi-daemon installed on each of them. For example, when there is a named 'alice', $ ping alice.local returns a normal response. I want to do the following things: - I want to resolve names of Windows from Linux, but I do not want to install the Bonjour or something like that on Windows. - I want to resolve names with NetBIOS (WINS) instead of mDNS. - I do not want to add a suffix such as .local in the name. So I deleted avahi-daemon and installed winbind. # dpkg --purge avahi-daemon libnss-mdns # apt-get install winbind libnss-winbind And, added setting to use 'wins' in /etc/nsswitch.conf. e.g. hosts: files dns wins With the above setting, $ ping mywindows will not respond. However, $ nmblookup mywindows can successfully get the IP address. Previously, when I was using Debian 8 Jessie, it should have been successful, but using Debian 9 Stretch will not be my expectation. Is there something missing?

Through StackExchange, we know how to configure Linux to resolve NetBIOS names with older versions of Samba, and I have configured my system in those ways. (I have installed winbind , configured my /etc/nsswitch.conf correctly and confirmed my changes , including disabling the NSCD on OpenSUSE Tumbleweed.) But now, with Samba 4.4 and later, the Samba developers have opted to require winbind to be running for WINS resolution since they have changed the execution path for WINS queries. If I include either of wins and winbind in my /etc/nsswitch.conf file, my name resolution fails without the winbind dæmon running, like the Samba page implies will happen. But, even running the winbind service, my name queries that would succeed previously (with earlier versions of Samba) are failing, though nmblookup returns successfully. How do I need to configure my client system such that host queries can resolve NetBIOS names with Samba 4.4 and greater? In end-result terms, running Samba 4.4 or later in Linux, how can I ping a Windows machine by its name without DNS? To clarify: I have a setup working in Samba 4.2. If I upgrade to Samba 4.4, 4.5, or 4.6, maintaining the same settings, name resolution stops working. If I then downgrade back to Samba 4.2, name resolution works again. Other than ensuring the running of the winbind dæmon, what else do I need to do differently with these new versions of Samba?

For the past day, I have been trying unsuccessfully to let my Ubuntu VM be able to resolve NetBIOS names on the local network, to find some non-computer devices (Printers, special barcode machines, etc..) that don't have a fixed IP. At first, I assumed I am failing to configure the usage of winbind/wins for resolving, even though I had read every webpage that ever mentioned nsswitch.conf, and I was sure my configuration should be correct. running nmblookup printername returns a successful result that looks like: x.x.x.x printername And this was my first clue, the service type. I fired up wireshark, and tried to ping printername, and I saw a NetBIOS broadcast asking for printername, to which no one replied. I stopped the winbindd service, and run it manually in foreground using: sudo winbindd -F -S -d 10 then tried the same ping, and I saw winbindd attempting the same erroneous query with instead of . Why is this happening? Where can this be configured? EDIT: Closing this question as this is hardcoded in the source. Digging through the code, I found the function in winbindd_wins_byname.c, harcoded as such: `subreq = resolve_wins_send(state, ev, state->request->data.winsreq, 0x20);`

I am trying to set up local hostname resolution on my Fedora machine. I have installed

-winbind samba-winbind-clients pam_krb5

and then went through the procedure shown on: https://www.server-world.info/en/note?os=Fedora_25&p=samba&f=3 I have added wins to my

/etc/nsswitch.conf

as follows:

:      files mdns4_minimal [NOTFOUND=return] dns myhostname wins

I then try to use wins to find my raspberry-pi which I can find on my Ubuntu install. If I add wins before myhostname I get:

$ ping my-pi
Segmentation fault

When it is as shown above I get:

$ ping my-pi
ping: my-pi: System error

Any pointers on how to diagnose/solve this issue would be much appreciated.

This is a equivalent question asked here for OSX. What is the easiest way to find out a NetBIOS name of a WIndows PC in my LAN by MAC address and vice versa? It can be done by IP with: nmblookup -A a.b.c.d nmblookup pc_netbios_name Is there a similar command for MAC address?

There is a mashine called "BIE" visible in my network surrounding of my dolphin File manager (Ubuntu 14.10). I cannot access that device in dolphin and also don't get an answer pinging it. How can I find out the IP of that device to do an intense scan with nmap?