similar to: Samba Printing Extremely Slow from Windows XP

Help! I'm in the process of migrating my companies Windows NT print server to Samba 3.2. (yea) But I'm running into a few problems. (boo) I've searched the archives and google with no success... I have about 15 clients testing out the new server, mainly Win2k. Some work fine, but others have problems connecting, getting the "Unable to Connect" message in the printer folder.

Hi, do ports 445 and 139 (incoming) have to be open for the samba server's IP on WinXP client side (all WinXP clients are using netbios over TCP/IP)? F-Secure 7.10 blocks all incoming microsoft-ds (445) and netbios-ssn (139) by default, which ends up in very slow printer-shares behaviour (for example opening the properties or the spool window of a samba-printer takes up to 30 seconds). For

Hi... I have set up my smb.conf to use the print$ directive, and have shared 3 printers. I sucesfully added the printer drivers to the host, and can use them. But - opening up the printer connection from the windows host is slow, and causes the printer 'status' window to say 'initializing'. While that happens, my samba.log shows : 2003/07/29 16:44:40, 2]

Since we've switched to spoolss printing (samba 2.2.4) it seems that the server is always trying to connect to the client. [2002/06/11 10:52:41, 3] lib/util_sock.c:open_socket_out(843) Connecting to 10.0.40.80 at port 445 [2002/06/11 10:52:41, 2] lib/util_sock.c:open_socket_out(871) error connecting to 10.0.40.80:445 (Connection refused) [2002/06/11 10:52:41, 3]

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

hi all, I have been stuffing around with thsi problem for a couple of weeks now, without much success :) I am sure i am missing something simple. I have a Samba server setup as a member server in a 2000 domain. (samba 3.0.10) Samba is printing through CUPS and the printing works fine. when i click on "Printers and Faxes" froma windows xp machine, it takes about 30-60 seconds to show

Hi, I am discovering several error messages from one of our samba servers. Logcheck says: Security Events =-=-=-=-=-=-=-= getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected

Hello, I have set up a samba server 3.1.2. I want to run it as a PDC. Final target is to use it with LDAP and Kerberos. At the moment I use tdbsam as backend. I have authentication problems. Everything is running, I have set the root password, I have created some user account on SAMBA and UNIX. I am lost. I followed the docs (Examples) except for the firewalling and BDC setup (I don't need

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

I am using Apache2.2 + Mongrel on my machine. Now I am accessing it over LAN. When I enter http://mymachinename/myapp it opens fine but when I click on any link in my rails app, it replaces mymachinename with localhost (http://localhost/myapp/controller/action) and thus I am unable to access it from remote location.

Dear list, I?m using samba 3.0.4 on a RHL9 server as domain member in a W2k3 ADS (native) environment. The shares on the Samba server are used by XP clients and these clients get the shares via scripting while they logon on the ADS. In the ADS domain there are several ADS servers (on remote locations, connected via routers) that have the same global catalog. This means that an XP client that

I am using Apache2.2 + Mongrel on my machine. Now I am accessing it over LAN. When I enter http://mymachinename/myapp it opens fine but when I click on any link in my rails app, it replaces mymachinename with localhost (http://localhost/myapp/controller/action) and thus I am unable to access it from remote location. -- Posted via http://www.ruby-forum.com/.

I'm seeing the following error in the logs. It's only from one machine, none of the others generate the error. The basic error is: "connect_to_client: machine KW1 rejected the tconX on the IPC$ share. Error was : NT_STATUS_ACCESS_DENIED." Following is a log excerpt: Jul 22 15:50:56 server smbd[15267]: [2002/07/22 15:50:56, 0]

We have about 300 users distributed on different vlans using private ip network spaces, and sharing one single public IP when going out to the Internet. Our samba (3.0.24) server has a pulbic IP and is running as a primary domain controller. All clients receive Sambas's public IP as their WINS server. I am able to join the domain but samba stops responding sporadically. Looking at the

Perhaps one of you could lend us a hand with this... We are trying to setup an open access print server using RedHat 7.3 and Cups 1.15. We are seeing the following error message on some of the log files related to some Win2K users: [2002/07/18 08:57:35, 0] rpc_client/cli_spoolss_notify.c:spoolss_connect_to_client(133) connect_to_client: machine JLEE rejected the tconX on the IPC$ share. Error

I have encountered a bizarre problem upon moving from Samba 2.2.2 to 2.2.4 on our local print server. When a client tries to map a printer, the server does a DNS lookup on the netbios name of the client, and tries to contact that IP address. This can fail in situations where the client's netbios and DNS names don't match, as in a wireless network user. The failure doesn't prevent

Hello everyone, When anyone of my users prints to a CUPS printer shared on a SAMBA 3 I get the following error in the log of the machine creating the printjob. I am running the following software SAMBA-3.0.1rc2 and CUPS-1.1.17-13 with the following config: [global] ....... printing = cups ..... [printers] comment = All Printers path = /var/spool/samba printer admin =

net join -d 2 -S pnicg-pdc -U Administrator [2004/02/18 20:27:03, 0] param/loadparm.c:map_parameter(2410) Unknown parameter encountered: "domain admin group" [2004/02/18 20:27:03, 0] param/loadparm.c:lp_do_parameter(3048) Ignoring unknown parameter "domain admin group" [2004/02/18 20:27:03, 2] lib/interface.c:add_interface(79) added interface ip=172.16.24.137

Howdy! the setup: RH-VALE 6.2.4 running samba2.2.2 cvs from 11/24/2001... user running NT 4.0 SP6a the problem: I have a user that cannot print - She can add the printer but can't print. log for that machine shows the following: ... normal looking connections to obtain drivers - all look OK - no complaints.. .. then this - libsmb/namequery.c:name_query(415) Got a positive name query

Hello Everyone, I recently upgraded from ver 2.0.7 to 3.0.5. Some of Xp clients had problems with connecting to Unix drives and printing. The following are the error messages, "lib/substitute.c:alloc_sub_basic(505) alloc_sub_basic: NULL source string! This should not happen" " libsmb/cliconnect.c:attempt_netbios_session_request(1543) attempt_netbios_session_request: