We upgraded from 4.xx to 5.3.17 and as the IT support guy for the store I have worked with many different POS companies and Aloha 4.xx for years and should be able to handle an upgrade no problem. Well apparently I'm missing something somewhere.
The setup:
BOH with two NICs one for terms and one for inet for CCs.
Two Terminals - Can ping and browse shares no problem from FOH or BOH.
However the terminals can not find the fileserver. I got one of the terminals to run as the fileserver and the other sees it and connects just fine. Still can not get either to find BOH. When I attempt to login at either terminal I get a - System redundancy limit has been exceeded! Restore your fileserver to continue or contact your service provider for assistance. - Error message. I have a call in Friday night but of course no one will get back to me 'til Monday. I hate sitting here wasting time so I finally was able to create an account on this forum to try and get some support (previous attempts to make an account have failed with error messages telling me to contact the admin of the site appears they have solved that I guess (wish they would of let me know this is a great forum)).
Things I've tried and settings that I thought may be an issue:
Terminals are win95 and the BOH is 2k. Debating upgrading the terms to 98, but don't see a real reason since 4.xx worked and it looks to work basically the same on the netork layer.
I setup term1 to login as TERM1 and setup a user account on the 2k box for it and also TERM2.
I thought maybe caps mattered so I went through today and renamed all the different places it refered to term1 or term2 to TERM1 or TERM2. Maintaine/hardware ini files etc. I might attempt to do another terminst to see if maybe I've got some command fixed on the BOH and maybe it'll pick it up. Yes it finds the BOH just fine when you do a terminst.
I tried going with the old setting like 4.xx ran (VERY insecurely) with administrator for login with no password for all the machines in the pos net. That also did not work.
I've tried giving the user account ellivated access (power user/admin/user etc). No change.
I've thought of ripping out the inet NIC but Aloha sales person said it was no problem. I've already ripped out all my hair so figured a NIC was no big deal.
Ideas? Maybe a magic switch they don't like to tell you about?
Help.
poshelp@94stewart.com
The setup:
BOH with two NICs one for terms and one for inet for CCs.
Two Terminals - Can ping and browse shares no problem from FOH or BOH.
However the terminals can not find the fileserver. I got one of the terminals to run as the fileserver and the other sees it and connects just fine. Still can not get either to find BOH. When I attempt to login at either terminal I get a - System redundancy limit has been exceeded! Restore your fileserver to continue or contact your service provider for assistance. - Error message. I have a call in Friday night but of course no one will get back to me 'til Monday. I hate sitting here wasting time so I finally was able to create an account on this forum to try and get some support (previous attempts to make an account have failed with error messages telling me to contact the admin of the site appears they have solved that I guess (wish they would of let me know this is a great forum)).
Things I've tried and settings that I thought may be an issue:
Terminals are win95 and the BOH is 2k. Debating upgrading the terms to 98, but don't see a real reason since 4.xx worked and it looks to work basically the same on the netork layer.
I setup term1 to login as TERM1 and setup a user account on the 2k box for it and also TERM2.
I thought maybe caps mattered so I went through today and renamed all the different places it refered to term1 or term2 to TERM1 or TERM2. Maintaine/hardware ini files etc. I might attempt to do another terminst to see if maybe I've got some command fixed on the BOH and maybe it'll pick it up. Yes it finds the BOH just fine when you do a terminst.
I tried going with the old setting like 4.xx ran (VERY insecurely) with administrator for login with no password for all the machines in the pos net. That also did not work.
I've tried giving the user account ellivated access (power user/admin/user etc). No change.
I've thought of ripping out the inet NIC but Aloha sales person said it was no problem. I've already ripped out all my hair so figured a NIC was no big deal.
Ideas? Maybe a magic switch they don't like to tell you about?
Help.
poshelp@94stewart.com