similar to: newbie help, please?

Am Dienstag, 13. März 2018, 11:21:17 CET schrieb Praveen Ghimire: > Harry, > > Thank you. > > Unfortunately we don't have the choice of upgrading LDAP due to distro > not supporting the newer version. However we have managed to get it > to work. A lot of fiddling around. > > I do have another question though ;). Now that we have LDAP > replicating, how do I

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

Hi, here is a client computer and a server computer (Debian Wheezy, armel, samba Version 3.6.6, IP address: 192.168.1.2, Name: xyz). Problem: wins doesn't answer nmblookups by the client on the broadcast address: client$ nmblookup -S xyz querying xyz on 192.168.1.255 name_query failed to find name xyz Why is that so? How to fix this? When I specify the the server IP I do get an answer:

I'm stumped on getting Samba to work again on our small network. I've got one Windows 95 machine that started to refuse to talk to Samba last week. I *was* running one of the 1.9.18 releases, but when it stopped working, I figured I would delete the old release and do a clean install of 2.0.3. I've done that, and used SWAT to configure the smb.conf file (which can be seen below).

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

After much nashing of teeth, I have compiled and installed Samba on Mac OS X! The following lines (or something like them) should probably be added to the config.guess file in the samba/source directory: Power*:Darwin:*:*) echo powerpc-apple-darwin${UNAME_RELEASE} exit 0 ;; I added them right after the "mac68k:OpenBSD:*:*)" section. I was not able to get the inetd installation

Hi All, Due to a hard-disc crash, I have just upgraded from a working Samba setup running in FC2 to a non-functional Samba setup running in FC3. The Windows XP machine has not changed, but won't connect. Samba is fully up2date from the FC3 repositories. smb.conf [global] workgroup = MYGROUP server string = Samba Server hosts deny = ALL hosts allow = 192.168.1.0/24 127.

Ok folks, the saga continues, but this is an issue that I think should concern all Samba users/sysadmins. It appears to me that Samba is NOT communicating with the WINS server (at least not consistently) for authentication of login requests when a pc tries to get logged in and map a drive letter to a share. In smb.conf I have the following relevant entries: name resolve order = wins host bcast

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

Linux 2.2.14, samba 2.0.7 Summary: samba kept __MSBROWSE__ registered but thought it was not the master browser. Details: 1) samba started and became master browser (6/13/2000 0.00) 2) then there was a problem on the network (I played with ipchains...) 3) samba received an announce from a win9x pc claiming it was MB (6/13/2000 circa 8.00AM) Due to the problems of point2, the election that

I just installed Redhat 8.0, got the errata samba packages, but I still can't get Samba to work. I have gone through the Diagnosis.txt file with the following results: Test 1: everything appears OK Test 2: pings work both ways Test 3: OK Test 4: # nmblookup -B lion __SAMBA__ querying __SAMBA__ on 192.168.8.14 192.168.8.14 __SAMBA__<00> OK Test 5: # nmblookup -B cub '*'

Hello. I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC. Samba can't find its hostname via nmblookup: $ nmblookup -B 192.168.1.255 frontier querying frontier on 192.168.1.255 name_query failed to find name frontier If I query Samba via unicast, it answers OK: $ nmblookup -U frontier frontier querying frontier on 192.168.1.31 192.168.1.31 frontier<00> Also,

Everyone, I am hoping that someone can help me. I have been trying for several weeks to get Samba working to no avail. I have consulted many online help files including the ones located at http://us1.samba.org/samba/docs/DIAGNOSIS.html, browsing.txt that comes with samba, http://us2.samba.org/samba/ftp/docs/Samba24Hc13.pdf, and a few others. I have even posted a previous message, which

I used to be able to browse the windows shares on the network through Nautilus. I can see them as computers, but when I click on them, it fails. (I'm on Ubuntu 6 LTS, AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am

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, My name is Zoran. I have been trying to setup a network with win98 for my home network which i need quite ergently so i can continue my work. My problem seems general, but the general solutions dont seem to solve it. I have spent a good week trying to figure it out and believe me i have tried almost every trick there is, and u guys are the last resort. If u help me solve this one you have

Hi, My name is Zoran. I have been trying to setup a network with win98 for my home network which i need quite ergently so i can continue my work. My problem seems general, but the general solutions dont seem to solve it. I have spent a good week trying to figure it out and believe me i have tried almost every trick there is, and u guys are the last resort. If u help me solve this one you have

Hi, My name is Zoran. I have been trying to setup a network with win98 for my home network which i need quite ergently so i can continue my work. My problem seems general, but the general solutions dont seem to solve it. I have spent a good week trying to figure it out and believe me i have tried almost every trick there is, and u guys are the last resort. If u help me solve this one you have

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