Server Remote Access Generation I

From ATLASWARES

Jump to: navigation, search


Remote connections to the WARES Server and to networked computers on its local subnet may be accomplished in a number of ways. Each connection method has its own set capabilities and limitations. The following connections are documented and supported.

Contents

Hamachi Virtual Private Network (VPN)

A VPN allows computers at separate locations, and therefore on separate networks, to be joined into a single virtual network for sharing resources. Due to limitations in networking services, a VPN is necessary to connect Windows(tm) or DOS machines if remote printing is required. We recommend the Hamachi zero-administration VPN client for this purpose.

Installing Hamachi on an XP Host computer

  • Configure the XP Host, installing software, mapping drives, and so forth
  • Setup Remote Desktop on the XP Host computer
  • Download the free client from Hamachi's site to the desktop
  • Double-click the installer and install setting it to activate on login
  • The Hamachi control panel will display
    • Select Create or join networks (the middle button at bottom)
    • Select Create a new network
    • Enter a unique network name: myDomainRemoteNumber (For example, AtlasWaresRemote1)
    • Enter a unique password
    • Create the network

Installing Hamachi on a remote XP client computer

  • Download the free client from Hamachi's site to the desktop
  • Double-click the installer and install setting it to activate on login
  • The Hamachi control panel will display
    • Select Create or join networks (the middle button at bottom)
    • Select Join an existing network
    • Enter the network name entered on the host: myDomainRemoteNumber
    • Enter the network password
    • Join the network

Configuring XP Client for Remote Printing over VPN

  • Share printers from XP Client computer on VPN
    • Open the menu item Start/Printers and Faxes
    • Right-click on the printer that you would like to share and select Sharing...
    • If there is a warning regarding security in the network just click If you understand the security risks but want to share printers without running the wizard, click here, then in the popup select Just enable printer sharing
    • Select Share this printer
    • Name the printer (PrinterName#)
    • Click Ok
  • Setup Remote access from XP Client to XP Host
    • Double-click the Hamachi icon on the task bar to open the control panel
    • note the XP host IP address listed in the Hamachi control panel (not the top title!)
    • Create a client desktop icon to connect to the XP host
  • note the XP Client IP address in the Hamachi control panel title (ClientIpAddress)
  • Double-click the remote connection icon to see the XP Host desktop
  • Map shared XP Client printers to XP Host LPT ports
    • Create or edit the NETUSE.BAT text document on the XP Host desktop (shown below)
    • Save the edited NETUSE.BAT file
    • Double-click the NETUSE.BAT icon to set the printer mappings
 net use LPT1 /delete
 net use LPT2 /delete
 net use LPT3 /delete
 net use LPT1 \\ClientIpAddress\PrinterName1 /persistent:yes
 net use LPT2 \\ClientIpAddress\PrinterName2 /persistent:yes
 net use LPT3 \\ClientIpAddress\PrinterName3 /persistent:yes

Windows(tm) sessions using NoMachine NX

Advantages

  • Very secure
  • Proxy based connection
  • SSH Encryption

Limitations

  • Registered user licenses required
  • Remote printing not supported

Configuring the NX Server

  • Login to the NoMachine NX Server console as the root user
  • Add a user for remote access
    • Open the menu item F Menu/Administration/Users and Groups
    • Select Add User
    • Give the user a unique user name containing no spaces (remoteUser)
    • Give the user a secure password consisting of both letters and numbers
      (note: the user name and password are case sensitive)
    • Click OK
    • Close the Users and Groups administration panel
  • Open a terminal (F Menu/System/Terminal)
    • Execute the following commands
 cd /usr/NX/bin/
 ./nxserver --useradd remoteUser
 cd ../scripts/setup
 ./nxserver --keygen

Configuring the NX Client

  • Download the NX Client for your platform
    (Note: NX Server and NX Node are not needed)
  • Run the installer with the default options
  • For Windows(tm) Clients:
    • Open the menu item Start/All Programs/NX Client for Windows/NX Client for Windows
  • For Mac OS X(tm) Clients:
    • Open /Applications/NX Client
  • For Linux Clients:
    • Open the menu item F Menu/Internet/NX Client for Linux/NX Client for Linux
  • On first run, the NX Connection Wizard opens
  • Click Next
  • Give the session a name such as Remote NX Connection
  • The host entry will be the public IP address of the NX Server
  • For speed optimization, select the type of internet connection you have
  • Click Next
  • Select the box that says Unix and change to Windows
  • In the box that is opened, enter the Windows(tm) XP Host's local IP address (i.e. 192.168.2.5)
  • Under Authentication select Use the following credentials
  • The username and password entered here should be the remote username and password used in the Windows(tm) XP Host
  • Click Ok
  • Check Enable SSL encryption of all traffic
  • Select the box that says Available Area and change to Fullscreen
  • Click Next
  • Check Show the Advanced Configuration dialog
  • Click Finish
  • In the window that opens, click Key...
  • Click Import
  • In the dialog, navigate to where you have the default.id_dsa.key file stored, select it, and click Ok
  • Click Save
  • Click Save again
  • Click Ok
  • In the login box, enter the username for the NX Server
  • In the password box, enter the password for the NX user
  • Click Login
  • If a dialog pops up regarding the authenticity of the host, click Yes
  • Now you are connected

Linux sessions using NoMachine NX

Advantages

  • Very secure
  • Full console or application only sessions
  • Excellent performance over low bandwidth

Limitations

  • Registered user licenses required

Configuring the NX Server

  • Login to the NoMachine NX Server console as the root user
  • Add a user for remote access
    • Open the menu item F Menu/Administration/Users and Groups
    • Select Add User
    • Give the user a unique user name containing no spaces (remoteUser)
    • Give the user a secure password consisting of both letters and numbers
      (note: the user name and password are case sensitive)
    • Click OK
    • Close the Users and Groups administration panel
  • Open a terminal (F Menu/System/Terminal)
    • Execute the following commands
 cd /usr/NX/bin/
 ./nxserver --useradd remoteUser
 cd ../scripts/setup
 ./nxserver --keygen
  • Navigate to the /usr/NX/share/keys folder
  • Copy the file default.id_dsa.key to a USB thumb drive for distribution to clients

Configuring the NX Client

  • Download the NX Client for your platform
    (Note: NX Server and NX Node are not needed)
  • Run the installer with the default options
  • For Windows(tm) Clients:
    • Open the menu item Start/All Programs/NX Client for Windows/NX Client for Windows
  • For Mac OS X(tm) Clients:
    • Open /Applications/NX Client
  • For Linux Clients:
    • Open the menu item F Menu/Internet/NX Client for Linux/NX Client for Linux
  • On first run, the NX Connection Wizard opens
  • Click Next
  • Give the session a name such as Remote NX Connection
  • The host entry will be the public IP address of the NX Server
  • For speed optimization, select the type of internet connection you have
  • Click Next
  • Check Enable SSL encryption of all traffic
  • Select the box that says Available Area and change to Fullscreen
  • Click Next
  • Check Show the Advanced Configuration dialog
  • Click Finish
  • In the window that opens, click Key...
  • Click Import
  • In the dialog, navigate to where you have the default.id_dsa.key file stored, select it, and click Ok
  • Click Save
  • Click Save again
  • Click Ok
  • In the login box, enter the username for the NX Server
  • In the password box, enter the password for the NX user
  • Click Login
  • If a dialog pops up regarding the authenticity of the host, click Yes
  • Now you are connected
Personal tools