On 22 Nov 2002, Bradley W. Langhorst wrote:
> After a thorough google and marc search i'm shocked to find
> this problem unmentioned...
>
> How does one go about changing the windows password from a unix machine
> with no physical access to the windows machine sharing things?
SWAT provides the pa
Just use smbpasswd.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
After a thorough google and marc search i'm shocked to find
this problem unmentioned...
How does one go about changing the windows password from a unix machine
with no physical access to the windows machine sharing things?
samba 2.2.3a (debian woody)
windows2000 server
thanks!
brad
note: here'
Hi,
I have reciently been attempting to connect an OS\390
system to a windows file server using the smbclient
program that is part of the MVS port of samba.
The problem I have encountered is this. When I try to
connect from MVS to windows without a password I can
connect with no problem at all
I thought the 13 character limit was a 'feature' of NT, and thus Samba
reflects that "feature", too... anyone know?
--On Tuesday, November 19, 2002 4:56 PM -0500 Diana McKenna
<[EMAIL PROTECTED]> wrote:
Hello All,
If I create a 13 char long share on a filer or a windows workstation (a
windows
Hello All,
If I create a 13 char long share on a filer or a windows workstation (a
windows 2000 workstation for example) and then run sbmclient to list the
shares on that system smbclient will not list any shares greater than 12
chars long. I can see and access the long share name on my window
If I create a 13 char long share on a filer or a windows workstation (a
windows 2000 workstation for example) and then run sbmclient to list the
shares on that system smbclient will not list any shares greater than 12
chars long. I can see and access the long share name on my windows system
an
If I create a 13 char long share on a filer or a windows workstation (a
windows 2000 workstation for example) and then run sbmclient to list the
shares on that system smbclient will not list any shares greater than 12
chars long. I can see and access the long share name on my windows system
an
uestions:
--
* Is smbclient's "queue"-command broken in 2.2.4 and 2.2.6? Did it ever
work? Is there anything special one needs to know?
* How can this be debugged on Windows? (I have currently no direct access
to the Windows boxen -- my partner on the other end 50 miles
Hello Samba list,
I lately noticed a strange behaviour :
nmblookup MyPC
returns the name & IP of the host
using "MyPC" as netbios name.
but,
smbclient -L MyPC
never connects as it returns an incoherent IP
(some fuzzy public IP nothing to with the local
network).
this is a fresh 2.2.3a install on
Just a stab in the dark, is there any chance it's an issue with those
Windows files being "in use" and locked for reading or writing?
[EMAIL PROTECTED] wrote:
I use smbclient for - among other things - backing up all the windows
clients to my DLT every night.
I get errors like the following.
Hello Andrew,
On Fri, Oct 25, 2002 at 10:45:11AM +1000, Andrew R Reid wrote:
[...snip...]
>
> If the only answer is to update to 2.2.6 and see how it goes, I'll do
> that. I just love the Debian package managing system a lot and don't
> really want to break it :-(
>
[...snip...]
Steve Langa
I use smbclient for - among other things - backing up all the windows
clients to my DLT every night.
I get errors like the following.
65808 ( 549.3 kb/s) \WINDOWS\SYSTEM\TDC.OCX
87097 ( 611.9 kb/s) \WINDOWS\SYSTEM\WMIDX.OCX
176400 ( 745.7 kb/s) \WINDOWS\SYSTEM\WMP.OCX
995
* Andrew Bartlett ([EMAIL PROTECTED]) wrote:
> Martin Sarajervi wrote:
> >
> > Im trying to send Winpopup messages to my XP computer from my linux
> > server (running samba),
> >
> > smbclient -M void
> >
> > added interface ip=212.33.141.45 bcast=
Martin Sarajervi wrote:
>
> Im trying to send Winpopup messages to my XP computer from my linux
> server (running samba),
>
> smbclient -M void
>
> added interface ip=212.33.141.45 bcast=212.33.141.63 nmask=255.255.255.192
> added interface ip=212.33.147.58 b
Im trying to send Winpopup messages to my XP computer from my linux
server (running samba),
smbclient -M void
added interface ip=212.33.141.45 bcast=212.33.141.63 nmask=255.255.255.192
added interface ip=212.33.147.58 bcast=212.33.147.63 nmask=255.255.255.248
added interface ip=212.33.147.59
Hi,
I have installed samba on my pc but I can't connect from my win-client.
the problem are the following:
1)if I do: smbclient //server/tmp -U root
It will be ok, but if I type: smbclient //server/tmp -U root%secret
Then the result is : "session setup failed: ERRSRV - ERRbadpw (Bad
passw
When trying to connect to a samba server using smbclient on the local
machine (or any other unix machine with smbclient), I get a "protocol
negotiation failed" error. When I try to connect to the same server using
a windows client it works just fine...
Regardless of whether the client is on t
pinging doesn't mean the WINS service is running. Try sending
a name resolution query to the WINS server using
nmblookup -R -U 172.16.0.121 MySQL
Kenneth Illingsworth wrote:
>
> I played with the smb.config file long enough to get both the smbd and nmbd daemons
>to run. Then ran TESTPARM agai
On Fri, Oct 04, 2002 at 08:51:48AM -0400, Kenneth Illingsworth wrote:
> I played with the smb.config file long enough to get both the smbd and
> nmbd daemons to run. Then ran TESTPARM against the correct smb,conf
> file without issue. Finally I tried the following command:
>
> [root@cofr3 /]# sm
I played with the smb.config file long enough to get both the smbd and nmbd daemons to
run. Then ran TESTPARM against the correct smb,conf file without issue. Finally I
tried the following command:
[root@cofr3 /]# smbclient -U illingsk -L MySQL
added interface ip=172.17.60.6 bcast=172.17.63.2
"[EMAIL PROTECTED]" wrote:
>
> Hy,
> can anyone help me?
> When I try to use "smbclient -L localhost -U", after password entry,
> It is shown:
> Domain=[LINUX] OS=[Unix] Server=[Samba 2.2.5]
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>
> What can I do?
>
> Thanks.
>
> Francesco
The -L
Hy,
can anyone help me?
When I try to use "smbclient -L localhost -U", after password entry,
It is shown:
Domain=[LINUX] OS=[Unix] Server=[Samba 2.2.5]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
What can I do?
Thanks.
Francesco
--
To unsubscribe from this list go to the following URL
On Mon, 23 Sep 2002, Benjamin, Devon wrote:
>
> Is there a version of smbclient that supports traversing MS-DFS links?
> smbclient 2.0.7 and 2.2.0 both fail when trying to follow MS-DFS
> redirects.
smbclient does not currently support MS-DFS. Steve French's
cifs fs for Linux does though.
Is there a version of smbclient that supports traversing MS-DFS links? smbclient
2.0.7 and 2.2.0 both fail when trying to follow MS-DFS redirects.
Thanks.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
I've reviewed and successfully tested everything from ping up to logging in
locally with :
smbclient //server/share
Now begins the problems:
#1 If I turn Encrypted Passwords the preceding command fails.
#2 On the Win98 client the command (tested with encrypted passwords on and
off with same res
Dienstag den 17.09.2002 um 15:38 CEST +0200, schrieb Palmer Magnus:
> Hi,
>
> I hope this is the correct mailinglist for my question.
>
> I've made a script that sends a file to a NT shared folder.
> As long as I make a successfull connect, I get return status 0...
> This is a problem, since no
Hi,
I hope this is the correct mailinglist for my question.
I've made a script that sends a file to a NT shared folder.
As long as I make a successfull connect, I get return status 0...
This is a problem, since now I can't make a correct errorhandling if
something goes wrong.
+/opt/samba-2.0.5a
Hi fellow samba users,
I'm having a problem with smbclient on Red Hat 7.2 transferring files from a
Win2k box. I am able to connect to the Win2k, login, list, traverse
directories, and even copy several files. However, shortly after I start to
transfer lots of files, smbclient just hangs. It w
On Wed, 22 May 2002, Pierre Belanger wrote:
> Hi,
>
> Is this a bug?
>
> By mistake, I was trying to connect to a samba server using
> smbclient... but the samba server did not allow my client to
> connect to the server, because of a "hosts allow" restriction.
>
> I can understand smbclient re
Hi,
Is this a bug?
By mistake, I was trying to connect to a samba server using
smbclient... but the samba server did not allow my client to
connect to the server, because of a "hosts allow" restriction.
I can understand smbclient reporting the first error:
session request to ALKONOST failed
I am very bad with password questions because I avoid all such things
by using guest ok = yes and guest account = ftp and security = share in
my global smb.conf section.
If you go this route, you might need to change security in each of your
shares, too. Don't know.
Joel
On Mon, May 20, 2002 at
This is going to sound like a rediculously dumb question, but I have just
finished reloaing RedHat 7.2 (from 7.1), a clean install, and samba appears
to be running, but I cannot log into my shares. I am rejected with a "bad
password - name/password pair..."
Now, I've been though this setup a doz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi !
I hope it is of interest to some of you. I have made a small
patch to smbclient/netbeui that makes it use only the core protocol for
printing, when you give it the -P option. It also supports the continuation
of a print job from the point wher
I am trying to setup samba ver 2.2.2-hppa1.1-hp-hpux11.00.tar so that i can attach a
unix share to a windown xp and windows 2000 workstation, when i try and run :
smbcleitn -L computername -N
i get:
added interface ip=172.27.20.34 bcast=172.27.20.255 nmask-255.255.255.0
session request to 172.27.
> On Thu, 02 May 2002 00:13, you wrote:
> > You don't need samba to print, just smbclient. That is, you don't need to
> > be running a samba server.
> > Since you don't have much time and don't want to mess around with a lot of
> > stuff, here is the quick and dirty way. Assuming your printer is
>
Oh, by the way, is the print file you are trying to send formatted for your
printer?
Joel
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
I don't have a printer on a windows box to mess with, but:
I would GUESS this is a problem on the win2k box. I would look at the
permissions on your printer in windows. Maybe take password protection or
whatever off that share (make sure it is shared!)
Since this might be a spooling error, look
On Thu, 02 May 2002 00:13, you wrote:
> You don't need samba to print, just smbclient. That is, you don't need to
> be running a samba server.
> Since you don't have much time and don't want to mess around with a lot of
> stuff, here is the quick and dirty way. Assuming your printer is
> postscrip
> Hi LUs,
>
> I dont have much time at the moment to read tons of documentation. So, I
> would like to ask a hopefully easy to answer question.
>
> Samba is running alright with me, smbclient works fine, but I would like to
> print from my Linux box over LAN to a printer (HP 560C) connected to
I got lazy. The full command with gs might look like this:
cat YourPostscriptFile | \
gs -q -sDEVICE=YourPrintingDevice -sOutputFile=- - | \
smbclient //Server/printershare PasswordStuff -c "print -"
quit
The trick is YourPrintingDevice. Look at gs -h for what is available.
Joel
On Wed, May 01,
You don't need samba to print, just smbclient. That is, you don't need to be
running a samba server.
Since you don't have much time and don't want to mess around with a lot of
stuff, here is the quick and dirty way. Assuming your printer is postscript,
just print your document in postscript format
On Wed, 1 May 2002, Diembo wrote:
> Hi LUs,
>
> I dont have much time at the moment to read tons of documentation. So, I
> would like to ask a hopefully easy to answer question.
Shame shame ;)
> Samba is running alright with me, smbclient works fine, but I would like to
> print from my Linux bo
Hi LUs,
I dont have much time at the moment to read tons of documentation. So, I
would like to ask a hopefully easy to answer question.
Samba is running alright with me, smbclient works fine, but I would like to
print from my Linux box over LAN to a printer (HP 560C) connected to a win2k
box.
On Fri, 19 Apr 2002, Angel F. Rosa wrote:
> Hello,
>
> I am trying the following with an error, anyone have any ideas here?
>
> /usr/local/samba/bin>smbclient //fileserver/home
> added interface ip=192.168.1.1 bcast=192.168.255.255 nmask=255.255.0.0
> Password:
> Anonymous login successful
Per
Hello,
I am trying the following with an error, anyone have any ideas here?
/usr/local/samba/bin>smbclient //fileserver/home
added interface ip=192.168.1.1 bcast=192.168.255.255 nmask=255.255.0.0
Password:
Anonymous login successful
Domain=[EARTH] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
On Wed, 2002-04-17 at 18:52, Urban Widmark wrote:
> > failed (code 143). I can however interact with other win95 computers
> > with shared disks from the same linux computer. What am idoing wrong
> > Is it at all posible to use an dos shared drive with smbclient?
> > for exsample:
> > --
On 17 Apr 2002, Samo Gabrovec wrote:
> Hello!
>
> I have a dos box which has a shared disk (no password) i can access this
> disk from any windows machine (win95) but not from linux with smbclient.
>
> what ever command i run (to list shares, mount it ...) i get *SMBSERVER
> failed (code 143).
Hello!
I have a dos box which has a shared disk (no password) i can access this
disk from any windows machine (win95) but not from linux with smbclient.
what ever command i run (to list shares, mount it ...) i get *SMBSERVER
failed (code 143). I can however interact with other win95 computers
wi
401 - 449 of 449 matches
Mail list logo
