similar to: Samba 2.0.7 Network Neighborhood problem

I am running Red Hat 7.3 and samba 2.2.3a I can see the samba server in network neighborhood however when I try to connect I receive the following error: \\Puddles is not accessible A network error has occurred. You might not have access to some network resources my smb.conf file is as follows: [global] workgroup = POND encrypt passwords = yes security = SHARE [homes] guest OK =

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

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

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

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 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, 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've got Samba 2.2.2 installed and running fine on one of our servers (RS/6000 AIX 4.3.3 and using NT authentication), however, when I do Test #4 (from docs/textdocs/DIAGNOSIS.txt) it looks like this: npssrv{root}#nmblookup -B npssrv _SAMBA_ querying _SAMBA_ on 173.148.200.113 name_query failed to find name _SAMBA_ The test said I should get back the IP address of our samba server. I got

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

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

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

Hi, I do not know whether this is a samba problem or an NT feature, but it seems only to occur with samba boxes, so it could be samba's fault: The NT PDC (moritz) runs also the WINS server. It regularly forgets the IP addresses of our samba servers: # nmblookup -U moritz -R hni-gate querying hni-gate on 131.234.166.19 name_query failed to find name hni-gate I then just have to stop and

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

dear Sir, i am running red hat 6.2 on one machine and windows 95 on another but i am unable to see the linux machine in my windows pcs network neighborhood.to check my samba server i tried the tests given in DIAGNOSIS.txt.I am able to run tests 1 to 4 without error but in test 5 which says ::: "test 5 : run the command "nmblookup -B ACLIENT '*'" You Should Get The

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

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

Hello! Here is request to 2.2.8a: [dm@dm-amd64 /]$ nmblookup -R -U 192.168.6.10 center querying center on 192.168.6.10 192.168.22.224 center<00> And here is to 3.0.2a: [dm@dm-amd64 /]$ nmblookup -R -U 192.168.22.220 center querying center on 192.168.22.220 name_query failed to find name center Certanly, all is OK in DNS, I have in smb.conf dns proxy = yes Today I upgraded 2.2.8a

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