On 3/10/12, Michael Havens <
bmike1@gmail.com> wrote:
> Okay.... you want me to tail samba's log. I stated I didn't know which file
> to tail..... but then I just realized you wanted me to tail samba's log and
> I know how to find that! but I don't know which log to tail. (the complete
> list of logs is at the end of this) I am going to give you the tail of the
> logs for the two that I think it might be:
>
> /var/log/samba/log.192.168.0.2 <-this just return through
> /var/log/samba/log.sonydesktop
>
> those are the ip of the xp and the machine name of the XP. Let me know if
> I'm wrong.
>
> bmike1@Michaels-PC:~$ tail /var/log/samba/log.sonydesktop
> getpeername failed. Error was Transport endpoint is not connected
> write_data: write failure in writing to client 0.0.0.0. Error Connection
> reset by peer
> [2012/02/25 08:38:26.260843, 0] smbd/process.c:79(srv_send_smb)
> Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
> [2012/02/28 14:45:50.288046, 0] lib/util_sock.c:680(write_data)
> [2012/02/28 14:45:50.346247, 0]
> lib/util_sock.c:1441(get_peer_addr_internal)
> getpeername failed. Error was Transport endpoint is not connected
> write_data: write failure in writing to client 0.0.0.0. Error Connection
> reset by peer
> [2012/02/28 14:45:50.346502, 0] smbd/process.c:79(srv_send_smb)
> Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
> bmike1@Michaels-PC:~$
>
> ====logs====
> /var/log/samba/log.0.0.0.0
> /var/log/samba/log.127.0.0.1
> /var/log/samba/log.192.168.0.2
> /var/log/samba/log.192.168.0.3
> /var/log/samba/log.192.168.0.4
> /var/log/samba/log.__ffff_127.0.0.1
> /var/log/samba/log.__ffff_192.168.0.2
> /var/log/samba/log.__ffff_192.168.0.3
> /var/log/samba/log.__ffff_192.168.0.4
> /var/log/samba/log.__ffff_192.168.0.6
> /var/log/samba/
log.bt
> /var/log/samba/log.c7250
> /var/log/samba/log.michaels-laptop
> /var/log/samba/log.michaels-pc
> /var/log/samba/log.nmbd
> /var/log/samba/log.nmbd.1.gz
> /var/log/samba/log.nmbd.2.gz
> /var/log/samba/log.nmbd.3.gz
> /var/log/samba/log.nmbd.4.gz
> /var/log/samba/log.nmbd.5.gz
> /var/log/samba/log.nmbd.6.gz
> /var/log/samba/log.nmbd.7.gz
> /var/log/samba/log.samba
> /var/log/samba/log.smbd
> /var/log/samba/log.smbd.1.gz
> /var/log/samba/log.smbd.2.gz
> /var/log/samba/log.smbd.3.gz
> /var/log/samba/log.smbd.4.gz
> /var/log/samba/log.smbd.5.gz
> /var/log/samba/log.smbd.6.gz
> /var/log/samba/log.smbd.7.gz
> /var/log/samba/log.sonydesktop
> /var/log/samba/log.toshiba-user
> bmike1@Michaels-PC:~$
>
>
>
> On Tue, Mar 6, 2012 at 6:50 PM, Michael Havens <
bmike1@gmail.com> wrote:
>
>> okay.... I enabled the guest account but that didn't improve the situation
>> any. I checked localhost:631 and the printer is listed. (weird thing, from
>> the laptop it is listed as a different model. It works so I don't really
>> care)
>>
>> ====
>> 1) As you initially asked, your XP account name was changed. Please refer
>> to the enabling of the guest account HowTo in:
>>
http://unixwiz.net/techtips/samba-xp-printing.html NOTE: I am assuming
>> that these machines are protected inside your network, since it's usually
>> a
>> BAD IDEA to enable the guest account otherwise. Verify your WORKGROUP and
>> NetBIOS name in XP.
>>
>> Please, then, attempt to connect from XP and tail the log and see what
>> Samba is whining about?
>>
>> ====
>> Not sure of the logs name. Can you help me out? I also don't know about
>> the net
>> --
>> :-)~MIKE~(-:
>>
>