Wednesday, November 24, 2010

How: using NetMeeting with SSH

NetMeeting on a tunnel SSH can be a tedious task.

Because NetMeeting uses a number of dynamic ports for the connections and a number of ports for entries in directories and other services, it is almost impossible to build a specific list of ports to forward to the SSH tunnel. The best option is to use dynamic port transfer: feature in SSH that allows to transfer all connections via SSH tunnel, which primarily operates as a SOCKS proxy server. Difficulty: average

Instructions

Things you need: remote shell account
  1. 1

    Start a command prompt or an SSH client that supports dynamic port transfer via SSH support.

OpenSSH has a Windows SSH port while PuTTY is a popular graphical client. Other clients may ports dynamic routing not supported.
  • 2

    Run the command "ssh server.com D 1080 - C" where "server.com" is the remote SSH server you will be relaying connections.

  • If you hear that socket using a graphical client, select dynamic ports transfer 1080 as the port number to use. Type your credentials when prompted to set up SSH tunnel completely.
  • 3

    Start Internet Explorer and then "Internet Options" access "Connections" and finally "LAN settings" on the proxy settings menu "Tools", then.

  • Click on the checkbox "Use A proxy server for your LAN" and enter "Localhost" as the address and port 1080. Click on "OK" in the dialog boxes LAN and Internet Options settings to save the system default proxy settings.
  • > ticleStep4 "> 4"

    Start NetMeeting and connect to a meeting as you normally have.

    Encrypted connection be dynamically passed to the remote SSH server are configured as tunnel.

    No comments:

    Post a Comment