similar to: Help to a wet-behind-the-ears Linux newbie

On 1/6/20 7:52 PM, Leon Fauster via CentOS wrote: > Am 06.01.20 um 22:44 schrieb Robert Nichols: >> How do I let a CentOS 8 client make use of the shared printers advertised by CUPS on the network? In CentOS 6, this was just a matter in a checkbox "Show printers shared by other systems" on the CUPS Admin page. Is this function still available somehow? Manually adding all the

Newbie question. If I type nmblookup __some other machine__ I get the correct response from Samba. If I type nmblookup __mymachine__ then I get an error yhat it is not found. So if nmbd is not setup right, how do I fix it? --Dan Dan Huston Phone (602) 965-2420 Measurement, Statistics and Methodological Studies Fax (602) 965-0300 Psychology in Education

Hello, I am hoping someone can help me.... I am trying to configure my samba...and the problem is the following: When I use nmblookup with -B option and Broadcast address it is impossible to find my samba server (named prova) that is: # nmblookup -B 10.254.14.127 prova querying prova on 10.254.14.127 name_query failed to find name prova If I do the same lookin up to another machine different

hi! Sorry in advance if I am not on the right mailing-list and sorry if my question is cover somewhere is doc (I didn't find anything). The result from nmblookup (same result on all platform) for a given samba server isn't what I expect. The key part of my smb.conf is: [global] netbios name = ourserver2 netbios aliases = ourserverdev ourserverlab ourserver name

Hello. I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC. Samba can't find its hostname via nmblookup: $ nmblookup -B 192.168.1.255 frontier querying frontier on 192.168.1.255 name_query failed to find name frontier If I query Samba via unicast, it answers OK: $ nmblookup -U frontier frontier querying frontier on 192.168.1.31 192.168.1.31 frontier<00> Also,

Hi all... I need to make a few queries to WINS, but am unsure how to do so. 'nmblookup' will allow me to enter an IP address and get information about the machine name, domain, and username. I want to do the opposite...I would like to have a tool that will take a username and return the IP address. I know this information is stored in WINS somehow, and I am capable of writing some Perl

Dear List, I hope someone could give me some explanation about above error/problem I got. I have 2 machines, one installed RH7.3 (IP ADDR. =10.1.45.12, host name = fk0000-msi-srv) and the other one, Mandrake8.2. (IP ADDR. = 10.1.45.13) Both machines use Samba 2.2.3a. At the RH7.3, I got following error if I connect from Mandrake8.2. $ smbclient -U% -L 10.1.45.12 added interface ip=10.1.45.13

Hi folks, I find that nmblookup seems to be receiving responses to name queries, but ignoring them. Here's what's happening: # nmblookup somehost querying somehost on x.y.255.255 name_query failed to find name somehost But watching the transaction with ethereal on the local host, I see that: 1. nmblookup on local udp port nnnn (some random number above 1024) sends an nbns

Hi, After lots of struggle and rtfm I finally got most things running, except for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but plenty more to learn. Here's the setup in summary: system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master, wins server, domain master browser, no iptables; system bdc is the BDC on subnet 192.168.2.0,

Dear all, I loose hope to be able to obtain the NETBIOS name of a Win95 box using the following command : nmblookup -A ipaddress Some of my user are using laptops and are connecting the network by a remote lan access. The IP address is attributed by the RLA supplier. I included in the login process (telnet) of our Administrative AIX server a NETBIOS name check of the calling machine. If the

Hi All: I'm worse than a newbie at this so if this seems a bit dumb please accept my appologies. I've gone to us1.samba.org/samba/docs/DIAGNOSIS.htm and run all of the tests. My installation appears to pass all of them except for this one: nmblookup -B ABNER Yes, Abner is all in uppercase on both the windoz box and the Linux box. All of the other tests appear fine. The above

Harry, Thank you. Unfortunately we don't have the choice of upgrading LDAP due to distro not supporting the newer version. However we have managed to get it to work. A lot of fiddling around. I do have another question though ;). Now that we have LDAP replicating, how do I transfer the "samba classic " PDC role to our BDC. I have read that using the domain master=yes in smb.conf

I'm debugging my Samba setup using the "Troubleshooting Techniques" from Sam's Teach Yourself Samba in 24 Hours. Everything works fine up until the nmbd section. I am able to do the following correctly: nmblookup -U 127.0.0.1 __SAMBA__ nmblookup -U 127.0.0.1 POGO (the server) nmblookup -B 192.168.1.255 WIN-CLIENT (the client) but when I do nmblookup -B 192.168.1.255

Hi Everyone, >From windows 2K, machine I could see Samba server but I can't get its share. I tried to follow the instruction given at http://samba.planetmirror.com/samba/ftp/docs/Samba24Hc13.pdf to resolve the problem. nmblookup -U 127.0.0.1 _SAMBA_ and nmblookup -B 10.10.255.255 real-samba-server-name fails for me but nmblookup -U 127.0.0.1 real-samba-server-name

I used to be able to browse the windows shares on the network through Nautilus. I can see them as computers, but when I click on them, it fails. (I'm on Ubuntu 6 LTS, AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am

Hi, Some time ago, I wrote a small script based on some information on one of the Samba lists, which let me figure out which machine a user was logged in on. The script was this:- # smbfind: watch for someone to log in PATH=/bin:/usr/bin case $# in 0) echo 'Usage: smbfind <nt_login>' 1>&2; exit 1 esac nmblookup -S "${1}#03" | awk '/<00> - /{print

I'm trying to troubleshoot a new samba setup on a tiny network, and I'm clearly missing something. I'm running Samba 3.0.22 on Ubuntu Linux. When I first set it up, it seemed to go so smoothly. I changed all the workstations to the same workgroup (RABNETWORK) and they could see each other and the server, but they couldn't open anything on the server. I don't really understand

Hi there, i have Samba 2.2.7a running on FreeBSD-STABLE 4.7. I set up a few things and smbd and nmbd start up at boot, i can browse the net. However, nmblookup can only find IPs by SMB-names, but not SMB-names by IPs. Here is an example output of the failed lookup: %nmblookup -d 3 210.104.1.133 Initialising global parameters params.c:pm_process() - Processing configuration file

We're running an older version of Samba on an Irix machine, and just got 2.0.2 working (finally!) on our Intel/Linux box. The odd thing, is that findsmb gives different results on the two systms. On Irix it lists the NetBIOS names with OS descriptions, but on Linux it lists the IP name and no OS description. I went through it line by line and found the first difference at: ../nmblookup -r

Hi list. I'm new to this list, so please bear with me. I've got samba 2.2.8a on Solaris 9 (SPARC). I've run all the tests. testparm runs fine. Other tests: # nmblookup -B stage __SAMBA__ querying __SAMBA__ on 192.168.18.25 192.168.18.25 __SAMBA__<00> # # nmblookup -B 192.168.1.9 '*' querying * on 192.168.1.9 192.168.1.9 *<00> # # nmblookup -d 2 '*'