Wiki

NeoRouterWiki:NetworkExplorer

From NeoRouterWiki

(Difference between revisions)
Jump to: navigation, search
(Wake-on-LAN (WOL))
(Connection Options)
Line 125: Line 125:
==== P2P Connection ====
==== P2P Connection ====
 +
 +
This option allows user to specify the connection type between this computer and its peers. The default option is
 +
UDP. User can also use direct TCP connection or relay traffic through NeoRouter server.
 +
 +
[[Image:P2PConnection.JPG]]
 +
 +
==== Proxy Setting ====
 +
 +
If the client host is behind proxy, user can enter the proxy information here.
 +
 +
[[Image:Proxy.JPG]]
 +
 +
==== Server Local Address ====
 +
 +
This option can be used to work around the connectivity issue when NeoRouter server is behind a router that does not support hairpin.
 +
 +
A router supports hairpin if it allows a host behind it to send network messages to its public-facing interface. Unfortunately some popular routers do not support this feature or turn off this feature by default.
 +
 +
When user logs into NeoRouter, Network Explorer first translates domain name into router’s public address using the NeoRouter DDNS service, and then tries to connect to server using this address. If both NeoRouter server and client are behind the same router and the router does not support hairpin, the router will block the messages that client sends to the router’s public address, thus client fails to establish connection to server. User could work around this issue by entering server’s LAN IP address instead of domain name in the “log on to” box, but this can be a
 +
hassle for laptop users who frequently move between networks.
 +
 +
These users can choose the second option “Connect to server using its local address when possible” in the following dialog and enter server’s local address. NeoRouter Network Explorer can detect when client and server are behind the same router and automatically choose the specified local address to establish the connection to server.
 +
 +
[[Image:AltServer.JPG]]

Revision as of 11:20, 24 June 2010

Contents

NeoRouter Network Explorer

Sign In

1. Launch NeoRouter Network Explorer from "Windows Start Menu | All Programs | NeoRouter | NeoRouter Network Explorer". Image:NetworkExplorerSignIn.JPG

On Mac Leopard or above, launch NeoRouter Network Explorer from Applications folder. You can also pin NeoRouter to the dock. Image:NetworkExplorerSignInMac.JPG

2. Enter user name and password of a valid account. If your NeoRouter server runs on Windows, you can use the administrator account created during server setup (NeoRouterWiki:ServerSetup). If you are using NeoRouter server for Linux/router firmware, you can use the account you use to login Linux or router. You can also create additional accounts in the Configuration Explorer.

3. In the "Log on to" field, enter the domain name you have chosen during server setup (NeoRouterWiki:ServerSetup). If you did not setup a domain name, you can enter the server’s IP address or computer name. You can also enter "localhost" if the Network Explorer is on the same PC as the server.

4. Click the "Sign In" button.

Manage computer list

The computer list is your view of the virtual LAN. You can add any computer of your LAN to this list and organize according to your preference. You will always have the same list regardless where you sign in from. Each user will have his/her separate list.

Initially you will see an empty computer list after signing in for the very first time (like the left picture below). To add a computer, you can choose the menu "Computers | Add a computer", and then select the computer and category in the dialog. Once complete, your computer list will be updated (see the right picture below).

Image:NetworkExplorerComputerList1.JPG

You can use categories to help manage a long list of computers. To create a category, you can choose menu "Computers | Create a category". To move a computer to a different category, you can simply drag and drop.

Image:NetworkExplorerComputerList2.JPG

OS type icons

Starting in release v0.9.8, the computer list shows the OS types in the computer list.

If you had used a previous version, OS type icon may not show for the existing clients.

Image:OSTypeIcon.JPG

CLI for Mac, Linux and Win2k

1. Usage: nrclientcmd [-d DOMAIN] [-u USERNAME] [-p PASSWORD] [-setproxy] [-setconn] [-dbroot DBROOT] [--help]

  • -setproxy: set proxy information.
  • -setconn: set client-to-client connection.

nrclientcmd requires domain, username and password info to sign in. You can either pass them in the command line or you will be prompted to enter them.

  • -internal: generate tags between information sections. This option can be used for third party developers to create a UI wrapper for CLI, which extends the UI look&feel and interact with CLI to implement operations.

2. After signing in, you will see your computer list just like on Windows. The computer list will automatically update if there are any changes in your virtual LAN.

  • Screenshot on Mac:

Image:Mac_clientcmd_cli.jpg

  • Screenshot on Ubuntu Linux:

Image:Nrclientcmd_screenshot.JPG

Remote access

In the computer list, two different icons Image:NetworkExplorerComputerOnlineIcon.JPG and Image:NetworkExplorerComputerOfflineIcon.JPG are used to represent online and offline computers respectively.

If you click on a computer in the list, a popup dialog will display a list of actions you can take to remotely control and access this computer. If a computer is online, the following actions are supported:

Icon Action
Image:NetworkExplorerComputerRemoteDesktopConnectionIcon.JPG remote desktop connection
Image:NetworkExplorerComputerFileSharingIcon.JPG file sharing
Image:NetworkExplorerComputerIcmpPingIcon.JPG ICMP ping
Image:NetworkExplorerComputerCopyIpAddressIcon.JPG copy the IP address

If a computer is offline, the following actions are supported:

Icon Action
Image:NetworkExplorerComputerRemoteWakeUpIcon.JPG remote wakeup


Custom action: you can even define your own action using the Add-On manager. NeoRouterWiki:AddOnManager



Information on Microsoft Remote Desktop Connection
For XP users: Get started using Remote Desktop with Windows XP Professional
For Vista users: Remote Desktop Connection: frequently asked questions
Information on Windows File Sharing
For XP users: Sharing files
For Vista users: File sharing essentials
Information on Wake-on-LAN
WikiPedia: Wake-on-LAN
EnergyStar: Wake On Local Area Network (LAN)

Wake-on-LAN (WOL)

WOL must be enabled in both the BIOS and the Windows network card settings. NeoRouter installer is able to enable the network card automatically; but you will have to make the BIOS change manually. Here is how you can do it:

a) restart computer; when prompted, click F2 to enter BIOS

b) find WOL setting like shown in the following image, enable it

Image:WakeOnLanBiosSetting.jpg

c) save and exit


Connection Options

Connection Options dialog can be opened from Network Explorer menu “File | Connection”.

P2P Connection

This option allows user to specify the connection type between this computer and its peers. The default option is UDP. User can also use direct TCP connection or relay traffic through NeoRouter server.

Image:P2PConnection.JPG

Proxy Setting

If the client host is behind proxy, user can enter the proxy information here.

Image:Proxy.JPG

Server Local Address

This option can be used to work around the connectivity issue when NeoRouter server is behind a router that does not support hairpin.

A router supports hairpin if it allows a host behind it to send network messages to its public-facing interface. Unfortunately some popular routers do not support this feature or turn off this feature by default.

When user logs into NeoRouter, Network Explorer first translates domain name into router’s public address using the NeoRouter DDNS service, and then tries to connect to server using this address. If both NeoRouter server and client are behind the same router and the router does not support hairpin, the router will block the messages that client sends to the router’s public address, thus client fails to establish connection to server. User could work around this issue by entering server’s LAN IP address instead of domain name in the “log on to” box, but this can be a hassle for laptop users who frequently move between networks.

These users can choose the second option “Connect to server using its local address when possible” in the following dialog and enter server’s local address. NeoRouter Network Explorer can detect when client and server are behind the same router and automatically choose the specified local address to establish the connection to server.

Image:AltServer.JPG