Bug 8209 - ps2 homebrew can't access samba share
Summary: ps2 homebrew can't access samba share
Status: NEW
Alias: None
Product: Samba 3.2
Classification: Unclassified
Component: File services (show other bugs)
Version: 3.2.5
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 14:51 UTC by craigayre
Modified: 2011-06-06 21:50 UTC (History)
1 user (show)

See Also:


Attachments
server ps2 log file (30.47 KB, application/octet-stream)
2011-06-06 14:51 UTC, craigayre
no flags Details
network traffic on port 445 (1.62 MB, application/octet-stream)
2011-06-06 15:06 UTC, craigayre
no flags Details
sudo /usr/sbin/tcpdump -i eth0 -p -s 0 -w tcpdump.log port 445 or port 139 (46.07 KB, text/plain)
2011-06-06 21:34 UTC, craigayre
no flags Details
sudo /usr/sbin/tcpdump -i eth0 -p -s 0 port 445 or port 139 > tcpdump2.log.txt (24.00 KB, application/octet-stream)
2011-06-06 21:35 UTC, craigayre
no flags Details
cat /var/log/samba/__ffff_192.168.0.10.log (1.10 KB, text/plain)
2011-06-06 21:37 UTC, craigayre
no flags Details
samba log file (__ffff_192.168.0.10.log) (42.53 KB, text/plain)
2011-06-06 21:40 UTC, craigayre
no flags Details
output from tcpdump (12.12 KB, application/octet-stream)
2011-06-06 21:49 UTC, craigayre
no flags Details
contents of 192.168.0.10 (ps2) samba log file (39.72 KB, application/octet-stream)
2011-06-06 21:50 UTC, craigayre
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description craigayre 2011-06-06 14:51:28 UTC
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
Comment 1 craigayre 2011-06-06 15:06:30 UTC
Created attachment 6526 [details]
network traffic on port 445
Comment 2 Kai Blin 2011-06-06 15:26:41 UTC
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
Comment 3 craigayre 2011-06-06 21:32:29 UTC
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 *
Comment 4 craigayre 2011-06-06 21:34:03 UTC
Created attachment 6529 [details]
sudo /usr/sbin/tcpdump -i eth0 -p -s 0 -w tcpdump.log port 445 or port 139
Comment 5 craigayre 2011-06-06 21:35:53 UTC
Created attachment 6530 [details]
sudo /usr/sbin/tcpdump -i eth0 -p -s 0 port 445 or port 139 > tcpdump2.log.txt
Comment 6 craigayre 2011-06-06 21:37:43 UTC
Created attachment 6531 [details]
cat /var/log/samba/__ffff_192.168.0.10.log
Comment 7 craigayre 2011-06-06 21:40:20 UTC
Created attachment 6532 [details]
samba log file (__ffff_192.168.0.10.log)
Comment 8 craigayre 2011-06-06 21:49:52 UTC
Created attachment 6533 [details]
output from tcpdump
Comment 9 craigayre 2011-06-06 21:50:39 UTC
Created attachment 6534 [details]
contents of 192.168.0.10 (ps2) samba log file