similar to: Can nmbd re-register itself with a WINS server?

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

Dear all, I'm setting up a wins server configuration with Samba 3.0.24 ### interfaces = 127.0.0.0/8, 192.168.1.0/24 bind interfaces only = Yes name resolve order = lmhosts host bcast preferred master = Yes dns proxy = No wins support = Yes ### Before setting dhcp to instruct the clients to use this wins server, I'm trying to make certain it's working correctly. The command:

I have the following PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 PDC is configured to be the WINS server for everything, including XP Pro clients and other Samba machines. PDC# testparm -v | grep master Load smb config files from /etc/sfw/smb.conf ... Server role: ROLE_DOMAIN_PDC ... Press enter to see a dump of your service definitions preferred

Hello together! I have an problem with the wins server, based on a Gentoo distribution with Samba 3.0.24. The problem is following: After an restart of samba everything works fine, but after an undefined time period its not possible to make an nmblookup for some other computers. The samba server is also configured as wins server. an cut from the smb.conf: ...... domain master = Yes

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

Hi, Problem: When our network has any glitches causing a network time-out for more than a few minutes, our samba servers lose their connectivity with our WINS server even after the network is restored. This causes the WINS server to tombstone the name registration for the samba server(s), thereby causing clients to not connect through the browser. SMB connections are not affected so the

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

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

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

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

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

Hi all, We have a weird problem, Samba is providing an outdated IP address for a client (XP Pro) machine. This means that the client machine is not contactable by the other machines on the network. The IP is that which was previously used when connecting via the company VPN, although the machine has/is now plugged onto the company network and had has new IP via DHCP. This problem continues

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

Hello everybody! Still struggeling with my latest Samba setup, I've just run accross another problem which I can't figure out on my own. Samba is supposed to act as a WINS server (among other things) on a multihomed machine. (The Samba version is 3.5.1 as part of Debian Squeeze) Here's the [global] part of the samba setup: ----------------------------------- 8<

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

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