Back to product page
- Introduction
- License agreement
- Getting Started
- Enumerations
- Objects
- wodTelnetDLX
- Methods
- Properties
- Authentication
- AutoSize
- BackColor
- BackLog
- BindIP
- BindPort
- Blocking
- BorderVisible
- Certificate
- CharEncoding
- Column
- Columns
- ColWidth
- Command
- ContextMenu
- CursorHeight
- DataOut
- DataReady
- Enabled
- ErrorText
- ExitSignal
- ExitStatus
- Font
- ForeColor
- HandleSysKeys
- Hostname
- hWnd
- KeepAlives
- Language
- LastError
- LocalCertBag
- Login
- MousePointer
- MouseWheel
- MyHostname
- MyIP
- Notification
- Password
- Picture
- Port
- Prompt
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RecordMode
- RemoteIdentification
- Row
- RowHeight
- Rows
- ScrollBars
- ScrollX
- ScrollY
- SecureMethod
- SelectedText
- ShowCursor
- Socket
- SpecialKeyFocus
- State
- StateText
- StripANSI
- StripColors
- TabStop
- TelnetOption
- TerminalEmulation
- TerminalType
- Text
- Timeout
- TranslateSpecial
- UseIPv6
- Version
- Events
- IwodTelnetNotify
- wodTelnetDLX
- How to get support?
- Technical information
- Fast notifications interface
- Error list
Connected event
Fires when wodTelnetDLX connects to remote server.
Syntax
- Basic
Private Sub object_Connected (ByVal ErrorCode, ByVal ErrorText)
The Connected(ErrorCode,ErrorText) syntax has these parts:
The Connected(ErrorCode,ErrorText) syntax has these parts:
ErrorCode | An Integer value. Error that occurred, if any. |
ErrorText | A String value. Text description of the error, if any. |
Remarks
Connected event will be fired always after Connect method is issued. If wodTelnetDLX successfully connected to server, ErrorCode will be set to 0, and you can start sending/receiving data from server. If ErrorCode is different than 0, then wodTelnetDLX will immediatelly close the connection.For SSH and SSL protocols, it is possible that wodTelnetDLX will internally negotiate connection parameters, before Connected event is fired at all. This is done to make wodTelnetDLX as much transparent to protocol used as possible. You might notice packets transmitted to/from server in the meantime, meaning wodTelnetDLX connected already but is still negotiating protocol parameters.
If SSH protocols are used, please check Protocol property as you might see it changed internally by wodTelnetDLX. This is possible if you set it to SSHAuto. wodTelnetDLX will negotiate possible SSH protocol version, and change Protocol property accordingly.