We are having an issue connecting from a PC to configure TL Ashford. It's
pretty much mandatory to have a host table entry on the PC to connect to
the system. It doesn't matter if you already have a working dns entry to
the system which works fine for your 5250, odbc, etc. The problem with
this is, when we switch over to our backup system the developer cannot
connect to 5250 or anything else because of this host table entry still
pointing to the IP address of the down system.
A workaround might be having TL Ashford connect to AshfordBullshirt and
putting in a host table entry for that. Then the only problem would be TL
Ashford development not working during a switch. His 5250 and everything
else would be fine.
I hate host table entries!
The developer says I had a workaround for his old PC but I can't remember
what it was.