Home / user-6108

slovon's questions

Martin Hope
slovon
Asked: 2010-01-15 00:57:21 +0800 CST
  • 2

I don't find anything suitable on this topic: we have a Solaris server, running CSW CUPS and several network printers. Printing using LPD is fast, but when we try socket or SMB, it is painfully slow (<1 sec vs. 30 seconds for a small job).

We avoided this by using LPD up until now when there is a printserver that only supports socket and SMB. The customer declines to replace the unit (please don't ask - we tried everything).

And on the other hand why would socket be slower than LPD?? Has anyone any ideas what to look for/into?

Many thanks!

printing cups solaris socket
Martin Hope
slovon
Asked: 2009-09-01 02:36:09 +0800 CST
  • 2

A customer of ours is setting up an ISA-Cluster in private network address range and we have to build a VPN connection with them. There is no way avoiding NAT-T and this is where we get to a problem:

in IKE request there is a field ENCAPSULATION_MODE where there should be a value of 3 for NAT-T if you go by the book (RFC3947).

However Ciscos and it seems Microsoft ISA still send historical value of 61443 which is accepted by OpenBSD (tolerant, good). But - there is no way to make OpenBSD send a request with ENCAPSULATION_MODE = 61443 and the "standard" value 3 is rejected by Microsoft ISA.

Anybody knows a solution to this?

It'd be nice to hear of a patch for MS ISA allowing it to accept the "3"...

Update: "The other side" has MS ISA 2006 Enterprise. "Our side" has OpenBSD 4.5.

vpn isa-server cisco-vpn openbsd
Martin Hope
slovon
Asked: 2009-06-23 06:21:26 +0800 CST
  • 1

Does anyone have an idea on why I see PROCESSED messages here: 

select 'MFS_MISSION' as queue_name, CONSUMER_NAME, MSG_STATE, count(*) from aq$MFS_MISSION_QTAB  group by consumer_name, MSG_STATE

 QUEUE_NAME     CONSUMER_NAME     MSG_STATE     COUNT(*)    
 -------------  ----------------  ------------  ----------- 
 MFS_MISSION    T1                PROCESSED     143216      
 MFS_MISSION    S1                PROCESSED     377208

but not here:

select dq.queue_table, dq.queue_type, dq.name, v$aq.waiting, V$AQ.ready, V$AQ.expired, V$AQ.total_wait, V$AQ.average_wait 
from V$AQ, dba_queues dq where dq.qid=v$aq.qid and dq.name like '%MISSION%'

 QUEUE_TABLE       QUEUE_TYPE       NAME                    WAITING     READY     EXPIRED     TOTAL_WAIT     AVERAGE_WAIT    
 ----------------  ---------------  ----------------------  ----------  --------  ----------  -------------  --------------- 
 MFS_MISSION_QTAB  EXCEPTION_QUEUE  AQ$_MFS_MISSION_QTAB_E  0           0         0           0              0               
 MFS_MISSION_QTAB  NORMAL_QUEUE     MFS_MISSION_QUEUE       0           539002    0           0              0               
 MFS_MISSION_QTAB  EXCEPTION_QUEUE  AQ$_MFS_MISSION_QTAB_E  0           0         0           0              0               
 MFS_MISSION_QTAB  NORMAL_QUEUE     MFS_MISSION_QUEUE       0           480333    0           0              0

The queue has retention of 0, so messages should either be PROCESSED or disappear altogether as soon as they are committed. The count of messages tells me they have accumulated over course of months.

I'll be glad for any pointers, esperience or insights.

Edit: Oracle Database 10g Release 10.2.0.3.0

oracle