Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread Unsolicited connection attempts
Fri, Jul 25 2008 9:47 AMPermanent Link

Paul Endersby
The product that I currently work on has it's own tailored DBISAM server developed using the DBISAM Server components.

My client wants to be able to log unsolicited calls to the DB Server port. This is to include the anyone-can-get DBISAM Database System Utility
connecting to the server as well as someone trying their luck with something like telnet.

I see from debugging my server that I get a TDBISAMEngine.ServerLogEvent firing whenever I try and use the Database System Utility so that is
easily logged. However I get no such event firing when I try to telnet onto the DB Server port.

Question can I hook up to an event on the TDISAMEngine or other component to enable me to code for this specific event ?

Thanks.
Fri, Jul 25 2008 9:48 AMPermanent Link

Paul Endersby
Apologies,

this is with DBISAM Version 4
Fri, Jul 25 2008 2:29 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Paul,

<< I see from debugging my server that I get a TDBISAMEngine.ServerLogEvent
firing whenever I try and use the Database System Utility so that is easily
logged. However I get no such event firing when I try to telnet onto the DB
Server port.

Question can I hook up to an event on the TDISAMEngine or other component
to enable me to code for this specific event ? >>

You can use the TDBISAMEngine.OnServerLogEvent event to do so.  Just look
for any log records coming through with "Connection rejected" in their Text.

from dbisamtb.pas

  TServerLogEvent = procedure(Sender: TObject; LogRecord: TLogRecord) of
object;

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jul 28 2008 7:00 AMPermanent Link

Paul Endersby
I'm already hooking up that event.

If I run up my server and put a breakpoint on the the first line ServerLogEvent then I see a connection attempt being made from the Database
System Utility.

If I try to connect to either port 12005 (ServerMainPort) or 12006 (ServerAdminPort) with telnet then I get no activity upon connect. However.
when the telnet session finishes I get a disconnect event showing in the ServerLogEvent handler.

The TDBISAMEngine is reporting an engine version of 4.10 if that's any help.

Cheers,

Paul.
Mon, Jul 28 2008 7:09 AMPermanent Link

Paul Endersby
Addendum.

I have tried this on the latest (I assume) build 4.25 build 7 and get the same behaviour.
Mon, Jul 28 2008 3:44 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Paul,

<< If I try to connect to either port 12005 (ServerMainPort) or 12006
(ServerAdminPort) with telnet then I get no activity upon connect. However.
when the telnet session finishes I get a disconnect event showing in the
ServerLogEvent handler. >>

Sorry, I assumed that you were actually trying to type something in via
telnet.  If you don't type anything, then DBISAM will simply disconnect the
connection after the session timeout setting on the server is reached.  You
can modify this value via the Server Administration Utility, or via remotely
via this method:

http://www.elevatesoft.com/manual?action=mancompmethod&id=dbisam4&product=d&version=7&comp=TDBISAMSession&method=ModifyRemoteConfig

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Jul 29 2008 6:14 AMPermanent Link

Paul Endersby
Tim,

Thanks for your reply. Sorry to keep banging on about this, but when I attempted to connect to our home brew DBISAM database server using a
telnet session, although I managed a persistent connection (i.e. didn't immediately kick me) as soon as I tried to type anything into the telnet
window (windows XP telnet) I got immediately kicked and a ServerLogEvent told me the session had ended.

Is this the behavior that you would expect (i.e. unable to type anything into the telnet session without being immediately disconnected) ?

Regards,

Paul.
Tue, Jul 29 2008 8:12 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Paul,

<< Thanks for your reply. Sorry to keep banging on about this, but when I
attempted to connect to our home brew DBISAM database server using a telnet
session, although I managed a persistent connection (i.e. didn't immediately
kick me) as soon as I tried to type anything into the telnet window (windows
XP telnet) I got immediately kicked and a ServerLogEvent told me the session
had ended.

Is this the behavior that you would expect (i.e. unable to type anything
into the telnet session without being immediately disconnected) ? >>

Yes, absolutely.  As soon as the database server detects that the incoming
connection request is invalid, it gives it the boot.  Because telnet
transmits in a character-by-character fashion, the database server will
detect the invalid connection as soon as you type the first character.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image