similar to: nmbd, wins.dat reload ?

I recently reconfigured a box running FreeBSD 5.3 with Samba v. 3.0.7 running as PDC. It was servicing 2 networks, processing logons for 192.168.200.0/24 and 192.168.115.0/24. The reason for 2 networks was security, 115.0/24 had some stuff on it that the users on 200.0/24 shouldn't have access to. Before the reconfiguration, the system was working 100%. To make everything better I flattened

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

Hi, I've got a Samba domain running across two networks. One of the Samba servers has a HiPPI NIC on it, used only for point-to-point connections, and unreachable from everywhere on both networks. The problem is that for some reason, nmbd is registering the HiPPI NIC's address instead of the Ethernet (correct) address for the machine. Anyone ever seen something like this before? I'm

I couldn't really find anything about this in the archives, sorry if it's been beat to death. I've got a Debian Linux box running kernel 2.0.33. The machine has two ethernet cards and does NAT between a LAN and a cable modem link. For some reason, it's got 127.0.0.1 listed for its name: root@spruce:/var/samba>cat wins.dat "SPRUCE#20" 914324043 127.0.0.1 46R

Hello. I have problem. I dont understand root of this problem and I say facts: Have samba wins-server and many win-clients and two samba-clients. At wins-server in browse.dat exists all clients, in wins.dat once in 2-3 days records about samba-clients is not available. In smb.conf at samba-clients exist this param:"remote announce = IP_of_wins_server" In log of wins-server:

Hi, I get constantly every some secondes this entry in log.nmd [2005/06/30 15:11:22, 4] nmbd/nmbd_workgroupdb.c:dump_workgroups(284) dump_workgroups() dump workgroup on subnet 192.168.53.180: netmask= 255.255.255.0: TOPTEST(1) current master browser = AADMT00 AADMT00 400c9b0b (Backoffice Testsystem PDC) [2005/06/30 15:11:22, 4]

Looking for a solution to this problem. I have Googled all over the place but haven't found a definitive answer. I have a Samba Server that ONCE was on a network where there was SECOND Samba Server with IP Address 192.168.20.3. Today, the FIRST server is on a network with an address range 10.0.0.0/255.255.255.0 and it has no way of finding that SECOND Server 192.168.20.3. However,

In the cached wins.dat file I'm noticing that it's caching the wrong ip for a hostname. We are using WINS not dns. So we can't ping the host by name, just by ip address only. Is there a way to clear this cache? Or what else on a network could be causing this?

Hi, I have troubles understanding wins and network browsing functionnality. I have a samba server(pdc) on a different subnet than my clients. The server smb.conf has wins support = Yes, the client are configured to use the wins server. In the wins.dat, i can see all the computers. In the browse.dat i have only computers/servers that are in the same subnet. When i try to browse the network

I have been trying all day to make WINS work for me, unsuccessfully. I have a rather complex setup, that works fine over a LAN, WINS and all. However, the LAN was a substitution for the internet, and when the setup is moved to the real internet, the WINS aspect of my setup does not work. I need some information about WINS over different subnets. I have two machines both running linux +

My wins.dat seems to be rather out of date. I'm running Samba 2.2.2 as a wins server with dhcp. When the client address changes, Samba doesn't seem to update wins. The clients are Win2k & WinXP. In the manual page, it suggests that I shouldn't change the max/min ttl parameters. Can I hook dhcp to samba somehow? Rebooting the out of date clients triggered Samba to update

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

We're running samba 2.0.7 on an alphalinux machine (kernel 2.2.16, this is redhat-alpha 6.0, if that's important) and nmbd is crashing with an internal error. See the logs below (log.nmb at the bottom). I'd do some checking around on the samba mailing list archives, but they've been down for some time now. nmbd generates this message on startup. When I ran it from the shell

Hello, does the latest versions of samba 3.x use wins.dat or wins.tdb ? Is documenation available about what the various values in the wins.dat ? Thanks Andreas

My network looks like this: internet 192.168.0.0/24 router ----+----+----+----- internal 192.168.5.0/24 | | | router ----+-----+------+- LNB--->mswin | | (also a | | | client | | samba | | .... | | server) | | samba | | samba

My network looks like this: internet 192.168.0.0/24 router ----+----+----+----- internal 192.168.5.0/24 | | | router ----+-----+------+- LNB--->mswin | | (also a | | | client | | samba | | .... | | server) | | samba | | samba

I've recently setup an iSCSI portal on my network and have taken some servers offline. However, due to the requirements of certain software programs I need to use UNC paths. I was able to fix this issue by adding CNAME into my DNS. I'm still finding that certain programs still require to view the browse list to find the appropriate server. Since CNAME doesn't link to the

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

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:

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