Hi again,

the packets in question:


91 17:16:13.40669 zitpcx6767.desy.de -> printsrv9.desy.de ETHER Type=0800 (IP), 
size = 360 bytes
 91 17:16:13.40669 zitpcx6767.desy.de -> printsrv9.desy.de IP  D=131.169.56.109 
S=131.169.194.172 LEN=346, ID=36008, TOS=0x0, TTL=127
 91 17:16:13.40669 zitpcx6767.desy.de -> printsrv9.desy.de TCP D=139 S=4390 
Push Ack=2546665685 Seq=1818884627 Len=306 Win=64725
 91 17:16:13.40669 zitpcx6767.desy.de -> printsrv9.desy.de NBT Type=SESSION 
MESSAGE Length=302
 91 17:16:13.40669 zitpcx6767.desy.de -> printsrv9.desy.de SMB C Code=0x25 
Name=SMBtrans Error=0
________________________________
 92 17:16:13.46879 printsrv9.desy.de -> zitpcx6767.desy.de ETHER Type=0800 
(IP), size = 54 bytes
 92 17:16:13.46879 printsrv9.desy.de -> zitpcx6767.desy.de IP  
D=131.169.194.172 S=131.169.56.109 LEN=40, ID=48233, TOS=0x0, TTL=64
 92 17:16:13.46879 printsrv9.desy.de -> zitpcx6767.desy.de TCP D=4390 S=139 
Ack=1818884933 Seq=2546665685 Len=0 Win=49680
 92 17:16:13.46879 printsrv9.desy.de -> zitpcx6767.desy.de NBT R port=4390
________________________________
 93 17:16:17.73338 printsrv9.desy.de -> zitpcx6767.desy.de ETHER Type=0800 
(IP), size = 162 bytes
 93 17:16:17.73338 printsrv9.desy.de -> zitpcx6767.desy.de IP  
D=131.169.194.172 S=131.169.56.109 LEN=148, ID=48234, TOS=0x0, TTL=64
 93 17:16:17.73338 printsrv9.desy.de -> zitpcx6767.desy.de TCP D=4390 S=139 
Push Ack=1818884933 Seq=2546665685 Len=108 Win=49680
 93 17:16:17.73338 printsrv9.desy.de -> zitpcx6767.desy.de NBT Type=SESSION 
MESSAGE Length=104
 93 17:16:17.73338 printsrv9.desy.de -> zitpcx6767.desy.de SMB R Code=0x25 
Name=SMBtrans Error=0
________________________________
 94 17:16:17.73402 zitpcx6767.desy.de -> printsrv9.desy.de ETHER Type=0800 
(IP), size = 222 bytes
 94 17:16:17.73402 zitpcx6767.desy.de -> printsrv9.desy.de IP  D=131.169.56.109 
S=131.169.194.172 LEN=208, ID=36010, TOS=0x0, TTL=127
 94 17:16:17.73402 zitpcx6767.desy.de -> printsrv9.desy.de TCP D=139 S=4390 
Push Ack=2546665793 Seq=1818884933 Len=168 Win=64617
 94 17:16:17.73402 zitpcx6767.desy.de -> printsrv9.desy.de NBT Type=SESSION 
MESSAGE Length=164
 94 17:16:17.73402 zitpcx6767.desy.de -> printsrv9.desy.de SMB C Code=0x25 
Name=SMBtrans Error=0

cheers
christoph




On Sun, 21 Feb 2010, christoph.be...@desy.de wrote:

Hi,

just had a look at a network trace, ther seems to be a ~ 4 sec. delay between a 'OpenPrinterEx' call and the 'OpenPrinterEx response' this seems to cause some of the delas I see is anyone aware of how to fix this ?

cheers
christoph



On Sun, 21 Feb 2010, christoph.be...@desy.de wrote:


 here is my testparm output:
 [global]
          workgroup = WIN
          realm = WIN.DESY.DE
          netbios name = ADPRINT
          server string = PRINTSERVER for WIN.DESY.DE (SAMBA 3.3.10)
          security = ADS
          map to guest = Bad User
          password server = <ip of my password server>
          username map = /global/spool/etc/smbusers.map
          log file = /global/spool/samba_logs/%m.printsrv9.smblog
          smb ports = 139
          name resolve order = wins lmhosts hosts bcast
          deadtime = 60
          printcap cache time = 600
          printcap name = /global/spool/etc/printcap.smb
          enumports command = /usr/bin/echo samba_port
          preferred master = Yes
          dns proxy = No
          wins server = <ip of my wins server>
          admin users = lp
          guest ok = Yes
          printing = lprng
          print command = /global/spool/lprng/bin/lpr -r -Fl -J"%J" -m"%m"
 -U"%U" -...@spool-lpr %s
          lpq command = /global/spool/lprng/bin/lpq -...@spool-lpr
          lprm command = /global/spool/lprng/bin/lprm -U%U -P%p %j
          lppause command = lpc hold '%p' %j
          lpresume command = lpc release '%p' %j
          queuepause command = lpc stop '%p'
          queueresume command = lpc start '%p'


 ???

 cheers
 christoph



 On Sun, 21 Feb 2010, christoph.be...@desy.de wrote:

>    Hi again,
> > I changed from 3.4.5 to 3.3.10 after an AD upgrade to 2008R2 and > prinitng
>    is
>    working mor ore less but it is incredibly sloooow. My server has no
> remarkable load so it is not due to hardware bottlenecks. Are there > any
>    ways
>    to 'tune' 3.3.10 or any tricks to make it faster ?
> > cheers
> ~    christoph
> > > --
>    /*   Christoph Beyer     |   Office: Building 2b / 23     *\
>     *   DESY                |    Phone: 040-8998-2317        *
>     *   - IT -              |      Fax: 040-8998-4060        *
>    \*   22603 Hamburg       |     http://www.desy.de         */
> > > --
>    To unsubscribe from this list go to the following URL and read the
>    instructions:  https://lists.samba.org/mailman/options/samba
>
 best regards
~   christoph


 --
 /*   Christoph Beyer     |   Office: Building 2b / 23     *\
   *   DESY                |    Phone: 040-8998-2317        *
   *   - IT -              |      Fax: 040-8998-4060        *
 \*   22603 Hamburg       |     http://www.desy.de         */



 --
 To unsubscribe from this list go to the following URL and read the
 instructions:  https://lists.samba.org/mailman/options/samba


best regards
        ~ christoph


--
/*   Christoph Beyer     |   Office: Building 2b / 23     *\
 *   DESY                |    Phone: 040-8998-2317        *
 *   - IT -              |      Fax: 040-8998-4060        *
\*   22603 Hamburg       |     http://www.desy.de         */


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba



best regards
        ~christoph


--
/*   Christoph Beyer     |   Office: Building 2b / 23     *\
 *   DESY                |    Phone: 040-8998-2317        *
 *   - IT -              |      Fax: 040-8998-4060        *
\*   22603 Hamburg       |     http://www.desy.de         */


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Reply via email to