Samba 2.0.3 problem

[Jesse Book Jr]

Hello,
	This morning my users started complaining that they could not log in to
the network.  When trying to log in people get a long pause and then a
message that the password was wrong, or there was no machine to
authenticate them.  When I check the logs I get the following errors:

[1999/04/22 08:18:37, 0] lib/util_sock.c:write_data(407)
  write_data: write failure. Error = Broken pipe
[1999/04/22 08:18:37, 0] lib/util_sock.c:write_socket(191)
  write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[1999/04/22 08:18:37, 0] lib/util_sock.c:send_smb(568)
  Error writing 4 bytes to client. -1. Exiting
[1999/04/22 08:19:11, 0] lib/util_sock.c:write_data(407)
  write_data: write failure. Error = Broken pipe

I saw a message like this in the newsgroups, but there were no replys.  The
other wierd happening that may or may not be related, was that once a user
does get logged in to the network (after 9-10 tries)  they can not connect
to the apache web server running on the samba box.  My setup is a Slackware
Linux 3.6 box running Samba 2.0.3 and Apache.  The Box has 2 network cards
in it and serves as a gateway machine too.  Connecting to Samba, and Apache
from the external side is still working.  If you have any hints on what is
causing this and how to fix it please email me directly.

-= Jesse =-