Created attachment 6525 [details]
server ps2 log file
I've been setting up PS2 homebrew and the PS2 homebrew is theoretically able to access samba shares over the network, i've been at #samba on freenode asking for help but i've been directed here due to lack of expertice.
From my log files I have been told that there is a connection between the machine and PS2 and it's even authed, but there's something not working and we can't figure out what that is.
I've attached my samba config file and the log file for the connection between the ps2 and the computer (ps2 having the addr 192.168.0.10, and the "guruplug" is the server -- debug level 10)
-- Couldn't find how to add more than one attachment so you can find my samba config file here, http://pastie.org/pastes/2027645/text
Created attachment 6526 [details]
network traffic on port 445
As vl said on IRC, please attach a debug level 10 log, to do so you need to remove the second log level = 3 line from your smb.conf. Also attach a full network trace, as described on http://wiki.samba.org/index.php/Capture_Packets
I noticed and have been told that my initial bug report was not very informative and here is an improved report.
I ran the command `tcpdump -i eth0 -p -s 0 -w tcpdump.log port 445 or port 139` and the output was as follows, * attachment: tcpdump.log.txt *(junk?)
though if i execute `tcpdump -i eth0 -p -s 0 port 445 or port 139 > tcpdump2.log` I get, * attachment: tcpdump2.log.txt *
my samba log (this time debug level is actually 10) is * attachment: sambalog.txt *
Created attachment 6529 [details]
sudo /usr/sbin/tcpdump -i eth0 -p -s 0 -w tcpdump.log port 445 or port 139
Created attachment 6530 [details]
sudo /usr/sbin/tcpdump -i eth0 -p -s 0 port 445 or port 139 > tcpdump2.log.txt
Created attachment 6531 [details]
Created attachment 6532 [details]
samba log file (__ffff_192.168.0.10.log)
Created attachment 6533 [details]
output from tcpdump
Created attachment 6534 [details]
contents of 192.168.0.10 (ps2) samba log file