Hi! One last try before ditching Samba and buying Windows 2000 Server... Server: RedHat 7.0 with Samba 2.0.7, set up as PDC to be able to run logon scripts. PC's: Norwegian Windows 98 with all the stuff from windowsupdate (including explorer 5.5) Every morning, all our Windows 98 users (we have about 20 of them) have to log on multiple times, usually between 2 and 5, before being able to log on to our domain. They get an error message saying something about not being able to contact the domain controller. But when they finally are able to log on, everything works very well untill the next morning. Our Windows NT 4.0 users are able to log on just fine every time they try. In the log.pcNN logfiles, we get the following 3 lines for every attempt: [2000/11/27 09:45:01, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2000/11/27 09:45:01, 0] lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [2000/11/27 09:45:01, 0] lib/util_sock.c:send_smb(754) Error writing 4 bytes to client. -1. Exiting But even worse: If the server is restarted while all workstations are off, it takes exactly 3 hours from the first workstation is back on until people are able to log on again. (Again, except for our NT users...) So I just have to tell them: "wait until lunch time, then everything will be OK!" And during these 3 hours, it is not possible to view any network information from any Windows 98 machine. "net view" gives a message about not finding the machine controlling shared resources or something like that (freely translated from Norwegian), while "smbclient -L pc07" works just fine and also shows all our workgroups with masterbrowsers, and everything looks just fine. It has not always been like that. The problem first turned up in an earlier version of Samba. I think when we upgraded to 2.0.6 or maybe 2.0.5, and has been there ever since. I have tried to change nearly every parameter in smb.conf, but nothing seems to help. So I should be really grateful if someone is able to help! I have also searched the internet, and it seems that there are other people having similar problems, but I have never seen anybody providing an answear that works for us. (btw: has anyone tested 2.2-alpha1? Is it stable enough to cause less problems than the version we are running? :) Svein Roar Nilsen
Svein Roar Nilsen wrote:> > One last try before ditching Samba and buying Windows > 2000 Server... > > Server: RedHat 7.0 with Samba 2.0.7, set up as PDC to be > able to run logon scripts. > > PC's: Norwegian Windows 98 with all the stuff > from windowsupdate (including explorer 5.5)the behavior you describe is pretty bad. Could you send me you smb.conf file? wrt the 'write errors', check for network layer error (such as packet lose, etc...) as well as DNS problems (bad reverse name resolution, etc...) CHeers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
Hello, Do you also have problems with locks ? I have same messages with same behaviour (same config), except the '3 hours outage'. It also stops some software (as ms-office) in normal use. The only thing I found to minimize in some way these problems was to put a slave DNS server on the same computer as Samba. But the problem is here, although less frequent. Take care about reverse naming (IP -> name). It seems a timing problem in Samba. I posted a question a few days ago in this list, but no answer. If you get solution, please mail to me. Hope this helps. Gilles SIMON "Svein Roar Nilsen" <svein-roar.nilsen@statkart.no> wrote:> Hi! > > One last try before ditching Samba and buying Windows 2000 Server... > > Server: RedHat 7.0 with Samba 2.0.7, set up as PDC to be able to run > logon > scripts. > > PC's: Norwegian Windows 98 with all the stuff from windowsupdate > (including > explorer 5.5) > > Every morning, all our Windows 98 users (we have about 20 of them) > have to log > on multiple times, usually between 2 and 5, before being able to log > on to our > domain. They get an error message saying something about not being > able to > contact the domain controller. But when they finally are able to log > on, > everything works very well untill the next morning. Our Windows NT 4.0 > users are > able to log on just fine every time they try. > > In the log.pcNN logfiles, we get the following 3 lines for every > attempt: > > [2000/11/27 09:45:01, 0] lib/util_sock.c:write_socket_data(540) > write_socket_data: write failure. Error = Broken pipe > [2000/11/27 09:45:01, 0] lib/util_sock.c:write_socket(566) > write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe > [2000/11/27 09:45:01, 0] lib/util_sock.c:send_smb(754) > Error writing 4 bytes to client. -1. Exiting > > But even worse: If the server is restarted while all workstations are > off, it > takes exactly 3 hours from the first workstation is back on until > people are > able to log on again. (Again, except for our NT users...) So I just > have to tell > them: "wait until lunch time, then everything will be OK!" And during > these 3 > hours, it is not possible to view any network information from any > Windows 98 > machine. "net view" gives a message about not finding the machine > controlling > shared resources or something like that (freely translated from > Norwegian), > while "smbclient -L pc07" works just fine and also shows all our > workgroups with > masterbrowsers, and everything looks just fine. > > It has not always been like that. The problem first turned up in an > earlier > version of Samba. I think when we upgraded to 2.0.6 or maybe 2.0.5, > and has been > there ever since. > > I have tried to change nearly every parameter in smb.conf, but nothing > seems to > help. So I should be really grateful if someone is able to help! I > have also > searched the internet, and it seems that there are other people having > similar > problems, but I have never seen anybody providing an answear that > works for us. > > (btw: has anyone tested 2.2-alpha1? Is it stable enough to cause less > problems > than the version we are running? :) > > > Svein Roar Nilsen >-- Gilles SIMON gilsim@wanadoo.fr
Hi Sounds like DNS probs to me. Check reverse mappings and the log.nmb log file. Should point you in the right direction. Don't put yourself through the NT/2000 hell, definitely not worth it. Thanks Regards Darren Philps darren.philps@bigfoot.com ABN: 64 423 959 118 -----Original Message----- From: Gilles SIMON <gilsim@wanadoo.fr> To: svein-roar.nilsen@statkart.no <svein-roar.nilsen@statkart.no> Cc: samba@lists.samba.org <samba@lists.samba.org> Date: Tuesday, November 28, 2000 8:11 PM Subject: Re: Windows 98 + domain logons>Hello, > >Do you also have problems with locks ? >I have same messages with same behaviour (same config), except the '3 >hours outage'. It also stops some software (as ms-office) in normal use. > >The only thing I found to minimize in some way these problems was to put >a slave DNS server on the same computer as Samba. But the problem is >here, although less frequent. Take care about reverse naming (IP -> >name). >It seems a timing problem in Samba. > >I posted a question a few days ago in this list, but no answer. If you >get solution, please mail to me. > >Hope this helps. > >Gilles SIMON > > >"Svein Roar Nilsen" <svein-roar.nilsen@statkart.no> wrote: >> Hi! >> >> One last try before ditching Samba and buying Windows 2000 Server... >> >> Server: RedHat 7.0 with Samba 2.0.7, set up as PDC to be able to run >> logon >> scripts. >> >> PC's: Norwegian Windows 98 with all the stuff from windowsupdate >> (including >> explorer 5.5) >> >> Every morning, all our Windows 98 users (we have about 20 of them) >> have to log >> on multiple times, usually between 2 and 5, before being able to log >> on to our >> domain. They get an error message saying something about not being >> able to >> contact the domain controller. But when they finally are able to log >> on, >> everything works very well untill the next morning. Our Windows NT 4.0 >> users are >> able to log on just fine every time they try. >> >> In the log.pcNN logfiles, we get the following 3 lines for every >> attempt: >> >> [2000/11/27 09:45:01, 0] lib/util_sock.c:write_socket_data(540) >> write_socket_data: write failure. Error = Broken pipe >> [2000/11/27 09:45:01, 0] lib/util_sock.c:write_socket(566) >> write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe >> [2000/11/27 09:45:01, 0] lib/util_sock.c:send_smb(754) >> Error writing 4 bytes to client. -1. Exiting >> >> But even worse: If the server is restarted while all workstations are >> off, it >> takes exactly 3 hours from the first workstation is back on until >> people are >> able to log on again. (Again, except for our NT users...) So I just >> have to tell >> them: "wait until lunch time, then everything will be OK!" And during >> these 3 >> hours, it is not possible to view any network information from any >> Windows 98 >> machine. "net view" gives a message about not finding the machine >> controlling >> shared resources or something like that (freely translated from >> Norwegian), >> while "smbclient -L pc07" works just fine and also shows all our >> workgroups with >> masterbrowsers, and everything looks just fine. >> >> It has not always been like that. The problem first turned up in an >> earlier >> version of Samba. I think when we upgraded to 2.0.6 or maybe 2.0.5, >> and has been >> there ever since. >> >> I have tried to change nearly every parameter in smb.conf, but nothing >> seems to >> help. So I should be really grateful if someone is able to help! I >> have also >> searched the internet, and it seems that there are other people having >> similar >> problems, but I have never seen anybody providing an answear that >> works for us. >> >> (btw: has anyone tested 2.2-alpha1? Is it stable enough to cause less >> problems >> than the version we are running? :) >> >> >> Svein Roar Nilsen >> > > >-- >Gilles SIMON >gilsim@wanadoo.fr >