• Introduction
• Getting Overthere
  • Depending on Overthere
  • Building Overthere
  • Running the Examples
• Programming Overthere
• Configuring Overthere
  • Protocols
  • Common connection options
  • Local
  • SSH
    • Host setup
    • Troubleshooting
    • Connection options
  • CIFS, WinRM and Telnet
    • Host setup
    • Troubleshooting
    • Connection options
  • Tunnelling
• Release History

Overthere is a Java library to manipulate files and execute processes on remote hosts, i.e. do stuff "over there". Overthere was originally developed for and is used in the XebiaLabs deployment automation product Deployit as a way to perform tasks on remote hosts, e.g. copy configuration files, install EAR files or restart web servers. Another way of looking at it is to say that Overthere gives you java.io.File and java.lang.Process as they should've been: as interfaces, created by a factory and extensible through an SPI mechanism.

Overthere is available under the GPLv2 with XebiaLabs FLOSS License Exception.

P.S.: Check the Overthere Ohloh page for some interesting code analysis statistics. If you use Overthere, don't forget to tell Ohloh! And while you're at it, you might want to vote for Overthere on the Overthere Freecode page too! ;-)

To get Overthere, you have two options:

1. Add a dependency to Overthere to your project.
2. Build Overthere yourself.

And, if you want, you can also run the Overthere examples used in the Overthere presentation mentioned above.

Binary releases of Overthere are not provided here, but you can download it straight from the Maven Central repository if you want to.

1. If your project is built with Maven, add the following dependency to the pom.xml:

    <dependency>
    	<groupId>com.xebialabs.overthere</groupId>
    	<artifactId>overthere</artifactId>
    	<version>2.3.1</version>
    </dependency>
   

2. If your project is built using another build tool that uses the Maven Central repository, translate these dependencies into the format used by your build tool.

1. Install Gradle 1.0 or up.
2. Clone the Overthere repository.
3. Run the command gradle clean build.

1. Install Maven 2.2.1 or up.
2. Clone the Overthere repository.
3. Go into the examples directory and run the command mvn eclipse:eclipse.
4. Import the examples project into Eclipse.
5. Change the login details in the example classes (address, username and password) and run them!

To program Overthere, browse the source code, check the examples and browse the Overthere Javadoc.

For a more thorough introduction to Overthere, check the presentation on Overthere that I gave for J-Fall 2011, a Java conference in the Netherlands (in English).

The protocols that Overthere uses to connect to remote hosts, such as SSH, CIFS, Telnet and WinRM, are existing protocols for which support is built into many platforms. As such you will not need to install any custom software on the remote hosts. Nevertheless in some cases the remote hosts have to be configured to correctly work with Overthere. Also, Overthere has a number of configuration features that allow you tweak the way it interfaces with the remote hosts.

Overthere supports a number of protocols to connect to remote hosts:

• local - a connection to the local host. This is a wrapper around java.io.File and java.lang.Process.
• ssh - a connection using the SSH protocol, to a Unix host, to a z/OS host, or to a Windows host running either OpenSSH on Cygwin (i.e. COPSSH) or WinSSHD.
• cifs - a connection using the CIFS protocol, also known as SMB, for file manipulation and, depending on the settings, using either WinRM or Telnet for process execution. This protocol is only supported for Windows hosts.

Apart from selecting a protocol to use, you will also need to supply a number of connection options when creating a connection. Common connection options are:

Apart from these common connection options, some protocols define additional protocol-specific connection options. These are documented below, with the corresponding protocol.

The local protocol implementation uses the local file manipulation and local process execution capabilities built-in to Java. The os connection option is hardcoded to the operating system of the local host and the tmp connection option defaults to the system temporary directory as specified by the java.io.tmpdir system property. There are no protocol-specific connection options.

The SSH protocol implementation of Overthere uses the SSH protocol to connect to remote hosts to manipulate files and execute commands. Most Unix systems already have an SSH server installed and configured and a number of different SSH implementations are available for Windows although not all of them are supported by Overthere.

Overthere uses the sshj library for SSH and supports all algorithms and formats supported by that library:

• Ciphers: aes{128,192,256}-{cbc,ctr}, blowfish-cbc, 3des-cbc
• Key Exchange methods: diffie-hellman-group1-sha1, diffie-hellman-group14-sha1
• Signature formats: ssh-rsa, ssh-dss
• MAC algorithms: hmac-md5, hmac-md5-96, hmac-sha1, hmac-sha1-96
• Compression algorithms: zlib and zlib@openssh.com (delayed zlib)
• Private Key file formats: pkcs8 encoded (the format used by OpenSSH)

To connect to a remote host using the SSH protocol, you will need to install an SSH server on that remote host. For Unix platforms, we recommend OpenSSH. It is included in all Linux distributions and most other Unix flavours. For Windows platforms two SSH servers are supported:

• OpenSSH on Cygwin. We recommend COPSSH as a convenient packaging of OpenSSH and Cygwin. It is a free source download but since 22/11/2011 the binary installers are a paid solution.
• WinSSHD is a commercial SSH server that has a lot of configuration options.

N.B.: The SFTP, SCP, SUDO and INTERACTIVE_SUDO connection types are only available for Unix hosts. To use SSH with z/OS hosts, use the SFTP connection type. To use SSH with Windows hosts, choose either the SFTP_CYGWIN or the SFTP_WINSSHD connection type.

To use the SFTP connection type, make sure SFTP is enabled in the SSH server. This is enabled by default in most SSH servers.

To use the SFTP_CYGWIN connection type, install COPSSH on your Windows host. In the COPSSH control panel, add the users as which you want to connect and select Linux shell and Sftp in the shell dropdown box. Check Password authentication and/or Public key authentication depending on the authentication method you want to use.
N.B.: Overthere will take care of the translation from Windows style paths, e.g. C:\Program Files\IBM\WebSphere\AppServer, to Cygwin-style paths, e.g. /cygdrive/C/Program Files/IBM/WebSphere/AppServer, so that your code can use Windows style paths.

To use the SFTP_WINSSHD connection type, install WinSSHD on your Windows host. In the Easy WinSSHD Settings control panel, add the users as which you want to connect, check the Login allowed checkbox and select Allow full access in the Virtual filesystem layout dropdown box. Alternatively you can check the Allow login to any Windows account to allow access to all Windows accounts.
N.B.: Overthere will take care of the translation from Windows style paths, e.g. C:\Program Files\IBM\WebSphere\AppServer, to WinSSHD-style paths, e.g. /C/Program Files/IBM/WebSphere/AppServer, so that your code can use Windows style paths.

To use the SUDO connection type, the /etc/sudoers configuration will have to be set up in such a way that the user configured with the connection option username can execute the commands below as the user configured with the connection option sudoUsername. The arguments passed to these commands depend on the exact usage of the Overthere connection. Check the INFO messages on the com.xebialabs.overthere.ssh.SshConnection category to see what commands get executed.

• ls
• cp
• mv
• mkdir
• rmdir
• rm
• chmod
• Any other command that you want to execute.

The commands mentioned above must be configured with the NOPASSWD setting in the /etc/sudoers file. Otherwise you will have to use the INTERACTIVE_SUDO connection type. When the INTERACTIVE_SUDO connection type is used, every line of the output will be matched against the regular expression configured with the sudoPasswordPromptRegex connection option. If a match is found, the value of the password connection option is sent.

This section lists a number of common configuration errors that can occur when using Overthere with SSH. If you run into other connectivity issues when using Overthere, pease let us know by creating a ticket or by sending us a pull request.

If the terminal type requested using the allocatePty connection option or the allocateDefaultPty connection option is not recognized by the SSH server, the connection will be dropped. Specifically, the dummy terminal type configured by [allocateDefaultPty] connection option, will cause OpenSSH on AIX and WinSSHD to drop the connection. Try a safe terminal type such as vt220 instead.

To verify the behaviour of your SSH server with respect to pty allocation, you can manually execute the ssh command with the -T (disable pty allocation) or -t (force pty allocation) flags.

The sudo command requires a tty to run. Set the allocatePty connection option or the allocateDefaultPty connection option to ask the SSH server allocate a pty.

This may be caused by the sudo command waiting for the user to enter his password to confirm his identity. There are two ways to solve this:

1. Use the NOPASSWD tag in your /etc/sudoers file.
2. Use the INTERACTIVE_SUDO connection type instead of the SUDO connection type.
3. If you are already using the INTERACTIVE_SUDO connection type and you still get this error, please verify that you have correctly configured the sudoPasswordPromptRegex option. If you have trouble determining the proper value for the sudoPasswordPromptRegex connection option, set the log level for the com.xebialabs.overthere.ssh.SshInteractiveSudoPasswordHandlingStream category to TRACE and examine the output.

The SSH protocol implementation of Overthere defines a number of additional connection options, in addition to the common connection options.

The CIFS protocol implementation of Overthere uses the CIFS protocol, also known as SMB, for file manipulation and, depending on the settings, uses either WinRM or Telnet for process execution. You will most likely not need to install new software although you might need to enable and configure some services:

• The built-in file sharing capabilities of Windows are based on CIFS and are therefore available and enabled by default.
• WinRM is available on Windows Server 2008 and up. Overthere supports basic authentication for local accounts and Kerberos authentication for domain accounts. Overthere has a built-in WinRM library that can be used from all operating systems by setting the connectionType connection option to WINRM_INTERNAL. When connecting from a host that runs Windows, or when using a "winrs proxy host" that runs Windows, the native WinRM capabilities of Windows, i.e. the winrs command, can be used by setting the connectionType connection option to WINRM_NATIVE.
• A Telnet Server is available on all Windows Server versions although it might not be enabled.

Windows domain accounts are supported by the WINRM_INTERNAL, WINRM_NATIVE and TELNET connection types, but the syntax of the username is different:

• For the WINRM_INTERNAL and WINRM_NATIVE connection types, domain accounts must be specified using the new-style domain syntax, e.g. USER@FULL.DOMAIN.
• For the TELNET connection type, domain accounts must be specified using the old-style domain synyax, e.g DOMAIN\USER.
• For both connection types, local accounts must be specified without an at-sign (@) or a backslash (\).

N.B.: When using domain accounts with the WINRM_INTERNAL connection type, the Kerberos subsystem of the Java Virtual Machine must be configured correctly. Please read the section on how to set up Kerberos for the source host and the remote hosts.

By default Overthere will access the administrative shares on the remote host. These shares are only accessible for users that are part of the Administrators on the remote host. If you want to access the remote host using a regular account, use the pathShareMapping connection option to configure the shares to use for the paths Overthere will be connecting to. Of course, the user configured with the username connection option should have access to those shares and the underlying directories and files.

N.B.: Overthere will take care of the translation from Windows paths, e.g. C:\Program Files\IBM\WebSphere\AppServer, to SMB URLs that use the administrative shares, e.g. smb://username:password@hostname/C$/Program%20Files/IBM/WebSphere/AppServer (which corresponds to the UNC path \\hostname\C$\Program Files\IBM\WebSphere\AppServer), so that your code can use Windows style paths.

To connect to a remote host using the CIFS protocol, ensure the host is reachable on port 445.

If you will be connecting as an administrative user, ensure the administrative shares are configured. Otherwise, ensure that the user you will be using to connect has access to shares that correspond to the directory you want to access and that the pathShareMappings connection option is configured accordingly.

To use the TELNET connection type, you'll need to enable and configure the Telnet Server according to these instructions:

1. (Optional) If the Telnet Server is not already installed on the remote host, add it using the Add Features Wizard in the Server Manager console.

2. (Optional) If the remote host is running Windows Server 2003 SP1 or an x64-based version of Windows Server 2003, install the Telnet server according to these instructions from the Microsoft Support site.

3. Enable the Telnet Server Service on the remote host according to these instructions on the Microsoft Technet site.

4. After you have started the Telnet Server, open a command prompt as the Administrator user on the remote host and enter the command tlntadmn config mode=stream to enable stream mode.

When the Telnet server is enabled any user that is in the Administrators group or that is in the TelnetClients group and that has the Allow logon locally privilege can log in using Telnet. See the Microsoft Technet to learn how to grant a user or group the right to logon locally on Windows Server 2008 R2.

For a PowerShell script to do what is described below in one go, check Richard Downer's blog

To use the WINRM_INTERNAL or the WINRM_NATIVE connection type, you'll need to setup WinRM on the remote host by following these instructions:

1. If the remote host is running Windows Server 2003 SP1 or SP2, or Windows XP SP2, install the WS-Management v.1.1 package.

2. If the remote host is running Windows Server 2003 R2, go to the Add/Remove System Components feature in the Control Panel and add WinRM under the section Management and Monitoring Tools. Afterwards install the WS-Management v.1.1 package to upgrade the WinRM installation.

3. If the remote host is running Windows Vista or Windows 7, the Windows Remote Management (WS-Management) service is not started by default. Start the service and change its Startup type to Automatic (Delayed Start) before proceeding with the next steps.

4. On the remote host, open a Command Prompt (not a PowerShell prompt!) using the Run as Administrator option and paste in the following lines when using the WINRM_INTERNAL connection type:

    winrm quickconfig
    y
    winrm set winrm/config/service/Auth @{Basic="true"}
    winrm set winrm/config/service @{AllowUnencrypted="true"}
    winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}
   

   Or the following lines when using the WINRM_NATIVE connection type:

    winrm quickconfig
    y
    winrm set winrm/config/service/Auth @{Basic="true"}
    winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}
   

   Or keep reading for more detailed instructions. :-)

5. Run the quick config of WinRM to start the Windows Remote Management service, configure an HTTP listener and create exceptions in the Windows Firewall for the Windows Remote Mangement service:

    winrm quickconfig
   

   N.B.: The Windows Firewall needs to be running to run this command. See Microsoft Knowledge Base article #2004640.

6. (Optional) By default basic authentication is disabled in WinRM. Enable it if you are going to use local accounts to access the remote host:

    winrm set winrm/config/service/Auth @{Basic="true"}
   

7. (Optional) By default Kerberos authentication is enabled in WinRM. Disable it if you are not going to use domain accounts to access the remote host:

    winrm set winrm/config/service/Auth @{Kerberos="false"}
   

   N.B.: Do not disable Negotiate authentication as the winrm command itself uses that to configure the WinRM subsystem!

8. (Only required for WINRM_INTERNAL or when the connection option winrsUnencrypted is set to true) Configure WinRM to allow unencrypted SOAP messages:

    winrm set winrm/config/service @{AllowUnencrypted="true"}
   

9. Configure WinRM to provide enough memory to the commands that you are going to run, e.g. 1024 MB:

    winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}
   

   N.B.: This is not supported by WinRM 3.0, included with the Windows Management Framework 3.0. This update has been temporarily removed from Windows Update because of numerous incompatiblity issues with other Microsoft products. However, if you have already installed WMF 3.0 and cannot downgrade, Microsoft Knowledge Base article #2842230 describes a hotfix that can be installed to re-enable the MaxMemoryPerShellMB setting.

10. To use the WINRM_INTERNAL or WINRM_NATIVE connection type with HTTPS, i.e. winrmEnableHttps set to true, follow the steps below:

    1. (Optional) Create a self signed certificate for the remote host by installing selfssl.exe from the IIS 6 resource kit and running the command below or by following the instructions in this blog by Hans Olav:

        C:\Program Files\IIS Resources\SelfSSL>selfssl.exe /T /N:cn=HOSTNAME /V:3650
        Microsoft (R) SelfSSL Version 1.0
        Copyright (C) 2003 Microsoft Corporation. All rights reserved.
       
        Do you want to replace the SSL settings for site 1 (Y/N)?Y
        The self signed certificate was successfully assigned to site 1.
       

    2. Open a PowerShell window and enter the command below to find the thumbprint for the certificate for the remote host:

        PS C:\Windows\system32> Get-childItem cert:\LocalMachine\Root\ | Select-String -pattern HOSTNAME
       
        [Subject]
          CN=HOSTNAME
       
        [Issuer]
          CN=HOSTNAME
       
        [Serial Number]
          527E7AF9142D96AD49A10469A264E766
       
        [Not Before]
          5/23/2011 10:23:33 AM
       
        [Not After]
          5/20/2021 10:23:33 AM
       
        [Thumbprint]
          5C36B638BC31F505EF7F693D9A60C01551DD486F
       

    3. Create an HTTPS WinRM listener for the remote host with the thumbprint you've just found:

        winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="HOSTNAME"; CertificateThumbprint="THUMBPRINT"}
       

For more information on WinRM, please refer to the online documentation at Microsoft's DevCenter. As a quick reference, have a look at the list of useful commands below:

• Do a quickconfig for WinRM with HTTPS: winrm quickconfig -transport:https
• View the complete WinRM configuration: winrm get winrm/config
• View the listeners that have been configured: winrm enumerate winrm/config/listener
• Create an HTTP listener: winrm create winrm/config/listener?Address=*+Transport=HTTP (also done by winrm quickconfig)
• Allow all hosts to connect to the WinRM listener: winrm set winrm/config/client @{TrustedHosts="*"}
• Allow a fixed set of hosts to connect to the WinRM listener: winrm set winrm/config/client @{TrustedHosts="host1,host2..."}

N.B.: You will only need to configure Kerberos if you are going to use Windows domain accounts to access the remote host with the WINRM_INTERNAL connection type.

In addition to the setup described in the WINRM section, using Kerberos authentication requires that you follow the Kerberos Requirements for Java on the host from which the Overthere connections are initiated, i.e. the source host.

Create a file called krb5.conf (Unix) or krb5.ini (Windows) with at least the following content:

[realms]
EXAMPLE.COM = {
    kdc = KDC.EXAMPLE.COM
}

Replace the values with the name of your domain/realm and the hostname of your domain controller (multiple entries can be added to allow the Overthere source host to connect to multiple domains) and place the file in the default location for your operating system:

• Linux: /etc/krb5.conf
• Solaris: /etc/krb5/krb5.conf
• Windows: C:\Windows\krb5.ini

Alternatively, place the file somewhere else and add the following Java system property to the command line: -Djava.security.krb5.conf=/path/to/krb5.conf. Replace the path with the location of the file you just created.

See the Kerberos V5 System Administrator's Guide at MIT for more information on the krb5.conf format.

N.B.: You will only need to configure Kerberos if you are going to use Windows domain accounts to access the remote host with the WINRM_INTERNAL connection type.

By default, Overthere 2.1.0 and up will request access to a Kerberos service principal name of the form WSMAN/HOST, for which an SPN should be configured automatically when you configure WinRM for a remote host.

If that was not configured correctly, if you have overridden the default SPN for which a ticket is requested through the winrmKerberosAddPortToSpn or the winrmKerberosUseHttpSpn connection properties, or if you are running an older version of Overthere, you will have configure the service principal names manually.

This can be achieved by invoking the setspn command, as an Administrator, on any host in the domain, as follows:

setspn -A PROTOCOL/ADDRESS:PORT WINDOWS-HOST

where:

• PROTOCOL is either WSMAN (default) or HTTP (if winrmKerberosUseHttpSpn has been set to true).
• ADDRESS is the address used to connect to the remote host,
• PORT (optional) is the port used to connect to the remote host (usually 5985 or 5986, only necessary if winrmKerberosAddPortToSpn has been set to true), and
• WINDOWS-HOST is the short Windows hostname of the remote host.

Some other useful commands:

• List all service principal names configured for the domain: setspn -Q */*
• List all service principal names configured for a specific host in the domain: setspn -L _WINDOWS-HOST_

This section lists a number of common configuration errors that can occur when using Overthere with CIFS, WinRM and/or Telnet. If you run into other connectivity issues when using Overthere, pease let us know by creating a ticket or by sending us a pull request.

For more troubleshooting tips for Kerberos, please refer to the Kerberos troubleshooting guide in the Java SE documentation.

The JCIFS library, which Overthere uses to connect to CIFS shares, will try and query the Windows domain controller to resolve the hostname in SMB URLs. JCIFS will send packets over port 139 (one of the [NetBIOS over TCP/IP] ports) to query the DFS. If that port is blocked by a firewall, JCIFS will only fall back to using regular hostname resolution after a timeout has occurred.

Set the following Java system property to prevent JCIFS from sending DFS query packets: -Djcifs.smb.client.dfs.disabled=true.

See this article on the JCIFS mailing list for a more detailed explanation.

If the problem cannot be solved by changing the network topology, try increasing the JCIFS timeout values documented in the JCIFS documentation. Another system property not mentioned there but only on the JCIFS homepage is jcifs.smb.client.connTimeout.

To get more debug information from JCIFS, set the system property jcifs.util.loglevel to 3.

The Kerberos subsystem of Java cannot start up. Did you configure it as described in the section on Kerberos setup for the source host?

The Kerberos subsystem of Java cannot find the information for the realm in the krb5.conf file. The realm name specified in the Kerberos configuration on the source host is case sensitive and must be entered in upper case in the krb5.conf file.

Alternatively, you can use the dns_lookup_kdc and dns_lookup_realm options in the libdefaults section to automatically find the right realm and KDC from the DNS server if it has been configured to include the necessary SRV and TXT records:

[libdefaults]
    dns_lookup_kdc = true
    dns_lookup_realm = true

The service principal name for the remote host has not been added to Active Directory. Did you add the SPN as described in the section on Kerberos setup for remote hosts?

The username or the password supplied was invalid. Did you supply the correct credentials?

Is the target machine part of a Windows 2000 domain? In that case, you'll have to add rc4-hmac to the supported encryption types:

[libdefaults]
    default_tgs_enctypes = aes256-cts-hmac-sha1-96 des3-cbc-sha1 arcfour-hmac-md5 des-cbc-crc des-cbc-md5 des-cbc-md4 rc4-hmac
    default_tkt_enctypes = aes256-cts-hmac-sha1-96 des3-cbc-sha1 arcfour-hmac-md5 des-cbc-crc des-cbc-md5 des-cbc-md4 rc4-hmac

The realm name specified in the Kerberos configuration on the source host does not match the case of the Windows domain name. The realm name is case sensitive and must be entered in upper case in the krb5.conf file.

The Kerberos subsystem of Java cannot start up and the remote WinRM server is sending a Kerberos authentication challenge. If you are using local accounts, the authentication will proceed succesfully despite this message. To remove these messages either configure Kerberos as described in the section on Kerberos setup for the source host or disallow Kerberos on the WinRM server as described in step 4 of the section on WinRM setup.

The Telnet service has been configured to be in "Console" mode. Did you configure it as described in the section on Telnet setup?

The Windows Firewall has not been started. See Microsoft Knowledge Base article #2004640 for more information.

This can occur if you have disabled the Negotiate authentication method in the WinRM configuration. To fix this situation, edit the configuration in the Windows registry under the key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\ and restart the Windows Remote Management service.

Courtesy of this blog by Chris Knight

The Windows Remote Management service is not running or is not running on the port that has been configured. Start the service or configure Overthere to use a different port number.

Multiple causes can lead to this error message:

1. The Kerberos ticket is not accepted by the remote host:

   1. Did you set up the correct service principal names (SPNs) as described in the section on Kerberos setup for remote hosts? The hostname is case insenstive, but it has to be the same as the one used in the address connection options, i.e. a simple hostname or a fully qualified domain name. Domain policies may prevent the Windows Management Service from creating the required SPNs. See this blog by LazyJeff for more information.

   2. Has the reverse DNS of the remote host been set up correctly? See Principal names and DNS for more information. Please note that the rdns option is not available in Java's Kerberos implementation.

2. The WinRM service is not set up to accept unencrypted traffic. Did you execute step #8 of the host setup for WinRM?

3. The user is not allowed to log in. Did you uncheck the "User must change password at next logon" checkbox when you created the user in Windows?

4. The user is not allowed to perform a WinRM command. Did you grant the user (local) administrative privileges?

Multiple causes can lead to this error message:

1. If the command was executing for a long time, this might have been caused by a timeout. You can increase the WinRM timeout specified by the winrmTimeout connection option to increase the request timeout. Don't forget to increase the MaxTimeoutms setting on the remote host as well. For example, to set the maximum timeout on the server to five minutes, enter the following command:

   winrm set winrm/config @{MaxTimeoutms="300000"}

2. If a lot of commands are being executed concurrently, increase the MaxConcurrentOperationsPerUser setting on the server. For example, to set the maximum number of concurrent operations per user to 100, enter the following command:

   winrm set winrm/config/service @{MaxConcurrentOperationsPerUser="100"}

Other configuration options that may be of use are Service/MaxConcurrentOperations and MaxProviderRequests (WinRM 1.0 only).

If you see an unknown WinRM error code in the logging, you can use the winrm helpmsg command to get more information, e.g.

winrm helpmsg 0x80338104
The WS-Management service cannot process the request. The WMI service returned an 'access denied' error.

Courtesy of this PowerShell Magazine blog by Shay Levy

The CIFS protocol implementation of Overthere defines a number of additional connection options, in addition to the common connection options.

Overthere supports the tunnelling of every protocol over SSH. This can be used to reach hosts that live in a DMZ which can only be reached by connecting to a different host first. This in-between host is called the jump station. In order to configure an SSH tunnel, you need to provide a set of nested connection options specifying which host is used as the jump station.

When using a jumpstation to connect to the remote host, Overthere will dynamically allocate an available local port to use for the connection to the end station. Using an additional connection option, you can configure from which port onwards Overthere starts the allocation.

• Overthere 2.3.1 (16-Jan-2014)
  • Fixed #89
  • Fixed race condition in creation of local temporary directories.
• Overthere 2.3.0 (25-Oct-2013)
  • Implemented support for winrs, the native WinRM implementation available on Windows hosts, fixes issue [#12|xebialabs#12]. N.B.: To distinguish this connection type from the existing Java one, the connection type WINRM has been replaced by WINRM_INTERNAL (the Java implementation) and WINRM_NATIVE (the Windows implementation).
  • Added refreshKrb5Config=true option to the Kerberos JAAS configuration to make sure the configuration is re-read for every request.
  • Upgraded the SSH/J 0.9.0.
  • Fixed bug that occurred when reading or writing many files over a single SFTP connection to a WinSSHD server.
• Overthere 2.2.2 (28-Aug-2013)
  • Fixed #81.
• Overthere 2.2.1 (24-Jul-2013)
  • Fully implemented OverthereConnection.startProcess() for CIFS/WinRM connections, fixes issue #54 properly. The previous implementation did not handle stdin.
  • Fixed #57, #72, #73, #76, #77 and #79.
  • Updated documentation and troubleshooting guides for SSH, CIFS, WinRM and Kerberos.
  • Some minor code and documentation fixes.
• Overthere 2.2.0 (07-Feb-2013)
  • Introduced OverthereExecutionOutputHandler interface to allow stderr to also be captured character by character, fixes issue #67.
  • Made the commands used for SSH/SCP, SSH/SUDO and SSH/INTERACTIVE_SUDO connections configurable, fixes issue #52.
  • Made canStartProcess() return false for CIFS/WinRM connections because its startProcess implementation does not correctly handle stdin, disables fix for issue #54.
  • Fixed issues #65, #68 and #70.
  • Some minor code fixes.
  • Some not-so-minor documentation improvements: more setup and troubleshooting info for WinRM and Kerberos.
• Overthere 2.1.1 (17-Dec-2012)
  • Fixed issues #61 and #62.
  • Added connection option openShellBeforeExecute, fixes #63.
• Overthere 2.1.0 (26-Oct-2012)
  • Re-enabled support for Windows domain accounts in CIFS/Telnet connections, fixes issue #60.
  • Fixed Kerberos code to use WSMAN SPN by default, fixes #58.
  • Added option to add the port to the SPN, fixes #49.
  • Added support for Negotiate authentication (Kerberos only), fixes #59.
  • Some minor code and documentation fixes.
• Overthere 2.1.0-beta-1 (21-Sep-2012)
  • Implemented OverthereProcess.startProcess() for CIFS/WinRM connections, fixes issue #54.
  • Fixed issues #53 and #55.
  • Some minor code and documentation fixes.
• Overthere 2.0.0 (22-Aug-2012)
  • Stable release of Overthere 2.0.0.
  • Some minor code and documentation fixes.
• Overthere 2.0.0-rc-1 (17-Aug-2012)
  • Added sudoPreserveAttributesOnCopyFromTempFile and sudoPreserveAttributesOnCopyToTempFile to specify whether -p should be used to copy files from and to the connection temporary directory when the connection type is SUDO or INTERACTIVE_SUDO.
  • Changed default value of sudoOverrideUmask to true.
  • Fixed Kerberos authentication for WinRM connections which was broken by overzealouos code cleanup.
  • Upgraded to SSH/J 0.8.1.
  • Added description of WinRM options and how to set up Kerberos authentication to the documentation.
  • Added troubleshooting section to the documentation.
• Overthere 2.0.0-beta-7 (02-Aug-2012)
  • Fixed bug in WinRM implementation: It was not sending individual stdout chars to OverthereProcessOutputHandler.handleOutput().
• Overthere 2.0.0-beta-6 (02-Aug-2012)
  • Renamed CIFS_PATH_SHARE_MAPPING back to PATH_SHARE_MAPPINGS.
• Overthere 2.0.0-beta-5 (02-Aug-2012)
  • Added support for Windows domain accounts to CIFS and WinRM connection methods.
  • Renamed a few options.
  • Fixed bug in SSH tunnel port allocation code that caused the same local port to be allocated multiple times on Windows.
  • Changed license to GPLv2 with XebiaLabs FLOSS License Exception.
• Overthere 2.0.0-beta-4 (19-Jun-2012)
  • Fixed issue #42.
  • Moved the itest-support sub project out to new Github repository Overcast
  • Updated documentation.
• Overthere 2.0.0-beta-3 (27-Mar-2012)
  • Updated documentation.
• Overthere 2.0.0-beta-2 (23-Mar-2012)
  • Fixed issues #39 and #40.
  • Upgraded to latest jCIFS to fix issues with windows domain names and stability using tunnels.
  • Set default pty to true in case of interactive sudo and no pty set.
• Overthere 1.0.17 (20-Mar-2012)
  • Fixed issues #39 and #40.
• Overthere 2.0.0-beta-1 (05-Mar-2012)
  • Re-implemented SSH tunnels. Tunnels are now created on demand instead of the user having to specify the localPortForwards explicitly. This makes management of tunnels easier and prevents clashes.
  • Ported Overthere tests to use TestNG instead of JUnit.
• Overthere 1.0.16 (23-Feb-2012)
  • Reverted changes made to support SSH tunnels in 1.0.14 and 1.0.15 because it did not work as well as we hoped. We are reimplementing it for Overthere 2.0 to be released early March.
  • Fixed command line encoding bugs for SSH/CYGWIN on Windows:
    • Now transforming the first element of the command line to a Cygwin path so that batch files (and executables) in specific directories (instead of on the PATH) can be executed.
    • Encoding the command line as if the target OS is UNIX because OpenSSH on Cygwin uses Unix encoding.
• Overthere 1.0.15 (21-Feb-2012)
  • Added explicit close() method to the new com.xebialabs.overthere.OverthereConnection interface (it was a class in 1.0.13) that does not throw java.io.IOException.
• Overthere 1.0.14 (20-Feb-2012)
  • Added support for SSH tunnels to jumpstations.
  • Added support for NTLM authentication.
  • Upgraded to SSH/J 0.7.0.
• Overthere 1.0.13 (18-Jan-2012)
  • Masked passwords in logging.
  • Made ItestHostFactory also look for itest.properties in ~/.itest (in addition to the classpath and the current working directory).
• Overthere 1.0.12 (12-Jan-2012)
  • Allowed forward slashes (/) to be used in Windows paths.
  • Made it possible to access non-administrative shares on Windows so that the CIFS connection methods can be used with regular user accounts. See the pathShareMappings connection option.
  • Added the allocatePty connection option to specify an explicit pseudo terminal to use.
• Overthere 1.0.11 (09-Dec-2011)
  • Fixes to the SSH/WinSSHD implementation and a few other little fixes.
  • Added a lot of documentation.
  • Added examples project.
  • Changed license to ASLv2.
• Overthere 1.0.10 (23-Nov-2011)
  • Added support for SSH/WinSSHD on Windows.
• Overthere 1.0.9 (22-Nov-2011)
  • Initial public release with support for SSH on Unix as well as CIFS/TELNET, CIFS/WinRM and SSH/CYGWIN on Windows.