Running Anzio on a Terminal Server or File Server

AnzioWin and Anzio Lite are both Windows-based terminal emulation programs designed for individual user to access remote hosts over various connection methods. Both programs can work from stand-alone PCs, from a file server or from a Windows terminal services server (including Citrix and Wyse).

While the installer is not specifically a terminal services server installer, the procedure for setting up AnzioWin or Anzio Lite in a terminal or file server environment is pretty straight forward and requires little more to get it running than the basic installation package. However, there are some key points that should bve mentioned when installinf and running in these environments.

File Server

When referring to a File Server, we consider this to be a shared drive environment, one where multiple people have access to the Anzio folder and are allowed to run the AnzioWin or Anzio Lite program from their PC. While slightly different than a terminal services server in functionality, there are many of the same issues.

Installation in this environment involves several steps:

1. Install it as Administrator on the file server.
    
2. Create an empty ser.ini file in the Anzio directory that will contain the serial number and license information. The license information is normally stored in the Windows registry for the specific user. However, in this environment, it should be accessible to all users and hence, we need to create an encrypted license file by first creating an empty ser.ini file (you can do this with Notepad).
    
3. Bring up AnzioWin or Anzio Lite. Select the terminal type and then when it asks for license information, enter in your license serial number and activation code. Remember that this license is a multiple user license, so you must have a license that matches or exceeds the number of users that will use Anzio.
    
4. If you are going to let each user enter their own communications parameters, when it comes to entering the communications settings, Cancel, and then quit AnzioWin or Anzio Lite without saving the parameters. If you want to set up all users to access the same host with the exact same settings, a global defaults file, then go through the communications settings and get attach, then exit AnzioWin or Anzio Lite and Save the parameters.
    
5. Add access to the directory and the executable for anyone or to the specific group you wish to have access to it. Access for "read" is needed for the keys file (the key file associated to the terminal type the user will be emulating) and the serial number file (ser.ini), and read/execute access is needed to the executable (AnzioWin is anzio32.exe and Anzio Lite is anzio32r.exe).
    
6. If you created a global default file, make sure to mark it as read-only.
    
7. For each clients PC, create a desktop shortcut to the executable on your shared drive.
   

That's it! But be sure to also look over the notes below as there are a couple of items you, as an administrator, you should be aware of.

Terminal Services

When referring to a Terminal Services Server, we consider this to be any of those Windows environments where a specific server is used to bring up a remote user under a copy of Windows from the server. This includes Citrix, Wyse, Windows 2003/2008 TS and others. From these sessions, you can allow a user to run the AnzioWin or Anzio Lite program from their PC. While slightly different than a file server environment in functionality, there are many of the same issues. But it is really no different in setup than it is for any Windows program you do in this setting.

Installation in this environment involves several steps:

1. Install it as Administrator on the terminal server for all users.
    
2. Create an empty ser.ini file in the Anzio directory that will contain the serial number and license information. The license information is normally stored in the Windows registry for the specific user. However, in this environment, it should be accessible to all users and hence, we need to create an encrypted license file by first creating an empty ser.ini file (you can do this with Notepad).
    
3. Bring up AnzioWin or Anzio Lite. Select the terminal type and then when it asks for license information, enter in your license serial number and activation code. Remember that this license is a multiple user license, so you must have a license that matches or exceeds the number of users that will use Anzio.
    
4. If you are going to let each user enter their own communications parameters, when it comes to entering the communications settings, Cancel, and then quit AnzioWin or Anzio Lite without saving the parameters. If you want to set up all users to access the same host with the exact same settings, a global defaults file, then go through the communications settings and get attach, then exit AnzioWin or Anzio Lite and Save the parameters in the Anzio directory.
    
5. Add access to the directory and the executable for anyone or to the specific group you wish to have access to it. Access for "read" is needed for the keys file (the key file associated to the terminal type the user will be emulating) and the serial number file (ser.ini), and read/execute access is needed to the executable (AnzioWin is anzio32.exe and Anzio Lite is anzio32r.exe).
    
6. If you created a global default file, make sure to mark it as read-only.
    
7. For each clients PC, make sure a desktop shortcut to the executable shows up.
   

Be sure to look over the notes below as there are a couple of items you, as an administrator, you should be aware of.

User Considerations

Default File

The default file is normally called "anziowin.def" for both AnzioWin and Anzio Lite and by default, is located within the Anzio directory. However, starting with version 16 of AnzioWin and Anzio Lite, this file, if not found in the Anzio directory, may be found automatically in the user's default "APPDATA" directory. this is particularly important in the Windows Vista arean where the user has no access rights to "Program Files\Anzio" by default.

In a file server or terminal services server environment, a global file (marked as read-only) can be setup under the Anzio directory and each user will use the same settings.

If you wish to setup individual, user controlled, default files, you can create one to start with, move it to the various user directories under APPDATA or an appropriate user directory and then remove the global one. AnzioWin and Anzio Lite will automatically try to find the appropriate default file in one of these directories.

You can also define multiple default files or name default files as you wish (not calling them "anziowin.def"). Do this with the File menu's "Save as" option. With this a default file can be saved anywhere and under any name. When you do this, a question will be asked if you wish to create a Desktop shortcut to this default file. If you are the Administrator, say no, if a user, say yes.

As Administrator if you wish to setup individual default files located somewhere else, you would need to also change the AnzioWin or Anzio Lite shortcuts. The target should reference the executable name and the default file name, i.e.

"Y:\Program Files\Anzio\anzio32.exe" "c:\documents and settings\appdata\anzio\bobs_default.def"

or

\\TSERVER\Anzio\anzio32.exe "z:\AppData\bobs_default.def"

Keys File

Both AnzioWin and Anzio Lite have an associated keys file for the particular terminal type the user will emulate. This keys file determines how function keys and special keys interact with the host. This keys file can normally be left on the server. If you are running AnzioWin, you may want to mark this file as read-only as well since AnzioWin can change and save this file.

• If you are working with an individual default file per user, to do this, you could copy the key file to a specific user directory and then change the Anzio default file to point to that key file if you want to allow the user to change key definitiions. You can do this through the Read Keys under the file menu.
   
• If you are using a global default file, but want individual users to have their own keys, you may be able to change the file name of the keys file to point to a virtual user directory such as %USER%\wyse50.kys (refer to your terminal services user setup documentation). However, for this to work, you will need to manually change the keys filename in the default file (you can do this by opening the default file in Notepad)

Macros

While Anzio Lite does not allow users to setup any user-defined macros or scripts, AnzioWin does. These macros are normally saved in the keys file. If you are to allow this, you will need to set up AnzioWin's key file similar to an individual default file, rather than a shared key file we will want each user to have their own key file.

• If you are working with an individual default file per user, to do this, you would copy the key file to a specific user directory and then change the Anzio default file to point to that key file. You can do this through the Read Keys under the file menu.
   
• If you are using a global default file, but want individuall users to have their own macros, you may be able to change the file name of the keys file to point to a virtual user directory such as %USER%\wyse50.kys (refer to your terminal services user setup documentation). However, for this to work, you will need to manually change the keys filename in the default file (you can do this by opening the default file in Notepad).

License Considerations

AnzioWin and Anzio Lite licenses are based on a per PC serial number. When you purchase a license from us for multiple users, the license usually comes with a single license and activation code for all users. This makes setting up a "ser.ini" file, talked about above, simple. Remember however that the ser.ini file should be protected and not distributed, it may cause problems if ran on other servers or on individual PCs.

A standard license is issued for the number of users you have running on your file server or terminal services server. This is for the total number of user nodes and a single license for each should be purchased. There are two exceptions:

• If you are running any approved license management software and can control the number of users which have access to the software, then you could purchase a reduced license for just that number of users. Contact us for which license management software packages we can work with.
   
• If you are running approved license management software and are limiting the number of simultaneous users, you may want to consider an concurrent-use license from us. Thhis is easier to explain in an example:

"Our terminal server supports 500 users, but our host only supports 50 simultaneous users. Hence our license management software is set up for 50 users. But any of the 50 users may login from any of the 500 PCs. Hence we need a concurren license for 50 users for AnzioWin."

Back to top

AnzioWin and FTP
by Bobby Ezell

AnzioWin version 16.0m is the latest release of our full-featured terminal emulation product and it offers some unique file transfer capabilities over a network through the FTP protocol.

AnzioWin can connect to a remote host over the telnet or the Secure Shell protocols. Most host systems that connect with telnet, also allow an FTP connection for file transfer, while most hosts supporting Secure Shell also support SFTP (SSH FTP). Both of these allow extremely fast file transfer capabilities. And AnzioWin has enhanced this with a two unique opportunities, graphical access and host or user macro initiated access.

The FTP/SFTP Dialog

The FTP and SFTP dialogs within AnzioWin provide access to the host and to the PC for file transfers, including drag/drop, fiel transfer, file print and file open options.

From this dialog, you can drag and drop a file, select a file and transfer it, or navigate around either the PC or the host (as long as you have proper permissions). With a right mouse click over a host name or a local PC name, you can also do numerous functions to the file, such as open it, print it, etc.

Host or Macro Initiated Transfers

AnzioWin supports scripting and script commands, as well as simple user-defined macro. From within AnzioWin, you can set a macro or script to run as an association to special key or key sequence, to initiate a file transfer over the FTP or SFTP protocol. New commands in AnzioWin to support FTP file transfers are

FTPPUT, FTPPUT/S, FTPGET, FTPGET/S

Commands in AnzioWin to support SFTP file transfers are

SFTPPUT, SFTPPUT/S, SFTPGET, SFTPGET/S

Commands assume that the host name, username, and password for the FTP session are the same as for the Anzio telnet or SSH connection. Thus the command can be as simple as

FTPGET <filename>

The full syntax is:

FTPGET[/S] [ASCII] <hostfile> [<PCfile>]

where <hostfile> can be a name, a pathname (with either kind of slash), or a URL matching:

username[:password]@hostname[:port]/filepath

(note that you can't do username and filepath but not hostname). The "ASCII" modifier causes an ASCII (text mode) transfer. If <PCfile> is not given, the PC file name will be derived from the basename (name without directories) of the hostname. The "/S" causes a status result to be sent to the host ("00" means success). FTPPUT follows the same syntax. Environment variable expansion will take place. Anzio's DOWNLOAD DIRECTORY will affect downloads (FTPGET[/S]). There may be a delay, with no progress indicator, during long transfers.

FTPGET/S [ASCII] hostfile [pcfile]
FTPPUT [ASCII] hostfile [pcfile]
FTPPUT/S [ASCII] hostfile [pcfile]

where hostfile name is not optional, but pcfile is. Binary is the default transfer type, but you can override this with "ASCII". As an example, suppose you want to move a file named "myfile" from your own home directory on the host to your PC. Just do (after an <ctrl><shift>f):

FTPGET myfile

These commands assume that you are dealing with the same host, the same user login, and the same password that Anzio is already accessing. Be sure you have the username and password entered in Anzio's Communicate:Login menu. You can use any of the following variations:

FTPGET ASCII myfile
FTPGET myfile pcfilename
FTPGET hostname/myfile

<hostfile> can be a name, a pathname (with either kind of slash), or a URL matching:

username[:password]@hostname[:port]/hostfileandpath

If <PCfile> is not given, the PC file name will be derived from the basename (name without directories) of the hostname. Anzio's DOWNLOAD DIRECTORY will affect downloads (FTPGET[/S]). FTPPUT uses the same syntax as FTPGET:

FTPPUT[/S] [ASCII] <hostfile> [<pcfile>]

Likewise any of the above commands can be sent from the host and initiated from your host application by simply sending the appropriate host command inside your application:

One more example, a shell command telling Anzio to do a transfer:

printf "\034ftpput/s uploaddir/newfile c:/transfer/upfile\035";

(note that using forward slashes simplify the shell scripting).

Back to top

Anzio Dropped Connections
by Bobby Ezell

One of the most often asked questions is "...why do we get dropped connections using Anzio and we do not with web anf FTP access, and how do we prevent this?"

Well, the answer is vague at best, but there are some things you can do to a) debug what is going on and b) maybe prevent it.

What is causing the line drop

Both telnet and Secure Shell connections over a network to a remote host are what is called a "stateful" connection. This is a connection that must always be up and available or it forces a line drop and the user will have to log back in. In the web, email and FTP world, these are packet-oriented, "stateless" connections that do not have to always be connected as they just keep sending a packet at a time. Hence they can live through a line drop or network reset.

We most often see these problems creep in when connecting over the Internet where multiple devices and vendors are involved. However, they can also happen on local networks as well. Some of the causes are:

• A network device at some ISP (Internet Service Provide) is dropping the line periodically to reset routing tables, NAT addresses, DHCP information or just because the devices are extremely busy with traffic and time out.
• A local device is resetting due to some routing table or time-to-live settings.
• A network card at the client's PC or at the host end is having network problems or is receiving more traffic than it can handle.
• The network is actually dropping (usually a sign of a network card, a switch port or network device going bad).

Less common causes are

• Your host system login script has a TOUT, TMOUT or some other idle timeout settings in the user's login profile.
• Your PC is busy with some large Windows or anti-virus or other application update that seems to have priority over other network traffic.
• Your PC has a virus and is flooding your network card
• Some outside influence is causing a denial-of-service attack against your router, your host end router, your PC or your host network connection.
• The Internet or your local network is simply flooded with actual traffic.

The dropped line is an indication that something is happening that needs to be resolved. It can simpoly be a configuration issue (such as when to clear routing tables, etc.), it can be an issue of an overloaded network or device, or it can be more serious.

How to prevent it

Of course the recommendation is to fix whatever the problem is. This is easier said than accomplished, especially if you are connecting over the Internet through multiple vendors and through multiple devices. Here are some recommendations:

a) "ping" and tracerouter (tracert on Windows), will help determine if you are having network device problems or if the network is unreachable for periods of time. Run these and look for long latencies (time between packets). This can be a sign of problems and definitely can affect a stateful connection.

b) Talk to the various vendors involved. Thei devices may not be set to accomodate stateful connections. In many cases, if you get the right techie, and you mention that you are doing a telnet or Secure Shell connection, they will know right away what device or firewall is causing the problem and how to fix it.

c) Check all network connections for problems. Also, if you are having problems connecting, and you are going through a local hub, router or switch, try changing ports and see if the probelm moves.

d) If you are connecting wirelessly, make sure you have enough signal strength and that it is continuous, no other devices or interference is influencing the connection.

e) Put a packet sniffer or some other network probe device on the local network and try capturing traffic. A network probe or a software package like Ethereal, can be set to capture data over a period of time. This not only may point at a device having a problem, but will also reveal any viruses, denial-of-service attacks or network slowdowns due to other applications.

When all else fails, and sometimes as a your only option, you can try to mask this problem by changing the STAYALIVE option in AnzioWin or Anzio Lite.

The STAYALIVE option, found under the Communicate : Network menu in AnzioWin and Anzio Lite is normally set to zero (this does nothing). If you change this to a value, such as 25, then the Anzio programs will send a single empty packet to the destination host every 25 seconds. this packet, called a No-OP packet, does not cause any significant traffic, but it can help in some cases.

Be aware that some hosts and some firewall or network devices will not let this packet go through and it can in fact, cause problems with certain security software.

Conclusion

Anzio is a stateful connection that must remain connected at all times. When that connection breaks, even if the network does not appear to drop, the connection to the remote host is broken and Anzio will disconnect.

Look under the Communicate menu in AnzioWin or Anzio Lite, at OnLine Drop and you can change this to reconnect. Look under the Communicate menu in AnzioWin or Anzio Lite at the Network StayAlive, and you may be able to mask the problem. Resolving the issue is your best bet, but it can be troublesome to get results.

Back to top