Samba Problems

[Mike Hornung]

Yes, the daemon listens on 123/UDP and (for some reason) binds too all of 
your (operational) network adapters.

---------------------------
-=<(| mike at boobaz.net |)>=-

On Wed, 12 Jul 2000, R. David Whitlock wrote:

|Does xntpd act as a daemon and leave open Yet Another Port on the client?
|
|	      "All of a sudden, I found myself in love with the world
|   		          So there was only one thing that I could do
| 		        Was ding a ding-dang my dang a long ling-long..."
| 		         	     -Ministry, Jesus Built My Hotrod
|
|On Wed, 12 Jul 2000, Mike Hornung wrote:
|
|> An even better solution is to use xntpd.  It's a network service which
|> will talk with a time server (like time.u.washington.edu) and update your
|> clock for you.  It comes with RedHat (don't think it's installed by
|> default though) and Slackware.  I used rdate via cron for a while and
|> had some issues.  No trouble with xntpd.
|> 
|> ---------------------------
|> -=<(| mike at boobaz.net |)>=-
|> 
|> On Wed, 12 Jul 2000, R. David Whitlock wrote:
|> 
|> |Not to change the subject, cause I just now read this and all, but as
|> |relates to the clock issue:
|> |
|> |rdate is an excellent package that will set your system time to that
|> |reported by some time server, and the funtionality is nice.  I had a
|> |system that had bad clock drift (dead CMOS battery, maybe?) a few years
|> |ago, so as a cron job or at the end of my rc.local, I'd do 
|> |"rdate -s time.u.washington.edu", which queries our local time server and
|> |sets the system time appropriately.  There are rpms and tar.gz's out there
|> |all over for it...
|> |
|> |-David
|> |
|> |	      "All of a sudden, I found myself in love with the world
|> |   		          So there was only one thing that I could do
|> | 		        Was ding a ding-dang my dang a long ling-long..."
|> | 		         	     -Ministry, Jesus Built My Hotrod
|> |
|> |On Fri, 7 Jul 2000, Thomas Anderl wrote:
|> |
|> |> Hi All,
|> |> 
|> |> I've been trying to get samba to work with my 2 Windows 98 computers at
|> |> home, but I can't access my linux box through the network
|> |> neighborhood.  It shows up in the network neighborhood, but when I try to
|> |> connect to it, I get a "\\Linux is not accessible. The network is
|> |> Busy" error message.
|> |> 
|> |> Here is what the log.smb file gets after I try to connect to the Linux
|> |> box(yes, I realize that I need to fix my clock ;) :
|> |> 
|> |> [2000/08/05 23:03:44, 0] lib/util_sock.c:write_socket_data(537)
|> |>   write_socket_data: write failure. Error = Broken pipe
|> |> [2000/08/05 23:03:44, 0] lib/util_sock.c:write_socket(563)
|> |>   write_socket: Error writing 4 bytes to socket 5: ERRNO = Broken pipe
|> |> [2000/08/05 23:03:44, 0] lib/util_sock.c:send_smb(751)
|> |>   Error writing 4 bytes to client. -1. Exiting
|> |> 
|> |> I'm running samba 2.0.6 that came with Mandrake 7.0
|> |> 
|> |> Thanks,
|> |> 
|> |> Tom
|> |> 
|> |> 
|> |
|> 
|> 
|