similar to: setup question

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,

Hi All, I am trying to set up samba simply as a standalone Primary Domain Controller, but unfortunatley - for the last three days at least, it just does not want to play! i cannot find a problem in my smb.conf file and to proove that it works, i can log into the samba server via the linux command line with smbclient. The problem is the windows machines, when to go to log into the domain, i get

In article <983130226.25873@phzzzt.atww.org> you wrote: : 1) With regards to the recent buffer-overflow exploit and the : recommendation of running icecast as a non-root user, how exactly does : one do that? I do it via "su". I use a pseudo user named "ice" and have this in a shell program that starts icecast: exec su --login -c

I'm configuring Samba on a Red Hat Linux 7.2 server, for access from a Windows 2000 client. My server name is DEMENTIA, and it's IP address is 192.168.0.5. I've confirmed with ifconfig that the server's broadcast address is 192.168.0.255. I'm having a problem with NMB that I seem to have isolated to the following symptoms - After starting NMBD, I can lookup the server name

I use samba 2.0.5 on a Solaris 7 Ultra 10 to provide UNIX disk mounts and backups to UNIX tape drives. But I have this new XP and I can't get smbclient to connect to it, although the XP is using all the samba shares R/W. All I get is: /usr/local/samba/bin/smbclient //paulxp/"My Documents" passwd -Tc mydocumentsxp.tar Added interface ip=161.217.10.13 bcast=161.217.10.255

I have literally beat my brains out trying to get my XP machine to talk to my samba server on my linux machine. MY PROBLEM: The samba server (version 2.2.7a) is running on Redhat Linux 9.0. I can successfully connect to the XP machine and copy files from the XP machine to my Linux machine. But I cannot access my linux box from my XP machine (The samba server shows up in the browse list on

I have FC1 + samba 3.0.1. From Nautilus I can't browse into smb:/// to view any available domain/workgroup. But I can go directly to any computer with smb:///conputer-name. When I tried to call 'nmblookup -M -- -' I get: querying __MSBROWSE__ on 192.168.0.255 name_query failed to find name __MSBROWSE__ #01 Does anyone know what's wrong? PS. Initially I had Samba 3.0.0 and

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

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

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,

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 all ! I have a PDC and a BDC in 2 differents subnets. I would like to sync their browse list but it doesn't seem to work. Actually here are a part my smb.conf files : PDC ------------------------------ ... remote browse sync = 10.10.20.10 remote announce = 10.10.20.10 security = user encrypt passwords = true domain logons = Yes os level = 70 preferred master = yes domain master = yes

I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup <clientname> This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road

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, 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

Hi, While going through DIAGNOSIS.txt on my samba 2.2.2 server, I came across the following test results: Test 5: [root@NetServer samba]# nmblookup -B resaddr8.research.bio2.edu '*' querying * on 209.64.53.8 name_query failed to find name * This appears to be a partial failure? Test 6: Initially, I got: [root@NetServer samba]# nmblookup -d 2 '*' added interface

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

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

Hi I am trying to stablish a relation between two different Samba domains. Each domain has two PDCs, all they are WINS servers, and the two domains are in different subnets. They are configured to use LDAP as the user/group/machine database. First, I will create the relation, being DOM1.CORP the trusted domain, and DOM2.CORP the trusting domain, so in a server of DOM1.CORP, I create a user this

I have setup my Samba server as a WINS server using the wins support = yes parameter. My remote network can see the Samba server at our head office fine. I have also setup the WINS setting on my PC (W2K Pro box) to point to the IP address of my Samba server. When I do a nmblookup -R -U <IP address of WINS server> <name of my PC> on my Samba server I get this reponse; querying pc1