Yes, the ADTRAN Utilities were written for Windows 95: so it is unlikely it will work on Windows 7.
There's no bundle that has all those application combined (that I'm aware of), but they are all available on the internet. ADTRAN does not recommend any specific applications, but here is what I use:
For telnet and VT100 I use PuTTY - however PuTTY doesn't support an XMODEM file transfer. Other than that it works very well. PuTTY Download Page. Tera Term (Tera Term Open Source Project) works just as well, but I've grown more accustomed to the PuTTY interface.
I actually use TFTP Daemon for both a TFTP Server and a Syslog Server. TFTP server
So those 4 applications can be covered by 2 programs.
Hope this helps,
You continue to be of such great help. Thanks so much for sharing your
expertise and providing me with answers. More questions to come!
I downloaded the PuTTY and Tftpd apps and need some guidance as to how
I go about saving the Atlas 550 configuration.
I launched the PuTTY app and specified the destination to connect to
as the IP address I set earlier via my VT100 program and selected the
the Connection type as Telnet. I hit Open and entered the Atlas 550
password. This brought up a screen that is identical to the VT100
screen seen earlier.
So I have both serial and ethernet active connections to the Atlas 550
on 2 different machines. (The VT100 window is on a Mac and the PuTTY
window is on a PC. And changes that I make in the PuTTY window are
reflected in the VT100 window and vice versa.)
Following the directions in the Atlas 550 manual, I entered the local
IP address into the TFTP Server IP Address field.
Then I changed the TFTP Server Filename to a unique filename for
saving the config file to the remote server using the compete
directory path to the file C:\Users\Dave\Desktop\Atlas550.cfg
Then I moved to the Save Config Remotely field and pressed Enter and
pressed y to confirm. Current Transfer Status shows Download: Copying
Internal Config but Previous Transfer Status shows TFTP Error: File
Access Violation. This occurs quickly.
I must be missing something in the procedure. Any suggestions?
(Also, how does the Tftpd app figure into this?)
Thanks for your help.
The TFTP Server needs to be up and running, since this is the server you are sending the configuration file to. Generally you use the TFTP Server to specify the path for the ROOT directory, so when you set the "TFTP Server FIlename" in the ATLAS you are simply specifying the name and not the directory path. It should save the file to whatever you specify as the ROOT directory in the TFTP Server.
Hope that made sense,
So would a valid path for the ROOT directory be C:\Program Files
(x86)\Tftpd32 ? What is the naming convention I should adhere to?
(See image below.) I can't find any mention of ROOT directory in the
TFTP server app window.
In the Application, it gives the "Current Directory" which is the root directory. If you send a file to the server it will be saved in this directory. If you try to pull a file it will try to find it in this directory. You can BROWSE to another directory if you want, or you can go under SETTINGS and set the "Base Directory" to something else if you always want it to be another directory every time you open the Server.
So in the ATLAS you don't need to put a directory - just the name you want the configuration saved as.