SSH servers are available for most Windows and UNIX platforms from several sources, including SSH Communications Security (www.tectia.com), Red Hat (www.redhat.com), SSH.Org (www.ssh.org) and others. Please refer to these sites for the correct version to download and the instructions for its installation. As for setting AnzioWin up to use with SSH, you do so with a clean startup, or by changing the communications method under the Communicate:Setup dialog. AnzioWin 12.5 and later support login and password authentication over the SSH1, SSH2 and OpenSSH protocols. Starting with version 12.6n, we also support public key authentication with SSH2 and OpenSSH (call for information on public key setup).

Are AnzioWin and Anzio Lite compatible with terminal servers?

Yes, we have AnzioWin and Anzio Lite running on many terminal servers around the marketplace. The only catch, similar to running from a file server (see above), is manually setting up shortcuts and making sure default files are referenced and read-only as necessary. As for entering a serial number/activation code for each workstation, this may not be necessary. We do have a method of accessing a global license entry - call for more information. Note that AnzioWin and Anzio Lite are licensed on a per-workstation base, a single license for each node accessing it from a terminal server, not one license per server, but one license per workstation.

AnzioWin / Anzio Lite will not connect to the host modem

Troubleshooting modems can be quite frustrating and time consuming. A couple of simple hints when connecting through AnzioWin or Anzio Lite: a) Make sure your host modem communications software is set correctly. It should handle the modem as a standard serial device (tty) and NOT as a PPP connection. If you are wanting to connect via PPP, use Microsoft's Dial-Up Networking to connect, and then run Anzio as a telnet, rlogin, or SSH connection. Also, check to see if your host serial port is set for "baud cycling" (common default setting on UNIX), whereby the baud rate may change if any errors are encountered. b) Make sure the host modem is set for dialing in (auto-answer). By default, modems are not configured to answer, you must configure them to do so. c) Know what your modem connection rates and settings are in advance. Remember that the host modem usually connects to the host over a serial line (unless it is internal) and if the PC uses an external modem, it too connects to the PC serially. Also, know the parity and stop bits. You then also have the rate of connection between the two modems (over the phone line). d) Test the host modem connection. Try dialing in manually and make sure the modem on the host picks up. You may also want to check with the system administrator for the host and make sure the modem is working for others (and that it has been tested). e) While there are standards out there for the higher speed modems, there are still a couple of different standards for error correcting that are followed. Know what each modem is set for. Compatibility among modems can be a real problem. f) If you are running an inexpensive PC internal modem (also called a WinModem), make sure you are using the latest drivers. These modems have little hardware and are driven by Windows software. Almost every one of these modems has had a major software update for each Windows version. And remember that even Windows ME, 2000 and XP may not ship with the latest drivers.

How can I change my Windows settings to increase my TCP/IP performance

It is possible to adjust certain TCP/IP parameters in Windows to increase performance and change the way the Winsock behaves. Check out the Microsoft web site for some helpful hints.

How can I tell Windows to stay connected to my host, it acts like it is timing out?

Anzio, and telnet in general, is a connection oriented protocol, requiring the connection remain up during a session's duration. However, network devices, traffic, auto-disconnects, etc., can cause the connection to be lost. Neither Anzio nor Windows has an auto-disconnect feature, but are dependent on the network staying active.

Sometimes you can fine tune the TCP/IP parameters to not respond quite so quickly or to retry more often before determining a connection as severed.

With the latest versions of Anzio Lite and AnzioWin (version 12.5 or later), you can also set an option that will occasionally send a single keep-alive packet to the host. In most cases this will work fine in keeping a connection open, especially over the Internet. However, remember that in doing this you are actually hiding some other issue that may cause problems down the road.

This option can be set in version 12.5 by doing a hexpatch command to the default file:

<ctrl><shift>f (to get to the Function line)
HEXPATCH 18c2 05<enter>

To use this feature in version 12.6 or later, go to Communicate:Network:Stay Alive, and enter an interval in seconds.

Whenever I bring up Anzio for local host access, Windows wants to dial out to my ISP. Can this be changed?

Anzio is simply trying to establish a connection to the desired host over the default network connection type for Windows. This is set in a Control Panel dialog called Internet Options. Under the tab "Connection", you will see a check item that says something like "Connect to the network using a modem" or "Always connect using my ISP" (wording varies between versions of the DUN, dial-up networking). There is also an option to "Connect using my Local Area Network". Unfortunately you can not have the best of both worlds. You can either connect to your ISP by default or to the LAN by default. However if you leave the box as is, Anzio should connect after you cancel the dial. If you change this option, Anzio (and other applications) will connect to your local network first. You may then have to set up a shortcut to do the dialing (see "My Computer" and "Dial-Up Networking"). Typically, people will set this option to connect locally first, then when they want to use their web browser, they will dial out by first going to the Dial-Up icon, rather than simply clicking on the browser icon.

Does Anzio do any time-outs over TCP/IP?

Anzio does nothing with time-outs. In fact, we totally depend on Windows and Windows is dependent on not getting any type of disconnect from the host. Within Windows, there are a few registry entries that relate to keeping a connection alive (refer to a reference guide on Windows Registry troubleshooting for more information). These determine when Windows will check for a dropped connection (how long to "stay alive") and how long to wait before determining the connection has been dropped from the other end. However, these do not determine time-outs. Rather Windows TCP/IP simply responds to a dropped connection. The most common problem for the dropped connection has to do with other network devices. A couple of examples are a) a router that drops stale "routes" out of its table after a period of time, b) WAN connection devices that occasionally get long latencies between the PC and Host and c) other devices, such as bridges, VPNs, firewalls, etc., that drop "stale" connections when a table fills up or idle period is reached. Of course, there are other causes, such as the host shell script having a time-out included, the host telnet server having time-outs set, etc. Sometimes you can fine tune the TCP/IP parameters to not respond quite so quickly or to retry more often before determining a connection as severed. Check out the Microsoft web site for some helpful hints.

How do I set Anzio up to access multiple hosts?

See our document on Using Anzio to Connect to Multiple Host Systems. This will describe how to set Anzio up for multiple host connections.

AnzioWin and Anzio Lite ZModem dates are suddenly wrong

When AnzioWin and Anzio Lite does file transfers, the date it grabs from the host is coming out wrong. The date comes in as a long integer, based on some beginning date and the size of this exceeds an artificial limit (this is not a buffer overflow issue, merely a bug).

In AnzioWin and Anzio Lite version 12.6zd or earlier and in releases of AnzioWin and Anzio Lite prior to 12.6, and in releases of AnzioWin and Anzio Lite version 15.0f or earlier, there was a problem whereby this integer was too large when the host file creation date was 1/10/2004 or newer.

Version 12.6zf and version 15.0m fix this problem. If you are on an early release of AnzioWin or Anzio Lite 15.0 or 12.6, you can update to the appropriate later release free of charge to fix this problem. The latest patch version can be downloaded from the Download page of our web site.

Users on releases prior to version 12.6 that are experiencing this zmodem problem, need to contact us about updates. Updates run 25% of list price and can be ordered online or by contacting us directly.

I am having problems with Kermit and Anzio, why?

See our document on Using Kermit in Anzio. This will describe some of the problems associated with Kermit file transfer.

As with Zmodem, it is important to remember that the Kermit protocol is designed to work over serial connections.

We see many cases where someone is running Kermit over a network connected Anzio and expecting it to work as it would over a serial connection. In about 75% of the cases it may work great. But it's the other 25% that is hard to fix. Fortunately, unlike the Zmodem protocol, Kermit and its clones, such as G-Kermit and c-Kermit, are a little better supporting in a network environment - provided you are using the most recent versions.

You can play with some parameters in Anzio, namely windows and get better result. Also check the Columbia Kermit Project, http://www.columbia.edu/kermit/, for release information.

As with Zmodem, we recommend using FTP for network file transfers. You will find FTP about 200% faster and more reliable for moving files between systems.

Does Anzio support SCO UNIX 'mscreen'?

Yes it does, but there is a little more to it than that. Within SCO, the terminal type dictates if 'mscreen' will work properly. See our document on Using Anzio with 'mscreen'.

How can I remote print from UNIX without passthrough printing?

In the terminal emulation world, such as what is supported with our Anzio products (serial, telnet or SSH), remote printing was most often done by passthrough printing, where the print job would "pass through" the terminal session to the locally attached printer. Host applications often supported this as well as the terminal client.

Other types of printing were also supported by the host application and the host itself, namely printing to a spool or queue on the host for the local printer. The UNIX could also be set to print through the LPR or LP program which could then be redirected to remote printers or remote print servers.

Print Wizard supports three types of printing that works with these approaches, Despool, LPD and Listen.

Listen watches for remote print jobs coming in as raw data on port 9100, similar to Hewlett-Packard's ® JetDirect protocol.
LPD utilizes the LPR / LPD protocol for capturing print jobs destined for a remote print server.
Despool, and the FTPDespool variation, watches for remote jobs posted to a specific location. While Despool watches a locally mounted directory, such as over SMB or NFS, FTPDespool can watch a remote directory over the FTP protocol.

Anzio will not connect to the host modem

Note: This applies to a modem-to-modem connection, not an Internet or other network connection.

Troubleshooting modems can be quite frustrating and time consuming. A couple of simple hints when connecting through AnzioWin or Anzio Lite:

Make sure your host modem communications software is set correctly. It should handle the modem as a standard serial device (tty) and NOT as a PPP connection. If you are wanting to connect via PPP, use Microsoft's Dial-Up Networking to connect, and then run Anzio as a telnet, rlogin, or SSH connection. Also, check to see if your host serial port is set for "baud cycling" (common default setting on UNIX), whereby the baud rate may change if any errors are encountered.
Make sure the host modem is set for dialing in (auto-answer). By default, modems are not configured to answer, you must configure them to do so.
Know what your modem connection rates and settings are in advance. Remember that the host modem usually connects to the host over a serial line (unless it is internal) and if the PC uses an external modem, it too connects to the PC serially. Also, know the parity and stop bits. You then also have the rate of connection between the two modems (over the phone line).
Test the host modem connection. Try dialing in manually and make sure the modem on the host picks up. You may also want to check with the system administrator for the host and make sure the modem is working for others (and that it has been tested).
While there are standards out there for the higher speed modems, there are still a couple of different standards for error correcting that are followed. Know what each modem is set for. Compatibility among modems can be a real problem.
If you are running an inexpensive PC internal modem (also called a WinModem), make sure you are using the latest drivers. These modems have little hardware and are driven by Windows software. Almost every one of these modems has had a major software update for each Windows version. And remember that even Windows ME, 2000 and XP may not ship with the latest drivers.

What do I do if Anzio won't connect?

If you are on a PC that has connected before from the same location, to the same host system, the problem is almost certainly outside of Anzio. The server (host system) you're trying to connect to may be down. A new firewall may have been installed, either on your PC or at the host end.

If you are trying to connect to your own office from home for the first time, and nobody else has done that before (from outside the office), the office may not be configured right. Many things need to be in place at the office for that to be possible and secure. Your best bet is to use a local network consultant.

If you don't know who runs the system you're trying to connect to, we don't either, and we can't help you with that.