similar to: Samba 3, Windows 2000 and DNS.

Believe me, I have tried everytbing I can think of to solve this problem. I will work my tail off to resolve this but I am fresh out of ideas. Any suggestions would be GREATLY appreciated. Here are the details... problem: server can see machines/shares on clients but clients cannot see machines/shares on server workgroup/domain: golgerth no router server: rpms: kernel 2.4.18.19.8.0

HELLO ! I HAVE SOME STRANGE PROBLEMS AND I NEED HELP. I DIDN'T FIND SIMILAR PROBLEMS IN THE MAILING LIST, SO POSSIBLY I HAVE OVERLOOKED SOMETHING VERY SIMPLE. WHAT I USE *********** SOLARIS 8; SAMBA 2.2.2 (DEFAULT COMPILATION AND INSTALLATION) WIN-BOXES: WIN2K (NATIVE INSTALLATION AND SOME WITH SP2); WINNT4; ALL MS-BOXES POINT TO THE SAMBA SERVER AS A WINS SERVER TWO WORKGROUPS IN

Hi! I so far succeeded in setting up a Samba NT4 DC with OpenLDAP backend. Unfortunately I get the following error message connecting a Windows XP client to the domain (translated from german): [...] The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.lohrmann.de [...] This is surely due to a

PROBLEM: Cross-subnet browsing is not working. Browse lists on all machines contain only the machines on the local subnet. SUMMARY OF ANALYSIS: The Local Master Browser (LMB) running Windows XP (ZAYIN) never contacts the Domain Master Browser (DMB) running Samba (BETH) to initiate a synchronization of browse lists.

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,

Greetings, I am running samba 2.2.5 win RedHat 8.0 Linux machine Windows 2000 machine has fixed IP 192.168.0.40 Windows XP machine has fixed IP 192.168.0.30 Linux machine has fixed IP 192.168.0.1 on eth0 (local network NIC) and dynamic IP on eth1 (NIC connected to ADSL modem). I can ping 192.168.0.1 ( linux machine) from all machines I can ping 192.168.0.40 ( windows 2000 machine) from all

Hi everyone, I'm trying to set up a Windows XP Pro client to connect to a Samba server (version 2.2.8) on a Redhat 8.0 linux box, but have been having trouble for the past 3 days. I have gone through Troubleshooting Samba at [http://us1.samba.org/samba/ftp/docs/Samba24Hc13.pdf] but I can't figure out how to fix the problem. I suspect that the broadcast address may not be the same on both

I use Samba 3.14.17 and later test Samba 3.6.9. The computer is WINs server on Samba. wins support = yes All work good. But now I see that NetBIOS clients cannot to re-register their names on WINs, when he change IP. >From WinXP SP3 I do nbtstat -RR Answer: NetBIOS-names registered by this computer were changed. >From server: relay2# nmblookup -U 10.0.0.1 -R -S aiy querying aiy on

Hi there. This is with regards to samba-3.0.23c, on FreeBSD 6.0-RELEASE-p12 Previously I had Samba up and running without any problems. Then I decided to do a tiny upgrade by simply switching to a new motherboard, while keeping all other hardware and software aspects the same. However, after the upgrade, netbios name resolution seems to have stopped working somehow. \\servername lookups no

I have been searching around for solutions to this but none of worked. I am trying to mount a drive over the Internet to my house. Very ugly, but it should work, no? I am pretty certain that I have opened all the correct ports. Here is the root of the problem: davt01-linux:~ # smbclient -I ip.address -L td-home session request to TD-HOME failed (Called name not present) session request to

Hi, I posted this ages ago (http://lists.samba.org/archive/samba/2004- September/093635.html) and never solved the problem so I thought I'd ask again as I've been digging deeper and have more information. I'm using Samba as a WINS server but it's not working reliably. The initial registration works fine on startup but renewals sometimes fail. I tested with a server for which

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

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

We have two FreeBSD 8.0 Samba (3.3.9) servers running with identical smb.conf files, except for the workgroup and netbios parameters. Both serve files flawlessly, but only the first is normally visible to browsing by XP and Win7 clients. Interestingly, if we reboot the first server, then the invisible (second) server becomes visible for several minutes, but then disappears again and is no

hi, when i give samba a workgroup name with more than 15 characters [the limit for netbios names], nmbd is unable to participate in browse master elections. it appears that parts of internal samba code honor 16 characters and parts only honor 15. details: i used a workgroup name of nodomain.nowhere, 16 characters, on samba 2.2.1a. the samba box was the only member of this workgroup on the

I noticed that samba is listening on IPv6, so I became curious and wondered if I could actually use it, and so far, it looks like it isn't usable. Running nbtstat -A fe80::216:3eff:fe6f:1f3a on Windows returns the stupid message that the address must be in the a.b.c.d format. I then tried using nbtlookup from linux: nmblookup -S -U '[fe80::216:3eff:fe6f:1f3a]' \* 10.1.1.232

Hello, I'm having problems getting my samba setup to work at a little LAN i partially maintain. I've been reading quite a lot about what I could think of being related to my problems/setup, and I've also googled my ass off :( So here I am, resorting to you guys in hope of help =] Sorry to say, but I don't have much experience, and therefore I'm a bit lost at the moment. Not

I am running smbd version 2.0.9 and cannot map to a samba share from a Windows 2000 SP2 Server. I can however map from the samba server to the win2k Server. I can also map from the Windows Server to a windows 2000 Pro laptop on the same network, so I know that the server can map shares outside of itself. I can also map from a Win2K pro client and from other unix boxes to the samba server. I can

Samba not responding to broadcast calls from networked PCs. Short: My Redhat Linux 8.0 box is not replying to udp broadcasts, and I can't figure out why. Network: The offending Redhat 8.0 Linux Box (//DS) attempting to run Samba 2.2.7 Firewall Redhat 7.3 (//IW) successfully running Samba 2.2.4 Win98 (//MS) Win2k (//SL) <Not running at the time of these tests> Very long: I've

On Tue, 8 Jan 2019 09:38:54 +0530 venkat ramu <ramut123 at gmail.com> wrote: > Hi Rowland, > > Please find the attached requested details. also Could you please > share right document for the SAMBA configuration with AD > authentication for file server. Thank you the help. > > Thanks, > Venkat OK, you have a choice here, you can either do what I do, which is make