search for: bonza

Guys, After upgrade to samba 3.3.4 on openSuSE 10.3, I'm getting: Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:write_data(1136) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:get_peer_addr_internal(1676) Jul 10 02:05:14 bonza smbd[31942]: getpeername failed. Error was Transport endpoint is not connected Jul 10 02:05:14 bo...

...idea what could be happening? Note the 3 second delay between packet 27 & 28. It also appears that XP does some dns caching that is persistant during shutdown and restart. I have the laptop at home right now, but you can see the NBNS packets still looking for "Nemesis" and "Bonza" which are two samba servers at work. Go figure?? Any ideas what is happening or how to fix it?? No. Time Source Destination Protocol Info 1 0.000000 rankin-p35.3111skyline.com www.3111skyline.com SMB Trans2 Request, QUERY_PATH_INFO, Query F...

Mates, I have configured samba 100 times, but this time, I'm doing something increadibly stupid that I just cannot see. Please HELP! I'm about to jump...... Background, Old samba sever (nemesis) being replaced with new one (bonza). Both are up and operating. All networking is OK, Name resolution is fine, etc. The problem is that all users can see all the shares on the new machine (bonza) just fine. They can map and browse their home share, but *cannot* browse any of the other shares. I on the other hand, as admin user,...

Listmates, I have had a few boxes where the 'matchname' message is filling my syslog with one new message ever ~40 seconds or so. No performance problems, just the log annoyance. An example of the messages are: Jan 11 13:43:03 nemesis smbd[2246]: [2010/01/11 13:43:03, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:43:03 nemesis smbd[2246]: Matchname failed on Adrienne-PC.rbpllc.com

POSTED TO THE LIST W/O ATTACHMENTS -------- Jerry, I am sending this to you directly because it contains the tcpdump information in addition to the samba logs just in case there is sensitive information contained in the files. What is happening is that samba 3.0.25c, after first running smoothly, is becoming very "chatty" across our LAN. I don't know why, but with no files or

My goal is to make VPN access to our Samba PDC (FreeBSD 7.0) so that users can access there home shares from Windows clients. I have read the instructions at http://samba.org/ftp/unpacked/lorikeet/pppd/final-report.pdf, but I can't make it work. Don't know if is due to my lack of skills or has something to do with the Popop functionality in FreeBSD. Following the instructions, i made a

...iled to find name * david@rankin-xp:~> nmblookup -d 2 '*' added interface ip=192.168.7.90 bcast=192.168.7.255 nmask=255.255.255.0 querying * on 192.168.7.255 Got a positive name query response from 192.168.7.15 ( 192.168.7.15 ) 192.168.7.15 *<00> david@rankin-xp:~> smbclient //bonza/office Password: Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.23b] tree connect failed: NT_STATUS_ACCESS_DENIED I have attached a level 10 debug if that will help. This is a standalone server. Right now I am running on 3.0.20 after saving myself with a "make revert" Gotta love...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've uploaded the *final* 3.0.23c roll up patch to http://samba.org/~jerry/patches/patch-3.0.23b-3.0.23c-gwc-2.diffs.gz. I've already cut the 3.0.23c tarballs so unless there is a major problem, this will be the final change set. Please report *any* bugs that you find. I'd like to wrap this one up and do the public 3.0.23c

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've upload the preliminary patch against 3.0.23b that will become 3.0.23c so people can do full testing against what we hope to be the release code. Note that the reported version in the patch is 3.0.23c-gwc-1 to prevent confusion from the final 3.0.23c release. You can download the gzipped patch file from