similar to: nmbd socket read errors

Hi, I would be very grateful if anyone could give me a bit of help with this. I am trying to run Samba 3.0.5, as distributed with Mac OS X server 10.3.8, on an Apple Xserve. Things were working beautifully until I had problems with an IP address change and had to reinstall everything. At present, the situation seems to be that the smb protocol is operating, since I can make an smb

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello: My name is Ruben and I am from Elche (Spain) We are trying to setup a Samba server in our network. Our server is Suse Linux 7.3 Professional, with this version of samba: at:/ # smbd -V Version 2.2.1a at:/ # nmbd -V Version 2.2.1a I think that smbd is running OK becouse we can access to the server using its IP from the outside. But Server

Hi everyone , Recently upgraded to 2.2.5 on RH73 and suddenly my Roaming profiles did stop working and on top of this my NMBD is giving me constant errors!!!! when i try nmblookup -U 127.0.0.1 _SAMBA_ name_query fail to find name _Samba_ then i have tried : nmblookup -B 192.168.123.1 MYSERVER and then : nmblookup -U 127.0.0.1 MYSERVER 192.168.123.1 MYSERVER<00> looks fine after this i

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

My client Windows XP boxes are failing to register with my WINS server (running nmbd from Samba). I'm puzzled how to figure out what I'm doing wrong. Background: I'm setting up BackupPC to back up my Windows clients using rsync. I've installed cwRsync to the clients. BackupPC uses nmblookup to find the client's IP address given its Windows NETBIOS name. I'm

> My PDC Samba nmbd is intermittently delaying responses to > name queries. As > an example, i run: > > nmblookup -U 192.168.75.11 -R "PDC#1C" > > from a member server, and the .11 machine will respond. > Repeat this a few > times, and the .11 machine stops reponding. After a while > (and you keep > trying, add "-d 10" to the

I've been working on this for about a week now and can't seem to figure out the magic configuration that will make my Samba server work. I've gone through all the tests in DIAGNOSIS.txt. I'm running Sambe 2.2.6 on Redhat 8 and trying to get it to work on a home network with two Win XP machines. smbclient works both to the local Samba server and to any of the XP boxes.

the original message looks like it was corrupted when it got to the list, so here's another try ... -----Original Message----- From: Tim Wolters Sent: Sun 11/10/2002 10:55 AM To: samba@lists.samba.org Cc: Subject: nmbd help please I've been working on this for about a week now and can't seem to figure out the magic configuration that will make my Samba server work.

Hi folks, I had some trouble running Samba 2.0.7 on my SuSE Linux 6.2. Configuration and installation worked fine, but after starting up smbd and nmbd as daemons I found a message about an internal error in log.nmb that the process received signal 11 (SIGSEGV). Here it is [2000/08/15 14:59:31, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(356) become_domain_master_browser_wins:

I am running the diagnostics to figure out why my client machine can't talk to the samba server, here's what I was able to find out. I went through the Hour 13 Troubleshooting from the samba.org web site (http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf) and I got all the way up to section where you test nmbd, and found the following problem: [root@server samba]# nmblookup -B

Hi, I've a got kind of weird problem using nmbd. At least, I think is is weird because this problem isn't dealt with in any documentation. I got my nmbd up and running, when I issue the command 'nmblookup -U 10.0.0.1 __SAMBA__' (my IP is 10.0.0.1/255.0.0.0) I get a correct response: 'querying __SAMBA__ on 10.0.0.1 10.0.0.1 __SAMBA__<00>' But when I use a

I am trying to get Samba 3.4.0 (on an Ubuntu 9.10 box) set up as a file server for my home. The router is 10.1.10.1; the Ubuntu box ("chronicles") is 10.1.10.2; the OS X box I'm using for testing purposes ("job") is 10.1.10.3. From job, I can see ports 139 and 445 on chronicles are open. Neither box has 'chronicles' or 'job' listed in its /etc/hosts file.

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

Hello. I just recently upgraded to redhat 9 from 7 & everything went smoothly except samba. Using the DIAGNOSIS.txt I get to step 3 (I think) & execute the following command nmblookup -B servername _SAMBA_ the return is thus querying _SAMBA_ on 127.0.0.1 name_query failed to find name _SAMBA_ the text advises that nmbd is not installed correctly. Well I'm using xinetd

Hi guys, I realy need your help. It looks like SMBD doesn't want to talk with NMBD, but why? When I run the command: nmblookup torpc8 The result is: querying torpc8 on 10.5.255.255 Got a positive name query response from 10.5.2.27 ( 10.5.2.27 ) 10.5.2.27 torpc8<00> That is correct. When I run the command: smbclient -NL torpc8 The result is: resolve_wins: Attempting wins lookup for

Helo , System : redhat 8 DS: netcape 4.16 Samba version : RC1. I am upgrading from samba3b3. Everything ( except changing passwd for user xp pro PC and I try to use rc1 to resolve ) seems ok in beta 3. On rc1 I Can't connect For a few second I can do : nmblookup -S l1serv2 added interface ip=172.29.160.100 bcast=172.29.167.255 nmask=255.255.248.0 querying l1serv2 on 172.29.167.255 Got

We can only process 1 packet at one time during sendmsg(). This often lead bad cache utilization under heavy load. So this patch tries to do some batching during rx before submitting them to host network stack. This is done through accepting MSG_MORE as a hint from sendmsg() caller, if it was set, batch the packet temporarily in a linked list and submit them all once MSG_MORE were cleared. Tests

I need to know if I can somehow tell nmbd which IP address on a multiple-ip interface to report - It is picking the wrong one! Details: -------- smb.conf is currently set up to bind to all interfaces in the machine. vrm378-02 ~ # ip addr show dev br0 216: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:1e:0b:65:c8:65 brd ff:ff:ff:ff:ff:ff inet

Hi, We are running samba 2.0.0 on solaris 2.6. We have security = domain and server = localNTbox. When nmbd starts up it registers itself with the localNTbox, which is a WINS server. After a period of time other WINS servers in our network synchronize and all machines on the network can access the samba server. After 24 days the WINS server tombstones the samba server entry - presumably

Hi I?ve been seeing this issue since we updated from Samba 2.X to 3.Y, and I wanted to know if anyone has seen this: I have a samba PDC mantaining a domain composed of WinXP, Win200 and win98 machines with shared folders and user authentication (smbpasswd). It works fine for hours but then everybody stops being able to logon. When anyone tries to login in a WinXP machine, it only replies