Hello Samba-aholics ;-)
I apologize for posting this question for the third time now, but it's
becoming frustrating...
when I use smbclient -L $SERVER to see which shares are available in a
PC box I miss something sometimes. For example:
-----------------------------------------------------------------------
# smbclient -L pivita
Added interface ip=192.1.1.21 bcast=192.1.1.255 nmask=255.255.255.0
Server time is Wed Sep 24 17:42:32 1997
Timezone is UTC-7.0
Server=[PIVITA] User=[] Workgroup=[JALEO] Domain=[]
Sharename Type Comment
--------- ---- -------
ADMIN$ Disk
DESKJET 520 Printer
DOLORES Disk
IPC$ IPC Remote Inter Process Communication
PRINTER$ Disk
NOTE: There were share names longer than 8 chars.
On older clients these may not be accessible or may give browsing errors
-----------------------------------------------------------------------
PIVITA is a Win95 box.
I know for certain that there are almost two shares more called C$ and
D$. If I execute a smbtar -v -s pivita -x ADMIN$ -t
/usr/tmp/testfile.smbtar I
can actually transfer files from PIVITA and store them in
testfile.smbtar. If I let the smbtar command do its task to the end or
even if I interrupt the process and then I take a look at the shares on
the Win95 machine, I see:
-----------------------------------------------------------------------
# smbclient -L pivita
Added interface ip=192.1.1.21 bcast=192.1.1.255 nmask=255.255.255.0
Server time is Wed Sep 24 17:42:32 1997
Timezone is UTC-7.0
Server=[PIVITA] User=[] Workgroup=[JALEO] Domain=[]
Sharename Type Comment
--------- ---- -------
ADMIN$ Disk
C$ Disk
D$ Disk
DESKJET 520 Printer
DOLORES Disk
IPC$ IPC Remote Inter Process Communication
PRINTER$ Disk
NOTE: There were share names longer than 8 chars.
On older clients these may not be accessible or may give browsing errors
-----------------------------------------------------------------------
After that I can transfer the files from the share(s) I really need (C$
and/or D$).
I use SAMBA 1.9.16p11 running on a SGI under IRIX 6.2 and the problems
arise with Win95 boxes. I still haven't experienced such a case with
NT's.
Any clue/ideas/help/comments on how could I execute a smbtar of C$
and/or D$ without executing first smbtar of ADMIN$? Is this a bug or am
I overseeing obvious things? :-/
Thanks in advance and best regards,
M@rtin
--
==================================Martin Mielke
Jaleo Development Office - SysAdmin
martin@jaleo.idecnet.com
Tel.: ++ 34 28 262299
Fax : ++ 34 28 263504
===================================
Luke Kenneth Casson Leighton
1997-Oct-07 12:57 UTC
Bug Report - smbclient can't see sometimes... III
On Tue, 7 Oct 1997, Martin Mielke wrote:> Hello Samba-aholics ;-) > > I apologize for posting this question for the third time now, but it's > becoming frustrating... > > when I use smbclient -L $SERVER to see which shares are available in a > PC box I miss something sometimes. For example:try smbclient -L $SERVER -U $USER luke <a href="mailto:lkcl@switchboard.net" > Luke Kenneth Casson Leighton </a> <a href="http://mailhost.cb1.com/~lkcl"> Lynx2.7-friendly Home Page </a> <br><b> "Apply the Laws of Nature to your environment before your environment applies the Laws of Nature to you" </b>
On Tue, 7 Oct 1997 21:37:16 +1000, you wrote:>Hello Samba-aholics ;-) > > >After that I can transfer the files from the share(s) I really need (C$ >and/or D$). > >I use SAMBA 1.9.16p11 running on a SGI under IRIX 6.2 and the problems >arise with Win95 boxes. I still haven't experienced such a case with >NT's. > >Any clue/ideas/help/comments on how could I execute a smbtar of C$ >and/or D$ without executing first smbtar of ADMIN$? Is this a bug or am >I overseeing obvious things? :-/ >Have you tried running smbtar on C$ even when it can't be seen in smbclient -L. If I recall correctly when you run smbtar with a sharename it will simply request \\server\share from smbclient which I understand, and I may be wrong here, simply requests the share from the windows machine, without first asking the windows machine for a list of shares and checking if it's on. It is therefore reasonable to assume that it might be possible that the windows machine simply isn't listing the C$ share in it's "i've got these shares" lists until it's been accessed in some way by the smbclient but it will still recognise requests of "i want to access C$ on your machine" and reply with "yeah sure here you go" instead of "what??? never heard of it, I don't have anything of the sort here". If that doesn't work you might want to try the following: echo "\nquit\n" | smbclient \\\\server\\admin$ -U guest -N before running your smbtar.