similar to: Samba fails diagnosis.txt test #5 nmblookup

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 am unable to find my Windows XP share (winpro) in Linneighborhood which runs on my desktop Kubuntu Linux box. When I try to mount that Windows XP share I get the error message: 2139: session request to WINPRO failed (Not listening on called name) 2139: session request to *SMBSERVER failed (Not listening on called name) SMB connection failed smbmt: Error: winpro _not_ mounted. The command line

Am using Kubuntu 6.06 to connect to a Windows XP Professional machine, both behind a natted router. The XP machine was installed from a new service pack 2 cdrom. I try to connect from kinda to winpro with a script run as root with the line: smbmount //winpro/c /mnt/winpro -o guest,uid=lba,gid=users This used to connect reliably but something happened :-( I also have a public share on the

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

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,

For some reason I can mount my XP Home machine but not my XP Professional. The mount seems to go ok until I enter the password then fails with: 17184: session request ok Password: 17184: session setup ok 17184: tree connect failed: ERRDOS - ERRnosuchshare (You specified an invalid share name) SMB connection failed The command smbmount //winpro/lba /mnt/winpro -o guest,uid=lba works from 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

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

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

I'm trying to use nmblookup to find the IP address of a Windows machine called "MARKETKA" (only with an accent over the 'E'). If I do a reverse lookup on the IP address, with debugging enabled, I can see that the hex code for the accented 'E' character is 0x90: $ nmblookup -d 4 -A 192.168.1.15 | grep MARK answers 0 char .MARK.TKA hex

$ nmblookup ohwow querying ohwow on 129.22.171.31 name_query failed to find name ohwow $ nmblookup -s /etc/samba/smb.conf ohwow querying ohwow on 129.22.171.31 name_query failed to find name ohwow $ cat /etc/samba/smb.conf [global] workgroup = scholars netbios name = fedora security = user wins server = 129.22.4.11 wins support = no name resolve order = wins lmhosts dns my problem is that

Howdy! I''m a newbie to Xen and SUSE. I''m running OpenSUSE 10.3 on an Intel Centrino Duo with virtualization enabled in the BIOS. When I use vm-install to install an image, select "other operating system" and full virtualization and attempt to run an install with an ISO of OpenBSD or Debian Gutsy Gibbon, I''m getting a kernel panic (with OpenBSD) and a hang

Dear Ladies and Gentlemens, i have a problem, the nmblookup command have an error, but the smbclient command have no error. See example. Can you please help me. rzs12:/opt/samba/bin># ./nmblookup -d 10 pc8686 Initialising global parameters params.c:pm_process() - Processing configuration file "/opt/samba/lib/smb.conf" Processing section "[global]" doing parameter workgroup

Hello list, The issue is as the topic says, following are details: the Samba server running as ADS member, NBT enabled on Windows machines, no WINS. Windows machines can find each other by 'nbtstat -a' but cannot find the Samba server. The Samba server can't find neither Windows machines nor itself by 'nmblookup -a <netbios-name>', error message is "could not open

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

I installed samba4wins on two of my Fedora Core 3 servers (from src rpm), on one PDC (samba 3.0.21c) and on one standalone server without samba, in order to test samba4wins. I think I managed to install and to setup properly the software but it seems nmblookup is not working on the PDC samba: [user]$ nmblookup '*' querying * on 192.168.19.255 name_query failed to find name *

The latest version of R did not make it in the recently released Ubuntu Gutsy Gibbon. As the title says, packages for version 2.6.0 of R are currently making their way to the CRAN mirrors. From the head of the README file: ===== R packages for Ubuntu on i386 are available. The plans are to support at least the latest two Ubuntu releases and the latest LTS release. As of October 2007, these

Everything else works, but "nmblookup -B ACLIENT '*'". It shows the servers IP address, unless "ACLIENT" can be resolved thru hosts/dns. Can someone explain me why? Samba 2.0.5b on Linux 2.0.36 name resolve order = lmhosts host wins bcast dns proxy = No wins proxy = No wins server = mywinsserver.mydomain wins support = No

Need Help with this one ASAP! When I issue smbstatus I get the following error: doing parameter max log size = 50 Processing section "[mytest]" doing parameter browseable = yes doing parameter read only = no doing parameter path = / Processing section "[homes]" doing parameter browseable = yes doing parameter guest ok = no doing parameter read only = no doing parameter create