Aloha terminal 2 does not see anything entered on terminal 1

[IThelper1]

I wanted to start a new thread on this because my other issues are now resolved.

So here is my issue:
We have two terminals running Aloha 4.2. Term1 is also acting as the server and its running WIN98. Term2 is a new box running WIN2K.
If I enter a table in Term2 it shows up just fine on Term1. If I enter a table in Term1 I can't see it at all on Term2.

I've checked the Lana number on Term2 and it's 0. I've also tried this on a 98box and found the same issue.

Thank you!

 

[IThelper1]

I should bring up that Term2 is mapped to the Aloha folder on the server. It would not let me map BOOTDRV and access the Aloha folder inside, but it would let me map right to Aloha.

 

[posrescue]

I would say your bootdrv share on term1 / FILESERVER is not shared to max/everyone. Sorry, dont remember the symantics of Win 98 sharing.

 

[IThelper1]

I checked it out, but it does have everyone checked. That box I've not changed at all since we replaced Term2, so I know it was working before.

Just thinking maybe something is not pointed at the right dir.

Thanks!

 

[dauphin2]

Try adding ROBUST=TRUE to the ibercfg.bat file on Term2 if it is not already in there.

 

[IThelper1]

Looks like its in there. Here is what we have.

 

[TJFman]

Your Server variable should look like this:
SET SERVER=ALOHABOH
It does not need the slashes.

I have never seen the "SET PATH=" be used for Aloha. Your IberDir and LocalDir should be sufficient.

Everything else looks good.

 

[IThelper1]

Thanks TJFman. I made those changes, but still no luck.

Seems funny they can see each other, but not 100%.

 

[Knectech]

Verify the user login that you are using on both your terminals.

is Term1 logging in as Guest ? What is term2 logging in as?

You may need to configure terminal 1 to login as the same user with Client for Windows Networking set instead of using Winlogon.

knectech.com

 

[IThelper1]

They both are setup with the user TD. I'm not sure why the Server/Term1 box uses that, but I did not want to change anything on it because everything was working until the original Term2 died.

 

[posrescue]

Bet your server / terminal is not named ALOHABOH. Check that then change the ibercfg on term 2 to have set server=* to the correct computer name, probably term1.

 

[IThelper1]

It's set as ALOHABOH. I know the terminals can see each other in some form because when one is down the other gives that terminal down error on the login screen.

Thanks!

 

[posrescue]

I bet the problem is your termstring naming. If you look at your TERMSTR= in the ibercfg file above you see termstr=term on term2. What is the termstr= setting on the alohaboh/term1? If it is set to "term" then that would explain the issue as the network name on that computer is not the termstring followed by the terminal number.

The termstring is the name (alpha characters) that precedes the terminal number. TERMSTR=term TERM=2 is term2...

In most older systems where you are running FOH and BOH on the same computer you will see the computer name of the fileserver/terminal set to term1. TERMSTR=TERM. TERM=1. SERVER=term1. Since there is no EDC path in the ibercfg.bat I assume you are not running credit cards thru your Aloha so at least you don't have to worry about the EDC Path.

Since your fileserver / terminal is Win 98 there are no environment variables so those settings will all be in the ibercfg.bat.

Be carefull before changing anything on the fileserver/terminal as you don't want to dump that one as well...

 

[IThelper1]

Thanks posrescue. So I should change the server name to term1? I've left it's settings alone so far because everything worked with the old term2. I just did not know its settings.

You are right on credit cards. We are not running them through Aloha.