Hi all, I am running SunOS 5.5.1 and am getting all sorts of problems. I am urgently in need of help. My Unix skills are limited. My first problem is starting the daemons. bind failed on port 139 socket_addr=0 (Address already in use) My second problem is the difference in the number of files dumped with either smbtar or smbclient. Here is the command that gives me the most problems. Notice the number of dumped files in each case. I also get an error with NAMSIZ. smbclient '\\chuck\c' -N -Tc tar.out "\my documents" "\windows\desktop" "\windows\start menu" arg 0 = \my documents arg 1 = \windows\desktop arg 2 = \windows\start menu ERRDOS - ERRbadfile opening remote file \windows\Start Menu\Programs\Remote Desktop\What_s New about Remote Desktop 32.lnk tar file \windows\Start Menu\Programs\PC Gamer December 97 Disc 3.9\Uninstall PC Gamer December 97 Disc 3.9.lnk name length exceeds NAMSIZ tar: dumped 252 tar files Total bytes written: 2941952 smbclient '\\chuck\c' -N -Tc tar.out "\my documents" "\windows\desktop" "\windows\start menu" arg 0 = \my documents arg 1 = \windows\desktop arg 2 = \windows\start menu ERRDOS - ERRbadfile opening remote file \windows\Start Menu\Programs\Remote Desktop\What_s New about Remote Desktop 32.lnk tar file \windows\Start Menu\Programs\PC Gamer December 97 Disc 3.9\Uninstall PC Gamer December 97 Disc 3.9.lnk name length exceeds NAMSIZ tar: dumped 236 tar files Total bytes written: 2932224 smbclient '\\chuck\c' -N -Tc tar.out "\my documents" "\windows\desktop" "\windows\start menu" arg 0 = \my documents arg 1 = \windows\desktop arg 2 = \windows\start menu ERRDOS - ERRbadfile opening remote file \windows\Start Menu\Programs\Remote Desktop\What_s New about Remote Desktop 32.lnk tar file \windows\Start Menu\Programs\PC Gamer December 97 Disc 3.9\Uninstall PC Gamer December 97 Disc 3.9.lnk name length exceeds NAMSIZ tar: dumped 154 tar files Total bytes written: 83456 smbclient '\\chuck\c' -N -Tc tar.out "\my documents" "\windows\desktop" "\windows\start menu" arg 0 = \my documents arg 1 = \windows\desktop arg 2 = \windows\start menu ERRDOS - ERRbadfile opening remote file \windows\Start Menu\Programs\Remote Desktop\What_s New about Remote Desktop 32.lnk tar file \windows\Start Menu\Programs\PC Gamer December 97 Disc 3.9\Uninstall PC Gamer December 97 Disc 3.9.lnk name length exceeds NAMSIZ tar: dumped 215 tar files Total bytes written: 2923008 Thank you for taking the time to read this cry for help. Charles Lawson-Glen (South Africa) P.S.. I hope you are watching the cricket. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 2831 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/19980123/66f1399c/attachment.bin
Hi, I am using a Linux client (SuSE Linux 7.0 with 2.2.16 kernel) within our Windows network. This is experimental and my private initiative so I am not supposed to count on the help of my network administrators (and they are not supposed to know about it). Anyway I had no problems accessing shares with smbclient. This changed a week ago for unknown reasons. Connecting to the share still works, but an 'ls' ends up in an error message. The share itself is still accessable from Windows clients. What happens is: bash-2.04# smbclient //fthw002x/temp_pt1 -U<user> -W<workgroup> added interface ip=x.y.203.3 bcast=x.y.255.255 nmask=255.255.0.0 Password: <typing in my password> Domain=[FTHW002X] OS=[UNIX 5.7 Generic_106541-08] Server=[Solaris PC NetLink] smb: \> ls code 0 listing \* Error in dskattr: code 0 smb: \> read_socket_with_timeout: timeout read. read error Daten?bergabe unterbrochen (broken pipe). I have also used the -dA option to get a detailed trace log. I have attached a part of the log. Please mind that it is shortened trastically but I think the most important section is available. Help is very much appreciated, Karlheinz smbclient trace log after typing 'ls': smb: \> ls size=83 smb_com=0x32 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=8 smb_flg2=1 smb_tid=1 smb_pid=544 smb_uid=32791 smb_mid=1 smt_wct=15 smb_vwv[0]=15 (0xF) smb_vwv[1]=0 (0x0) smb_vwv[2]=10 (0xA) smb_vwv[3]=4356 (0x1104) smb_vwv[4]=0 (0x0) smb_vwv[5]=0 (0x0) smb_vwv[6]=0 (0x0) smb_vwv[7]=0 (0x0) smb_vwv[8]=0 (0x0) smb_vwv[9]=15 (0xF) smb_vwv[10]=68 (0x44) smb_vwv[11]=0 (0x0) smb_vwv[12]=83 (0x53) smb_vwv[13]=1 (0x1) smb_vwv[14]=1 (0x1) smb_bcc=18 [000] 00 44 20 16 00 00 02 06 00 04 01 00 00 00 00 5C .D ..... .......\ [010] 2A 00 *. write_socket(3,87) write_socket(3,87) wrote 87 read_socket_with_timeout: timeout read. EOF from client. receive_smb: length < 0! client_receive_smb failed size=0 smb_com=0x0 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=0 smb_flg2=0 smb_tid=0 smb_pid=0 smb_uid=0 smb_mid=0 smt_wct=0 smb_bcc=0 code 0 listing \* write_socket(3,39) write_socket(3,39) wrote 39 read_socket_with_timeout: timeout read. EOF from client. receive_smb: length < 0! client_receive_smb failed size=0 smb_com=0x0 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=0 smb_flg2=0 smb_tid=0 smb_pid=0 smb_uid=0 smb_mid=0 smt_wct=0 smb_bcc=0 Error in dskattr: code 0 Total bytes listed: 0