similar to: The strangest problem..

> I have a network that sporadically give 'network busy' errors. One morning > the workstations will all connect up fine and stay up throughout the days > work, yet the next day there is not one machine that can log on to the > network. It may run fine for two weeks, then bam, three days of no logins. > Yet the internet works fine. Could I copy my smb.conf file and rpm -e

Hello all, This my first mail in this list. We have succesfully setup a samba server at our 1st attempt, next we go in another site and try the same things but now it seems we got it all wrong! The facts: we have a linuxbox (named enlogic) (REdHat 7, kernel 2.2.18, samba 2.0.7)and one winbox win98se (named ndemou). Our workgroup is localenlogic. No other PC (not even a Hub because we've

Hi Folks, I am running Samba 2.0.6 on Solaris 2.6 and I have a bunch of write errors showing up in my log.smb file. Here are some of them: ---------------------------------------------- [1999/12/16 14:25:42, 1] lib/util_sock.c:client_name(997) Gethostbyaddr failed for 10.41.0.184 [1999/12/16 14:25:42, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken

Hi everybody, I'm writing for an any help. I tried some news groups about linux etc... nothing :-( On our normaly working network unexpectly starts this problem. Win clients don't see smb server. See logs below: log.nmb [2002/03/11 09:37:33, 1] nmbd/nmbd.c:main(757) Netbios nameserver version 2.0.10 started. Copyright Andrew Tridgell 1994-1998 [2002/03/11 09:37:33, 0]

> Message: 1 > Date: Fri, 08 Mar 2002 08:45:57 -0500 > From: Michael Joyner <mjoyner@ewc.edu> > Organization: MIS - Edward Waters College > To: Thom Paine <thom@darksaber.com> > Cc: Gustav Tresselt <gtressel@broadpark.no>, > Samba List <samba@samba.org> > Subject: Re: [Samba] 'Network Busy' - indeed > > It is a reverse DNS problem.

doing something wrong by not registering our workstations with a DNS? I have been searching through the documentation today without finding anything relevant on the subject. When our PC's are configured via DHCP to use our caching only DNS, will they start looking up machines on our local network using DNS and forget everything about WINS and broadcast? It worked just perfectly for nearly

Jason Haar <Jason.Haar@trimble.co.nz> wrote: | Well I've just had a crash last night, and I've copies the log files off. | But I see nothing to suggest what happened. Also I've enabled core-dumps, | and no core dump exits, even though smbd died... | | If you look at the smb.conf file, you'll see I've put in a HUGE sleep | statement to be called via "panic

Hi all, here's hoping you can help with a problem I have got. I am currently running samba 3.0.7-1 on a Suse 9.0 system and I am having the following problem. I am trying to get my samba server to join a windows NT4 domain called BVFL-DOM and then use winbind to get user names from that domain to be use samba. The samba box joins the NT domain without a problem and I can use NT server

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

Iam running Samba 2.0.10 on a FreeBSD 4.2 platform within a Windows 98/2k peer to peer network. Most of the time this system appears to be working very well with the file system nicely browsable by the client machines. Unfortunately, from time to time the following error appears within the log.smb: [2002/02/14 10:54:28, 3] lib/util.c:interpret_addr(1833) Get_Hostbyname: Unknown host. ed0

Hi: I am running Samba 1.9.17 at SUN Solaris 2.6 and it works well. After I upgrade Samba 2.0.3 or 2.0.5a, my Excel spreadsheets got trouble. In the Samba log file I got: [1999/08/23 10:45:32, 0] lib/util_sock.c:write_socket_data(570) write_socket_data: write failure. Error = Broken pipe Anybody has an idea what is the problem? I

can someone with more samba knowledge then me tell me what this means in my log file? [2000/06/28 16:37:31, 1] lib/util_sock.c:client_name(997) Gethostbyaddr failed for 192.168.0.1 It doesn't appear to be a problem with samba itself but rather the way I have my network setup? any help would be appreciated.. the reason being I am having random connection problems with my cleint windows2000

I have tried everything I can think of, including all of the remedies in the diagnostics site. I always get the following error when I try to connect to my SAMBA server: [root@pdslnx /root]# smbclient -L PDSLNX Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0 session request to PDSLNX failed session request to *SMBSERVER failed I can connect to my other machines (W95 and

Hi all! I'm configuring Samba 3.0.1 on Solaris 9 (rel s9_58shwpl3) Sparc. Have successfully installed Ldap libs, Krb5 libs, and, finally - Samba. Trying to join W2KSP4 domain. net rpc join -S dc01 -U Administrator Gives bash-2.05# /usr/local/samba/bin/net rpc join -S dc01-tmn -U Administrator Password: Joined domain MYDOMAIN. Now i start winbindd. The smb.conf file is:

I get the following errors in log.smb: [1999/02/24 17:02:44, 1] lib/util_sock.c:client_name(810) Gethostbyaddr failed for <CLIENTs IP> [1999/02/24 17:02:44, 0] lib/util_sock.c:write_data(407) write_data: write failure. Error = Broken pipe [1999/02/24 17:02:44, 0] lib/util_sock.c:write_socket(191) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [1999/02/24

Thanks to a couple of pointers from readers here, plus the PROFILES.txt documentation (that wasn't in the old 1.9.17xx distribution I was using), I got profiles/policies working. Yay!!! However, another issue has cropped up for us. We had a network outage last week that cut our subnet off from any DNS nameservers. At that point, Samba quit working. Looking at the logs, client computers

Greetings. Is there something up with Samba and RedHat, or with recent kernels, or with some packages that have been updated recently? A lot of us seem to see the same login errors with samba and I have yet to get my windows clients to login to my new samba server. The log messages really don't help. I had an old server running Samba 2.0.7 (RedHat 5.0 upgraded to nearly 5.2 with 2.0.33).

I am having problems with Samba. Things have been working I think but they aren't now. We have 2 class C addresses, one doesn't seem to be having as many problems as the other. When folks on the 207 side try to connect to Samba shares they can usually but right now are failing and getting a network busy error. The file called log. which appears to be a system log file for samba says:

Hi! Short time ago our Samba-Server crashed during normal use with low load. (Ping was working, but no login was possible (didn't ask for password on the terminal)). Perhaps it is a bug, or perhaps it is a problem with my machine and you can help me. I am running: SuSE Linux 6.4 Samba Version 2.0.6 (smbd) Kernel: 2.2.14 (original SuSE-Kernel) Some Logfiles: /var/log/warn ... Aug 16

Hi. Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have added will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont