From lepera@us.ibm.com Tue Oct 10 15:30:16 2006 Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by underdog.stansell.org (8.13.8/8.13.8) with ESMTP id k9AMU86w022048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 10 Oct 2006 15:30:14 -0700 (PDT) Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.13.8/8.12.11) with ESMTP id k9AMU77w016047 for ; Tue, 10 Oct 2006 18:30:07 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k9AMU3b1268544 for ; Tue, 10 Oct 2006 18:30:06 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k9AMU3Qv009962 for ; Tue, 10 Oct 2006 18:30:03 -0400 Received: from d01mll96.pok.ibm.com (zvmnotes02.pok.ibm.com [9.56.225.15]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k9AMU3gW009954 for ; Tue, 10 Oct 2006 18:30:03 -0400 Subject: conserver.cf question To: users@conserver.com X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 Message-ID: From: William P LePera Date: Tue, 10 Oct 2006 18:30:02 -0400 X-MIMETrack: Serialize by Router on D01MLL96/01/M/IBM(Release 7.0.1FP1 | May 25, 2006) at 10/10/2006 18:30:02 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=0ABBF890DFEB757C8f9e8a93df938690918c0ABBF890DFEB757C" Content-Disposition: inline X-Spam-Score: -0.924 () BAYES_00,HTML_10_20,HTML_MESSAGE X-Scanned-By: MIMEDefang 2.57 on 209.182.219.30 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.8 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 22:30:17 -0000 --0__=0ABBF890DFEB757C8f9e8a93df938690918c0ABBF890DFEB757C Content-type: text/plain; charset=US-ASCII We are running conserver version 8.1.7, using the UDS socket feature for client/server communications. We recently modified our conserver configuration files to call our terminal server directly using the "type host" syntax. An example configuration entry looks like this: default csm { logfile /var/log/consoles/&; timestamp 1da; rw *; master c104hc01.clusters.com; } console f1x345n01.clusters.com { include csm; type host; host 192.168.1.25; port 2900; } Whenever we open a console to this server, the console opens in read-only mode, even if we don't specify -s: [root@c104hc01 conserver]# /opt/conserver/bin/console f1x345n01.clusters.com [Enter `^Ec?' for help] [read-only -- initializing] hitting some keystrokes here results in: [read-only -- use ^E c ? for help] [read-only -- use ^E c ? for help] [read-only -- use ^E c ? for help] [read-only -- use ^E c ? for help] We can use the Ctrl E-c-f sequence to get into read/write mode: [attached] Red Hat Enterprise Linux AS release 4 (Nahant) Kernel 2.6.9-5.ELsmp on an i686 f1x345n01.clusters.com login: If we change the configuration file back to this: default csm { logfile /var/log/consoles/&; timestamp 1da; rw *; master c104hc01.clusters.com; } console f1x345n01.clusters.com { include csm; type exec; exec "/usr/kerberos/bin/telnet 192.168.1.25 2900"; } everything works: [root@c104hc01 conserver]# /opt/conserver/bin/console f1x345n01.clusters.com [Enter `^Ec?' for help] Trying 192.168.1.25... Connected to c104v1mrv01.clusters.com (192.168.1.25). Escape character is '^]'. Red Hat Enterprise Linux AS release 4 (Nahant) Kernel 2.6.9-5.ELsmp on an i686 f1x345n01.clusters.com login: Is there anything else that needs to be added to the config file to get the console opened in read/write mode? I would have thought the "rw *" in the default block would be enough. Thanks, ___________________________________________________________________ Bill LePera IBM Systems and Technology Group Poughkeepsie, NY --0__=0ABBF890DFEB757C8f9e8a93df938690918c0ABBF890DFEB757C Content-type: text/html; charset=US-ASCII Content-Disposition: inline

We are running conserver version 8.1.7, using the UDS socket feature for client/server communications. We recently modified our conserver configuration files to call our terminal server directly using the "type host" syntax.

An example configuration entry looks like this:

default csm {
logfile /var/log/consoles/&;
timestamp 1da;
rw *;
master c104hc01.clusters.com;
}

console f1x345n01.clusters.com {
include csm;
type host;
host 192.168.1.25;
port 2900;
}

Whenever we open a console to this server, the console opens in read-only mode, even if we don't specify -s:

[root@c104hc01 conserver]# /opt/conserver/bin/console f1x345n01.clusters.com
[Enter `^Ec?' for help]
[read-only -- initializing]

hitting some keystrokes here results in:

[read-only -- use ^E c ? for help]
[read-only -- use ^E c ? for help]
[read-only -- use ^E c ? for help]
[read-only -- use ^E c ? for help]

We can use the Ctrl E-c-f sequence to get into read/write mode:

[attached]

Red Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.9-5.ELsmp on an i686

f1x345n01.clusters.com login:

If we change the configuration file back to this:

default csm {
logfile /var/log/consoles/&;
timestamp 1da;
rw *;
master c104hc01.clusters.com;
}

console f1x345n01.clusters.com {
include csm;
type exec;
exec "/usr/kerberos/bin/telnet 192.168.1.25 2900";
}

everything works:

[root@c104hc01 conserver]# /opt/conserver/bin/console f1x345n01.clusters.com
[Enter `^Ec?' for help]
Trying 192.168.1.25...
Connected to c104v1mrv01.clusters.com (192.168.1.25).
Escape character is '^]'.

Red Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.9-5.ELsmp on an i686

f1x345n01.clusters.com login:


Is there anything else that needs to be added to the config file to get the console opened in read/write mode? I would have thought the "rw *" in the default block would be enough.

Thanks,
___________________________________________________________________
Bill LePera
IBM Systems and Technology Group
Poughkeepsie, NY --0__=0ABBF890DFEB757C8f9e8a93df938690918c0ABBF890DFEB757C-- From david.k.harris@siemens.com Tue Oct 10 15:52:33 2006 Received: from usnwk224srv.usa.siemens.com (usnwksmtp04e.usa.siemens.com [12.46.135.35]) by underdog.stansell.org (8.13.8/8.13.8) with ESMTP id k9AMqNo4022244 for ; Tue, 10 Oct 2006 15:52:30 -0700 (PDT) Received: from usnwk206a.ww017.siemens.net ([155.45.111.74]) by 172.16.1.38 with trend_isnt_name_B; Tue, 10 Oct 2006 15:52:03 -0700 Received: from USNWK102MSX.ww017.siemens.net ([155.45.111.56]) by usnwk206a.ww017.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 15:52:14 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6ECBE.B9FE409E" Subject: RE: conserver.cf question (portbase, port...) Date: Tue, 10 Oct 2006 15:52:13 -0700 Message-ID: <2461A50AD2345646B1C4B3D7BA40B8E28B05C8@USNWK102MSX.ww017.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: conserver.cf question (portbase, port...) Thread-Index: AcbsvGljJsxb8lIDT9msRi852U5pRQAAJ8Gg From: "Harris, David \(SBS US\)" To: "William P LePera" X-OriginalArrivalTime: 10 Oct 2006 22:52:14.0062 (UTC) FILETIME=[BA5398E0:01C6ECBE] X-Spam-Score: -2.311 () BAYES_00,HTML_MESSAGE X-Scanned-By: MIMEDefang 2.57 on 209.182.219.30 Cc: users@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.8 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 22:52:34 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C6ECBE.B9FE409E Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hi William, =20 The one difference I see from my standard configs, is that I call out=20 the "portbase" and "portinc" variables for each brand of [terminal|console]=20 server, as in the following example... =20 default cyclades { type host; portbase 2000; portinc 1; } =20 This way, my "port" variable for each device represents the hardware port number, so it's a bit more intuitive which port to which you are=20 connecting each console... =20 console daphne { include ts21 ; port 12 ; } =20 While this seems pretty self-evident for most console servers, there are a few cases where the port increment is x100, versus x1, and there are a few devices where the starting port base is 'unusual', depending on which slot you use for the NM-xA or HWIC-xA modules. That's where this method really shines, helping to document where you=20 plugged in the cables. :-) =20 Perhaps having just the port called, without a defined portbase or portinc variable is the cause? Seems like an interesting symptom. :-) =20 -Z- =20 ________________________________ From: users-bounces@conserver.com [mailto:users-bounces@conserver.com] On Behalf Of William P LePera Sent: Tuesday, October 10, 2006 3:30 PM To: users@conserver.com Subject: conserver.cf question We are running conserver version 8.1.7, using the UDS socket feature for client/server communications. We recently modified our conserver configuration files to call our terminal server directly using the "type host" syntax.=20 An example configuration entry looks like this: default csm { logfile /var/log/consoles/&; timestamp 1da; rw *; master c104hc01.clusters.com; } console f1x345n01.clusters.com { include csm; type host; host 192.168.1.25; port 2900; } Whenever we open a console to this server, the console opens in read-only mode, even if we don't specify -s: [root@c104hc01 conserver]# /opt/conserver/bin/console f1x345n01.clusters.com [Enter `^Ec?' for help] [read-only -- initializing] hitting some keystrokes here results in: [read-only -- use ^E c ? for help] [read-only -- use ^E c ? for help] [read-only -- use ^E c ? for help] [read-only -- use ^E c ? for help] We can use the Ctrl E-c-f sequence to get into read/write mode: [attached] Red Hat Enterprise Linux AS release 4 (Nahant) Kernel 2.6.9-5.ELsmp on an i686 f1x345n01.clusters.com login:=20 If we change the configuration file back to this: default csm { logfile /var/log/consoles/&; timestamp 1da; rw *; master c104hc01.clusters.com; } console f1x345n01.clusters.com { include csm; type exec; exec "/usr/kerberos/bin/telnet 192.168.1.25 2900"; } everything works: [root@c104hc01 conserver]# /opt/conserver/bin/console f1x345n01.clusters.com [Enter `^Ec?' for help] Trying 192.168.1.25... Connected to c104v1mrv01.clusters.com (192.168.1.25). Escape character is '^]'. Red Hat Enterprise Linux AS release 4 (Nahant) Kernel 2.6.9-5.ELsmp on an i686 f1x345n01.clusters.com login:=20 Is there anything else that needs to be added to the config file to get the console opened in read/write mode? I would have thought the "rw *" in the default block would be enough. Thanks, ___________________________________________________________________ Bill LePera IBM Systems and Technology Group Poughkeepsie, NY ------_=_NextPart_001_01C6ECBE.B9FE409E Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

  Hi William,
 
  The one difference I see from my = standard=20 configs, is that I call out
the "portbase" and "portinc" variables for = each brand=20 of [terminal|console]
server, as in the following=20 example...
 
  default cyclades { type host; portbase = 2000;=20 portinc 1; }
 
  This way, my "port" variable for each = device=20 represents the hardware
port number, so it's a bit more intuitive = which port to=20 which you are
connecting each = console...
 
  console daphne { include ts21 ; port = 12 ;=20 }
 
  While this seems pretty self-evident = for most=20 console servers, there
are a few cases where the port increment is = x100,=20 versus x1, and there
are a few devices where the starting port = base is=20 'unusual', depending
on which slot you use for the NM-xA or = HWIC-xA modules.=20 That's
where this method really shines, helping to = document=20 where you
plugged in the cables. = :-)
 
  Perhaps having just the port called, = without a=20 defined portbase or
portinc variable is the cause? Seems like an=20 interesting symptom. :-)
 
       =20 -Z-
 
From: users-bounces@conserver.com=20 [mailto:users-bounces@conserver.com] On Behalf Of William P=20 LePera
Sent: Tuesday, October 10, 2006 3:30 PM
To:=20 users@conserver.com
Subject: conserver.cf=20 question

We are running conserver version 8.1.7, using the UDS socket feature = for=20 client/server communications. We recently modified our conserver = configuration=20 files to call our terminal server directly using the "type host" syntax. =

An example configuration entry looks like this:

default = csm=20 {
logfile /var/log/consoles/&;
timestamp 1da;
rw = *;
master=20 c104hc01.clusters.com;
}

console f1x345n01.clusters.com = {
include=20 csm;
type host;
host 192.168.1.25;
port = 2900;
}

Whenever we=20 open a console to this server, the console opens in read-only mode, even = if we=20 don't specify -s:

[root@c104hc01 conserver]# = /opt/conserver/bin/console=20 f1x345n01.clusters.com
[Enter `^Ec?' for help]
[read-only --=20 initializing]

hitting some keystrokes here results = in:

[read-only=20 -- use ^E c ? for help]
[read-only -- use ^E c ? for = help]
[read-only --=20 use ^E c ? for help]
[read-only -- use ^E c ? for help]

We can = use the=20 Ctrl E-c-f sequence to get into read/write = mode:

[attached]

Red=20 Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.9-5.ELsmp on an = i686

f1x345n01.clusters.com login:

If we change the = configuration=20 file back to this:

default csm {
logfile=20 /var/log/consoles/&;
timestamp 1da;
rw *;
master=20 c104hc01.clusters.com;
}

console f1x345n01.clusters.com = {
include=20 csm;
type exec;
exec "/usr/kerberos/bin/telnet 192.168.1.25=20 2900";
}

everything works:

[root@c104hc01 conserver]#=20 /opt/conserver/bin/console f1x345n01.clusters.com
[Enter `^Ec?' for=20 help]
Trying 192.168.1.25...
Connected to c104v1mrv01.clusters.com = (192.168.1.25).
Escape character is '^]'.

Red Hat Enterprise = Linux AS=20 release 4 (Nahant)
Kernel 2.6.9-5.ELsmp on an=20 i686

f1x345n01.clusters.com login:


Is there anything = else=20 that needs to be added to the config file to get the console opened in=20 read/write mode? I would have thought the "rw *" in the default block = would be=20 enough.

Thanks,
_______________________________________________= ____________________
Bill=20 LePera
IBM Systems and Technology Group
Poughkeepsie, = NY

------_=_NextPart_001_01C6ECBE.B9FE409E-- From bryan@stansell.org Fri Oct 13 09:42:43 2006 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.13.8/8.13.8) with ESMTP id k9DGgh9F007152 for ; Fri, 13 Oct 2006 09:42:43 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.13.8/8.13.8/Submit) id k9DGghiS007151 for users@conserver.com; Fri, 13 Oct 2006 09:42:43 -0700 (PDT) Date: Fri, 13 Oct 2006 09:42:43 -0700 From: Bryan Stansell To: users@conserver.com Subject: Re: conserver.cf question Message-ID: <20061013164243.GD3435@underdog.stansell.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.57 on 209.182.219.30 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.8 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 16:42:44 -0000 On Tue, Oct 10, 2006 at 06:30:02PM -0400, William P LePera wrote: > [root@c104hc01 conserver]# /opt/conserver/bin/console > f1x345n01.clusters.com > [Enter `^Ec?' for help] > [read-only -- initializing] the 'initializing' says that conserver is still busy trying to bring up the console. if there is some 'initcmd' stuff buried in the config (somehow) that's firing, that could explain it. if not, then perhaps the socket connection isn't being accepted immediately. the config snippet you sent showed you used a kerberos telnet client before - if you use a standard telnet client, do you get a delay? i kinda doubt it, but i figured i'd ask anyway. you shouldn't be in the 'initializing' state once the socket connection is made unless you have some 'initcmd' stuff going. and it could be a bug in 8.1.7 that has hopefully been fixed...there has been quite a bit between .7 and .14. and i think newer versions will pop you into read-write mode once the initialization is complete...so you at least know it's ready. at least, i think i remember working on that at some point... > Is there anything else that needs to be added to the config file to get the > console opened in read/write mode? I would have thought the "rw *" in the > default block would be enough. yep...that's all...it really is just conserver thinking the console isn't ready to be used yet. hopefully you can drop in 8.1.14 for a quick test to see what happens...if it still doesn't initialize the consoles properly, i'd love to know. i'd then love to see debug output, maybe a trace, etc... Bryan From hf@spg.tu-darmstadt.de Mon Oct 23 02:20:43 2006 Received: from bounce.nt.e-technik.tu-darmstadt.de (bounce.nt.e-technik.tu-darmstadt.de [130.83.197.1]) by underdog.stansell.org (8.13.8/8.13.8) with ESMTP id k9N9KZVn019514 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 23 Oct 2006 02:20:42 -0700 (PDT) Received: from [130.83.118.66] (Dachstein.nt.e-technik.tu-darmstadt.de [130.83.118.66]) by bounce.nt.e-technik.tu-darmstadt.de (8.13.5.20060614/8.13.3) with ESMTP id k9N9KU7m017065 for ; Mon, 23 Oct 2006 11:20:32 +0200 (CEST) Mime-Version: 1.0 Message-Id: Date: Mon, 23 Oct 2006 11:20:29 +0200 To: users@conserver.com From: Hauke Fath Subject: unix domain socket permissions Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: 8bit X-Spam-Score: -1.11 () BAYES_05 X-Scanned-By: MIMEDefang 2.57 on 209.182.219.30 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.8 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 09:20:44 -0000 Hi list, when I run Conserver with unix domain sockets (configured with --with-uds), the server daemon creates sockets under /tmp/conserver with umask 022. As a result, you have to either be root to use console(1), or manually fix socket permissions until the next restart of conserver(8). Is there any way of setting the permissions on the socket persistently? hauke -- /~\ The ASCII Ribbon Campaign Hauke Fath \ / No HTML/RTF in email Institut für Nachrichtentechnik X No Word docs in email TU Darmstadt / \ Respect for open standards Ruf +49-6151-16-3281 From rip@s93065935.onlinehome.us Wed Oct 25 11:20:58 2006 Received: from mout.perfora.net (mout.perfora.net [217.160.230.41]) by underdog.stansell.org (8.13.8/8.13.8) with ESMTP id k9PIKm1i000980 for ; Wed, 25 Oct 2006 11:20:57 -0700 (PDT) Received: from [217.160.229.2] (helo=pustefix130.perfora.net) by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis), id 0MKoyl-1GcnMs0OUr-0004VQ; Wed, 25 Oct 2006 14:20:47 -0400 Message-Id: <1549134.1720911161800446016.JavaMail.servlet@perfora> From: rip@s93065935.onlinehome.us To: Subject: One Way Communication Only MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 X-Binford: 6100 (more power) X-Mailer: Webmail X-Originating-From: 28397270 X-Routing: US X-Message-Id: <28397270$1161800446015172.19.56.72981120@pustefix130.perfora.net-20616472> X-Received: from pustefix130.perfora.net by 66.63.140.98 with HTTP id 28397270 for [users@conserver.com]; Wed, 25 Oct 2006 14:20:46 EDT Date: Wed, 25 Oct 2006 14:20:46 -0400 X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.57 on 209.182.219.30 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.8 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2006 18:20:59 -0000 Hello all- I have conserver running on a SUSE box, ttyS0 and S1. I can telnet to the ports and call the serial ports, everything is great. The problem is, I can only send out going serial traffic (ie, from the conserver/telnet session to ttyS0 to a PC running hyperterm as a test. Traffic back to the Conserver box is not relayed out via telnet. I've tried multiple cables on multiple ports on multiple machines. Even fired up some protocol analyzers to watch whats happening. The traffic is good and sent, both ways, so it looks like it's on the conserver side. The conserver ports brings cts/dsr/cd high, the other macine brings rts/dtr up, so everything serial was in ready to go. I have have played with multiple configs enabling and disabling hardware/software controls, etc. Nothing changes. This is driving me nutty, basically because I know it's likely that I'm missing a very basic bit of information. Probably related, but I'm not sure how: Conserver refulses all connection involked via console. Conserver is not asking for authentication (just login root and call, no password prompt) Suse 9.1 Pro (2.6.4) A tad old, but was handy. Tured off every form of firewalls, etc. protection I can think of. ports are configed super simply at 9600 8N1. passwd is simple username:*passwd* .cf is uber basic (and reflects tinkering with xon/off/cts/rts, tried many variations): efault * { logfile /var/consoles/&.log; timestamp 1hab; rw *; master localhost; baud 9600; parity none; options !ixon, !ixoff, crtscts; host unused; } console s1 { type device; device /dev/ttyS0; } console s2 { type device; device /dev/ttyS1; } access * { trusted 127.0.0.1; allowed 0.0.0.0/0; } Thanks in advance. Been crusing googe/archives for days looking for an answer as I hate to ask something that a simple fix for the informed. I'm at that point where I need to walk away from it and come back. :P From phantom.iv@gmail.com Fri Oct 27 03:32:57 2006 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by underdog.stansell.org (8.13.8/8.13.8) with ESMTP id k9RAWoJ3000861 for ; Fri, 27 Oct 2006 03:32:56 -0700 (PDT) Received: by nf-out-0910.google.com with SMTP id l36so1260115nfa for ; Fri, 27 Oct 2006 03:32:49 -0700 (PDT) Received: by 10.48.254.10 with SMTP id b10mr603585nfi; Fri, 27 Oct 2006 03:32:49 -0700 (PDT) Received: by 10.49.56.15 with HTTP; Fri, 27 Oct 2006 03:32:49 -0700 (PDT) Message-ID: Date: Fri, 27 Oct 2006 11:32:49 +0100 From: "Luc Hands" To: users@conserver.com Subject: Can't connect MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.57 on 209.182.219.30 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.8 Precedence: list Reply-To: luc@handsfamily.org.uk List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 10:33:02 -0000 Hi, I've tried setting up conserver with a basic config. What I wan't to do is telnet into the console sever and be connected to a remote telnet connection. At the moment my conserver.cf reads, console testconf { master localhost; type host; rw *; host 10.2.138.66; port 2005; } I then run conserver -p782 So I should be able to do 'telnet localhost 782', except I keep getting 'Connection refused' Any ideas why? Thanks in advance, Luc