Hi! At 21:25 19.02.2003 -0600, you wrote:
Yes. And that's what confuse me. Everyone from a Win98 or W2K workstation can log in and gets the login script and so on - but Samba generates this error message.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1On Wed, 19 Feb 2003, Michael Paarmann wrote: > smbd[7809]: [2003/02/11 18:26:45, 0] > smbd/password.c:domain_client_validate(1517) > smbd[7809]: domain_client_validate: could not fetch trust account > password for domain OFFICE Is office you domain? Did you successfully join the domain?
Can i ignore this ? If yes, it's ok, but this messages fill up my logs.
>In this case:Yes. And the clients crash much more often than before i replace the old server based on novell with Samba. The intenstion of replacing novell was to stabilize the network. I've checked the hardware once again and it's ok.
> smbd[4902]: [2003/02/11 18:32:32, 0] lib/util_sock.c:read_data(436)
> smbd[4902]: read_data: read failure for 4. Error = Connection reset by peer
The client dropped the socket. Not Samba.
>
> smbd[3535]: [2003/02/11 18:33:28, 0] lib/util_sock.c:read_data(436)
> smbd[3535]: read_data: read failure for 4. Error = No route to host
Did the client crash?
But this messages appears whether the client dies or not!
Or are 35 workstations and 15 printers too much for one Samba server ?
> smbd[30829]: [2003/02/11 14:02:15, 0] > rpc_server/srv_netlog.c:api_net_sam_logon(206) > smbd[30829]: api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON. Please see the ml archives on this one. 99% chance you can ignore it.
Can i disable this warning ?
>
> smbd[30829]: [2003/02/11 14:02:15, 0] rpc_server/srv_pipe.c:api_rpcTNP(1200)
> smbd[30829]: api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
>
> smbd[3777]: [2002/12/23 12:03:43, 0] lib/util_sock.c:write_socket_data(500)
> smbd[3777]: write_socket_data: write failure. Error = Broken pipe
>
cheers, jerry
thankx. Michel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
