Hello,
I have an issue with ScSSHChannel.Connect.
If I compile the source under Win 7 the application works correctly but if I compile the same source with Win 8 the application give me the following error message:
First chance exception at $76B94B32. Exception class SocketException with message
'Socket error on binding. WSAGetLastError return 10013($271D)
An attempt was made to access a socket in a way forbidden by its access permissions'.
Process TDBRichViewEditor.exe (6412)
The following is the setup of TScSSHClient and TScSSHChannel and I have installed SecureBridge version 5.5.1
  object ScSSHClient1: TScSSHClient
    Connected = False
    HostKeyAlgorithms = <
      item
        Algorithm = aaRSA
      end
      item
        Algorithm = aaDSA
      end>
    HostName = 'hostname'
    Port = 7822
    User = 'username'
    Password = 'password'
    Timeout = 100
    KeyStorage = ScFileStorage1
    OnServerKeyValidate = ScSSHClient1ServerKeyValidate
    Left = 128
    Top = 77
  end
  object ScSSHChannel1: TScSSHChannel
    Client = ScSSHClient1
    SourcePort = 5433
    DestHost = 'localhost'
    DestPort = 5432
    Timeout = 10
    Left = 288
    Top = 77
  end
Many thanks
Pio Pio
			
									
									
						Issue with ScSSHChannel.Connect.
Re: Issue with ScSSHChannel.Connect.
We have tested TScSSHChannel on Windows 8 and all functionality works correctly.
The possible reason for this error is that another application, service, or kernel mode driver is bound to the same address that is specified in the TScSSHChannel.SourcePort property with exclusive access. Please check that only one component TScSSHChannel with the same SourcePort is active.
Also this problem can be connected with firewall settings or access privileges.
			
									
									
						The possible reason for this error is that another application, service, or kernel mode driver is bound to the same address that is specified in the TScSSHChannel.SourcePort property with exclusive access. Please check that only one component TScSSHChannel with the same SourcePort is active.
Also this problem can be connected with firewall settings or access privileges.