search for: netbuie

We have one brand new HP EPC-43 which can see all the Windows boxes, but not the Samba shares on the Unix server. We have many other Windows machines of all vintages including 95, 98, 98se, NT, 2000, ME and XP which can see each other and the Samba server. The HP runs XP, but we have other XP boxes which have no difficulty with Samba. We have a simple network with no domain controller, just

Hi, I believe it's mentioned in one of the docs with the samba distro, that this problem can happen, when you have File and print services enabled on the PC's using a protocol _other_ than tcp/ip like NETBUI or IPX. Samba use's TCP/IP only. Marc Heckmann UNIX systems Space Technologies, SGS Canadian Space Agency

Hi there, I have two Samba servers running within an NT domain. One Samba (F-Samba) server runs samba-1.9.18.10 on top of FreeBSD-2.2.8 and the other (L-Samba) runs samba-1.9.18p2-C6 on a RedHat Linux variant. All of our NT machines run NT4,SP4. One is workstation and the rest run server. The PDC is an NT Server (NT1). F-Samba and L-Samba only show up in the browsers of about half of the

I have setup a small office of 6 win95/98 workstations and a Samba share (SuSE, Samba 2.0.6) on a P90 with 32MB of RAM and 2, 2GB HD?s. File sharing and PDC functions work perfectly (better than any NT machine). However, I cannot get the samba computer to show up in network neighborhood. I set the netbios name to SAMBA and wins = yes. When I go to start => run and type <\\samba>, the

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

Hi, I've looked through the samba archives, and saw no messages related to this. Is there a way to get smbtar to tar long filenames? When I restore the files, they're all cut down to 8.3 format. smbclient does see the long filenames of an NetBui drive, why doesn't smbtar? Thanks. Gabe

Hi All: I have scoured the archives and done a Google search with no answers. I set up Samba on Redhat 7.2 Samba 2.2.1a-4 on a friends network. He is running 2 Windows 98 machines. They can't browse network neighbourhood. Sometimes rebooting the machines will fix it temporarily. Shutting down Samba allows the Windows Machines to browse the network. So, I am pretty sure it is the culprit.

I have posted more messages, essentially to the same effect... had quite a few good answers, but somehow I seem to be missing something ... :-( Well, I told you already about the workgroup DAARO, which refused to show up... I got some suggestions, and, indeed, there it was! I could even log in to it. And then, next morning, I started up my test network, ... no DAARO. However, after a restart

I'm just getting started, and getting quite a strange result. I've been able to mount my (login hal) Linux home directory as E: on my w95 system, but when I try to "smbmount //isdn2/AMDAHL-WORK /mnt/amdahlwork", where /mnt/amdahlwork is an empty directory on Linux, isdn2 is defined in /etc/hosts as 192,168.1.2, the address the W95 box uses, and AMDAHL-WORK is the name under

I recently installed Samba-2.0.6 on my machine. I copied the smb.conf over from another, working machine that I just got rid of. Anyway, I can't seem to get things working. Here are some files: when I 'restart' nmb in SWAT ---(log.nmb): Netbios nameserver version 2.0.6 started. [2000/02/02 13:33:19, 1] nmbd/nmbd.c:main(747) Netbios nameserver version 2.0.6 started. Copyright

Sorry if this is the subscription address and not the mailing list address, if so..... subscribe sglenister@comcab.co.uk ;-) Guess what...I have a problem. Bound to be my lack of knowledge about Netbios/ WINS/Netbui etc.... Been going through the DIAGNOSIS.txt tests and have got this far... ../smbclient -d 10 -L indy1 which gives... ============================================== 07/13/1998

I can only conclude that Samba is an elaborate hoax and here's why. 1) Setup is more complex than Sendmail (it set the standard for complexity) 2) Even the simplest smb.conf causes trouble 3) You can pass ALL the tests in the DIAGNOSIS procedure, AND Samba will still not let you SHARE FILES or SHARE PRINTERS between Windows and Unix but you WILL be able to BROWSE YOUR SHARES (Just pretend

Hey, so i finally got it working thanks to your list (found the right place for EnablePlainTextPassword here, the existing 3-4 matches in the default registry don't seem to do a thing). It was all brilliant. I got connected to all my 4 samba servers. I was happy... 'til the next boot (you know, during installation of system, boots happen). Now it connects to 3 sambas (1 on FreeBSD, 1 on

to see the logs to check. Andrew Bartlett Samba Build Farm Maintainer -- Andrew Bartlett abartlet@pcug.org.au abartlet@samba.org Return-Path: <gcarter@valinux.com> Delivered-To: samba@samba.org Received: from Eng.Auburn.EDU (dns.eng.auburn.edu [131.204.10.13]) by lists.samba.org (Postfix) with ESMTP id 48F454E77; Tue, 3 Jul 2001 06:56:24 -0700 (PDT) Received: from localhost

... (port 138, setting options)... [2001/07/10 20:11:23, 3] nmbd/nmbd.c:(541) open_sockets: Broadcast sockets opened. [2001/07/10 20:11:23, 2] lib/interface.c:(85) added interface ip=141.43.132.161 bcast=141.43.132.191 nmask=255.255.255.192 [2001/07/10 20:11:23, 3] lib/util_sock.c:(832) bind succeeded on port 137 ... (port 138, setting options)... [2001/07/10 20:11:23, 2]

...dd some additional info. I mapped a share from a win2k workstation to a dos machine, and I experience the same crap write performance :/ So this is not a samba problem, but by chance, if someone has some good advice please let me know! I don't want to have to change all the dos clients back to netbuie and use a NT4 server! Kind Regards, -Jev On Tue, Jul 10, 2001 at 05:12:46AM -0500, Jev wrote: > Hello all, > > I recently switched from using NT4 server to samba 2.2.0a as a PDC in a > production network, the network in question has a lot of msdos clients > using MSCLIENT. >...

<-----------------------------------------------------------------------> Changes to user passwords are captured by a special DLL, which traps and then stores the password changes in encrypted form in a private area. On each synchronization schedule, the synchronization service first examines the SAM file for changes, and then checks this private area for passwords to be synchronized. Once