Thanks for the response, Brad.

Brad wrote:
> 
> On Sat, 19 Jun 1999, Kent West wrote:
> 
> > Now I can't even find smbclient, and I can't find what package contains
> > it.
> 
> Looks like it's in the smbclient package... You may have to look in
> unstable, i don't remember if slink has the proper versions or not.

Apparently it's not in the Stable (Slink?) branch, but I pointed my
sources.list to unstable and was able to install it.

<snip>

> >  3) What is the currently correct syntax to connect to a WinNT share?
> > The share is named "//big_guy/common" and the username is "westk" and
> > the mount point I want to use is "/NetShare".
> 
> That's the important question... i obviously can't test this, but this
> command _should_ work.
> 
> smbmount-2.2.x '\\big_guy\common' -Uwestk -I 150.252.x.x -c 'mount /NetShare 
> -u uid -g gid'

<snip>

Returns the following:

westk03:/home/westk#  smbmount-2.1.x '\\big_guy\common' -U westk -I
150.252.3rd_octet.4th_octet -c 'mount /NetShare -u 1000 -g 1000'
params.c:OpenConfFile() - Unable to open configuration file
"/etc/smb.conf":
        No such file or directory
Can't load /etc/smb.conf - run testparm to debug it
load_client_codepage: filename /etc/codepages/codepage.850 does not
exist.
Added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Server time is Mon Jun 21 00:19:41 1999
Timezone is UTC-5.0
Password: 
Domain=[ACU] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
security=user
westk03:/home/westk# 

I entered my password at the prompt. Then, as soon as I try to do an "ls
/NetShare", I get:

westk03:/home/westk# ls /NetShare smbmount: got signal, getting new
socket
Password: [I type in my password again, and it displays in full living
color] 
ls: /NetShare: Input/output error
ls: [password displayed again in full living color]: No such file or
directory
westk03:/home/westk# 

Then the eterm I'm doing all this in just stops responding. I can close
it and open another one and go on with life.

(BTW, I'm having to "umount /NetShare" after each attempt or on the next
try I get an error message.)

I tried it again after installing smbclient, but it does the same thing.

smbclient seems to work just fine.

There is indeed no /etc/smb.conf file, but it seems that if I needed one
the installation of the smbfsx package would have prompted me or given
me an example file or there'd be a man page for it or something.

> >  4) Will the smbmount (or smbmount-2.2.x) command work over a dial-up
> > connection? The dial-up connection is provided by my university, and
> > that's where the server is located. My local IP (provided by the dial-up
> > connection) has the same first two octets (150.252.x.x) as the rest of
> > campus, but the third octet (and probably forth, but not necessarily) is
> > different.
> 
> i don't see why it wouldn't...

Because before I posted to this list I searched the web and the mail
archives and etc and somewhere in all that I read that samba (or smbfs,
I forget) wouldn't work across routers and that it needed to be on the
same LAN segment, but since I'm not a networking guru I'm not entirely
sure if that applies here.


Then I thought, "Hey, why not install the version from Unstable?". So I
did. Now the errors have decreased, but still no success. The output
looks like:

westk03:/home/westk# smbmount-2.2.x '//big_guy/common' -U westk -c
'mount /NetShare'
Added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
Server time is Mon Jun 21 00:52:04 1999
Timezone is UTC-5.0
Password: 
Domain=[ACU] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
security=user
westk03:/home/westk# ls /NetShare 
ls: /NetShare: Input/output error
westk03:/home/westk# 

And the eterm window doesn't lock up.

HOLD IT! STOP THE PRESSES!

Oh, that's too weird...

I just up-arrowed to recall the last time I tried it, and this time it
worked!
I had been trying it as root all this time because of the mount point
not being mountable by westk. So as another test I tried mounting it
using /home/westk/bub as my mount point logged in as westk, not root.
Again, the same type error messages. So I "su"'d back to root and
up-arrowed one last time as I said in the first sentence of this
paragraph, and it worked.

Something strange going on here....

Reply via email to