similar to: I can't ping NT workstation

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 =

I've seen this happen several times, and, short of rebooting the NT PDC, I can't seem to fix it. Background: We have two numbered networks in the building. We have an NT domain that has members on both numbered networks. To keep browse lists straight, I've designated Samba as the browse master on one of the networks. It's declared to be in the same workgroup as the NT primary

Hi, I have a strange problem with a domain member server. The Samba3 domain master/wins server can not lookup the host. Workstations that are trying to connect to the server appear to be having trouble finding it (network path not found). nmblookup problemserver querying problemserver on 192.168.0.255 name_query failed to find name problemserver rigel:/var/lib/samba# nmblookup otherserver

Hi all, I have samba server 2.2.8a to act as a PDC on a mixed WinXP/Win2k/WinNT network. I joined all my workstations to the domain with no problem... And users can login into the domain and access their folders/printers, BUT!!! Every now and then they cannot log in getting error message that domain controller cannot be found.... I'm trying to track the problem down :-) When I went thru

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

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

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

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 all, I'm investigating the possibility of creating a Linux-based firewall solution which can allow or reject connections based on the identity of the user currently logged into a machine, similar to what's possible with MS Proxy Server. I know that nmblookup can be used to query the logged-in user on a Win9x machine; is there a similar ready-made mechanism that can be used in an NT

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

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

Does know anybody a small, little, beatiful (and cheap) software replacement of PING utility for pingins machines with netbios name and with ip number and without DNS entry? Smbclient and nmblookup work fine, but I thinking in a utilitity like PING of windows95. This ping is capable to work in WINS (NETBIOS) and ip and name translation. The ping of linux dont work in this way. Samba work fine.

Folks, I am stumped! I have followed every tech tip I could find and I am still unable to complete my SMB installation. Specifically, I fail Test 4 and Tests 9 and 10. I believe the problem has something to do with the NMBD configuration. Below are the parameters of our system. Any help is greatly appreciated. Brandon Stauber brandon@inetevents.com 310-889-9264 [Please respond

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

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

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

Dear R-Help-Team, I would like to cluster my data using the ward-method. In several papers I read (e.g. Bahrenberg) that it is neccesary to use the "squared euclidean distance" with the ward-method. Unfortunatelly I cannot find this term in r as a method for measuring the distance. Does anybody have an idea? Thanks in advance, Carolin [[alternative HTML version deleted]]