Re: alsaconf and printing

On Tue, 30 Oct 2007 22:10:15 +0100, Florian Kulzer wrote:

On Tue, Oct 30, 2007 at 19:32:51 -0000, Ed wrote:

To test your ability to access the SMB-shared printer, run this
command on the client machine:

smbclient -U USER -L //HOST

This will list all SMB-shares (folders, printers, etc.) which USER
can access on HOST. (You will be prompted for USER's password on
HOST.)


When I issue the above command from either the host machine that the
printer is connect to, OR the Debian machine that I have been trying to
get working, I get back an error message session setup failed:
NT_STATUS_LOGON_FAILURE --- yet the linux machine that the printer is
connected to prints fine, AND the two windows laptops print fine
through the linux samba server. However, I suppose I have something
wrong in my smb.conf file.

Does your smb.conf file allow connections from that computer?

Are you sure you are using the right USERname and password?

I think getting NT_STATUS_LOGON_FAILURE means that there is at least
some communication between client and host, so we can probably rule out
elementary network problems. Nevertheless it cannot hurt to try pinging
the host from the client and making sure that there isn't a firewall on
the host blocking access of the client.

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |

Hi,

I added a line to my /etc/hosts file on the debian machine indicating the
ip address of the local machine that the printer is connected to and the
machine name. Really the only reason I did this was so when I wanted to
ping it, I could use the machine name which is 3 letters long, verses the
ip number which is 12 char long. Anyway, after that - printing and
smbclient -H username started to work. I don't know why, but then I
guess I more want to use the machine, then become an expert in debian so
I suppose, I am satisfied as long as it continues to work. I admit, I
hate when things just start working, or doing something for reason x
solves problem y as serendipity. Oh well THANKS very much for all your
help. I 'think' everything is working now.

Ed


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: SSH Option files using hashes instead of hostnames?
    ... But if you only typed "slowpoke" on the command line, ... client can't even look up the canonical FQDN from that. ... And yet, ssh today will accept a non-fqdn today, even without a "hostname" entry in your config. ... I admit that this would not work in cases where you're using both host and hostname for the same host in your options file. ...
    (SSH)
  • RE: ICS clients cannot connect
    ... I've got this from the ICS host: ... I turned off ICS host and then enabled it. ... the client and entered "ipconfig /release". ... goto one of the client machines and do the same, ...
    (microsoft.public.windowsxp.general)
  • Re: HTTPS; SSL-Tunnel
    ... Referring Server Destination Host Name Transport MIME Type Object Source ... Source Proxy Destination Proxy Bidirectional Client Host Name Filter ... > SSL-tunnel OFT Website anonymous Internal External ...
    (microsoft.public.isa)
  • Re: alsaconf and printing
    ... To test your ability to access the SMB-shared printer, run this command ... (You will be prompted for USER's password on HOST.) ... some communication between client and host, so we can probably rule out ...
    (Debian-User)
  • =?Utf-8?Q?RE:_RE:_WCF_Service_Library:_=E2=80=9Cca?= =?Utf-8?Q?nnot_change_thread_mode_after
    ... Thank you for your response. ... It helped me solve the problem of the host ... (Notice that the client app can be any ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.distributed_apps)