similar to: Error Printing Using Samba

Displaying 20 results from an estimated 400 matches similar to: "Error Printing Using Samba"

2009 Feb 06
2
smbtree Error NT_STATUS_HOST_UNREACHABLE
Hi, I've been running samba on a linux machine (dslkayak) to share a folder and a printer with several windows machines on a home network for a couple of years without problems. I've recently added a second linux machine (ps3ydl) to the network, but I cannot access it from any other machines on the network even though it can access the other network shares. There error I get is:
2002 Sep 22
0
CUPS filtering mechanism explained, was: [cups raw mode, was Re: unlink data file in cups_job_submit]
Paul Janzen wrote on Samba digest: > Message: 7 > To: Gerald Carter <jerry@samba.org> > Cc: samba@lists.samba.org > From: Paul Janzen <pcj@samba.sez.to> > Subject: cups raw mode, was Re: [Samba] unlink data file in cups_job_submit > Date: 21 Sep 2002 12:09:23 -0700 > > > Gerald Carter <jerry@samba.org> writes: > > > Looks right to
2019 Apr 04
1
Shared printing between Linux (client) and Windows (server): NT_STATUS_ACCESS_DENIED
Applied the update: $ sudo samba --version Version 4.9.5-Debian The results of `posix_open' and `queue' cmds stay the same. Printer is idle on print cmd. A GUI problem with endless authentication request was shot down: 1. Delete the printer 2. Add a new one 3. Network Printer -> Search -> 192.168.0.100 -> Authorization Reqired: username "user", password
2010 Nov 15
3
Win7 SLOW printing
Greetings, We use a dedicated samba-3.3.12+cups-1.3.11 on debian lenny to serve printing (with point and print) to windows clients. We're getting complaints that some clients (win7, vista, XP) have to wait an awful long time from when they hit 'print' to when the job starts coming out of the printer. Other clients (win7, vista, XP) print right away. I can tail the cups log and
2007 Jul 19
1
odd "Not listening on called name behavior"
After migrating from RHEL 3 to Fedora Core 6 I get the following error message repeatedly libsmb/cliconnect.c:cli_start_connection(1445) session request to *SMBSERVER failed (Not listening on called name) : 15 Time(s) What is *SMBSERVER? I don't have anything with that name on the network. libsmb/cliconnect.c:cli_start_connection(1445) session request to DSARABIA-WKS failed
2013 Sep 04
1
Samba 3.6.9 on Centos 6.4 and very slow first access to fileserver
Hello good people, I am fighting with following issue: our users are complaining about very slow/delayed displaying of main folders during accessing server using \\dns.name.of.server (using \\IP or \\netbios_name is it with same slowness). But once they are authenticated, displaying contents of (sub-)folders are getting normal. Once the user hit "enter" key on
2011 Jan 05
2
Odd printing issue
Over the last few days, our users have started experiencing delays in printing. In the log files (for the client), we now see [2011/01/05 11:12:34.360166, 1] libsmb/cliconnect.c:2216(cli_start_connection) cli_start_connection: failed to connect to MACHINENAME<20> (::ffff:IPADDRESS). Error NT_STATUS_UNSUCCESSFUL As new systems are affected, these errors appear. We get about 7 of them
2006 Feb 21
0
Authenticating Samba on NT4 SRV
Hi, I'm just using samba for few weeks and i'm triing to migrate all NT4 SAM base to Samba Linux. I'm working with Red Hat enterprise Linux ES 4.0 updated, openldap 2.2.13-4, samba samba-3.0.10-1.4E.2 and i've followed IDEALX migration procedure with smbldap-tools-0.9.3-1. Every configuration seems to be clean but not ;o))))) I'm using cleartext password in slapd.conf and
2007 Jun 07
0
LAN and public IP
Hi, I am running Debian (Sid) and Samba 3. My computer which intends to be only a SMB client is on a LAN (192.168.2.0/24) We have a gateway to internet and it's public IP address is 81.56.120.7. When I launch smbtree in order to "scan" existing SMB shares over the _LAN_ : ?mihamina@mihadev:~$ smbtree ?Password: ?MAINET ? ? ? ? \\SOPHIE ? ? ? ? ? ? ? ? ? ? ? ?SOPHIE ?timeout
2009 Jun 13
0
Failed to join domain: The network name cannot be found -
I get this error "Failed to join domain: The network name cannot be found " while trying to connect my linux server to a windows 2003 server domain. Details Below. root@sandstone:/etc/squid# net ads join -U administrator@MIL.LOCAL administrator@MIL.LOCAL's password: Failed to join domain: The network name cannot be found root@sandstone:/etc/squid# net ads join -U
2003 Oct 17
0
Problems with Trust Relationship
Hey All, I'm having problems with a Trust relationship between our Win 2002 PDC and our Samba PDC. Here are the details: (names have been changed to protect the innocent...!) Win 2002 PDC: WINPDC, IP 1.2.3.4 Client in Windows Domain: CLIENT Samba PDC in Domain TEST: SMBPDC I use Start -> Run -> \\SMBPDC on a machine in our Windows 2000 Domain and got an error saying "\\SMBPDC, A
2002 Sep 17
2
configuration & cups
I seem to be having a great deal of trouble with cups and samba configuration. cups seems to go on and off and it works and doesn't work. I think I need some help on my samba configuration. Generally, it has worked well on another machine, but my current setup seems a bit screwy. System: FreeBSD 4.6.2; cups-1.1.15.1; cups-base-1.1.15.1_4; cups-lpr-1.1.15.1_1;cups-pstoraster-7.05.5;
2011 Oct 29
0
samba 3.5.6 & win2k8 r2, session request fails
Hi I've been trying to join a debian6 (IP: 172.16.0.180) box to a win2k8 r2 active directory (ORCHARD, IP: 172.16.0.200), without much success. The settings for samba and kerberos are correct: - and kinit works fine The error string returned is: 'failed to lookup DC info for domain 'ARIAS.INT' over rpc: The network name cannot be found'
2008 Nov 21
2
Why does the server want to connect to a client
Hi, I have 5 of 140 Windows XP SP2/SP3 machines that make problems when printing. The client open the printer dialog and it takes a long time (up to 1 minute) before it appears. Printing is slow, too. Meanwhile I see the following messages (repeating several times) in the client log: [2008/11/21 08:17:28, 1] lib/util_sock.c:open_socket_out(888) timeout connecting to 10.1.0.253:445
2007 Jul 07
0
joining samba 3.0.25b on aix to a native w2k domain
Hi, I've compiled Samba 3.0.25b on an AIX 5.2 machine without any hassle (also without ADS / Kerberos Support!) but getting it to join our AD domain is a true PITA. The AIX machine is called NLXDRZ05, the domain D-REIZEN.INTRA (could also be D-REIZEN, I'm a Unix guy, not an NT guy and I usually leave that stuff to the people that know what they're doing) I've had a machine
2004 May 06
0
Winbindd/network freeze samba
Packet send failed to 62.101.92.90(137) ERRNO=Network is unreachable [2004/05/03 10:27:45, 0] nmbd/nmbd_packets.c:reply_netbios_packet(975) Hi list, once again looking for some good advice. I apologize for the long email and for the mistakes I could have done. I'm running Samba 3.0.2-6.3E on White box linux 3.0 kernel 2.4.21-4.EL (clone of Red Hat EL 3.0), the environment is a Win 2k ADS
2005 Oct 20
0
Unable to join domain
I am attempting to have a Samba3-0.10 server join an NT domain with no success. Samba has been installed (./configure --with-syslog --with-acl-support) on a SunFire V240 with Solaris 9 as the OS. >From what I've read if the machine account exists on the domain then I should not have to provide a password. I am however being prompted for a password even though th account exists. I am
2004 Jun 22
2
Unable to join Windows 2k AD NT_STATUS_ACCESS_DENIED
I am having horrendous issues with trying to get Samba 3.0.4 to join to a Windows 2000 AD (patched to current). As this one is hurting a bit and needs to be fixed soon, I was hoping I may find salvation in this list from someone here who may be able to shed some useful light on this issue. I am using the latest gentoo mit-krb5 build. Net join always results in NT_STATUS_ACCESS_DENIED - this
2004 Feb 26
0
Unable to access Samba Domain Member
Hi, I'm trying to connect to a Samba Domain Member, but I always end up with the same strange error. The PDC (authenticating againt LDAP) and the server itself (Lobo) are Samba 3.0.2a-1 (Debian). I first tried to connect from my Windows client. It gave me the following error: "\\Lobo is not accessible. The specified network name is no longer available." When connecting via
2005 May 31
0
windbind stopped working
I recently upgraded my PDC's and BDC's to 3.0.14a but my member servers are still running 3.0.10. Today users complained that the couldn't logon to the member server. When I try to run a wbinfo -u I get: Error looking up domain users Here's the log.windbindd: 2005/05/31 11:06:26, 4] param/loadparm.c:lp_load(3933) pm_process() returned Yes [2005/05/31 11:06:26, 3]