What determines MASTER and SERVER in Aloha start up? 3

[zsmitchell]

We have our Aloha server and 19 terminals in VLAN1, we have 1 terminal in VLAN2, and another terminal that we want to connect remotely via a VPN Tunnell (More on that one when we get to it.

I have enabled traffic between the two VLANs - I can ping IPS between vlans.

I updated the LMHOSTS files - I can ping TERM NAME between vlans.

I Installed the WINS service on server, and mapped the odd terminal in wins.

Still....Searching for master...

I have a feeling it has to do with RFSSRV or DCOM...can anybody point me in the right diection to get this terminal talking to the master and server.

Combining all terminals into one vlan is not an option.

Thank you!

Zack

 

[alohaakamai3]

Zack-

That's a tough one. Aloha can be kinda finicky when it comes to playing nice on the network or in complicated network setups (at least that's the way it used to be, I am sure it has improved over the years).

There are a couple of things that typically cause this problem, that probably *don't* apply to you hear, but I will list them anyway- maybe it will get your mind going in a different direction.

1- The Lana number is wrong on the terminal's network card. This is usually seen on the back office, but if you have two protocols bound to the NIC on the terminals- sometimes the protocol the protocol that Aloha is using will get a higher lana number, like 1 or 2- instead of zero, which is what it needs. The easiest way around this is usually to remove everything but the protocol you need for Aloha just to test it. It can also be changed with lanacfg.exe.

2- Somewhere in the terminals settings for Aloha (ibercfg.exe, autoexec.bat, or environment variables), there is a configuration error. You'll see if this, for example, if "Set Server=" is set to a different name than that of your file server or if the Termstr= is not the same as the rest of the terms.


The easiest way to make sure it's not a config problem is to physically move one of those units thats giving you a problem and try to bring it up locally and see if it comes up running on the local network where everything is good.

If all of the above requirement are satisfied, then you definitely have some "geeky" issue with the vlan that aloha doesn't like.

Was it ever working properly in this setup before?

 

[zsmitchell]

Yep, both of those are in order. Actually, we run this terminal for 20 days, and then bring it down the mountain and plug it into VLAN1 overnight, so that it will run another 21 days in standalone mode.

It has never worked like this (on the separate vlan) but I am tired of bringing this terminal down every 20 days...Did I mention it is a ski resort? Try sking down a mountain with a terminal on your back!

Zack

 

[alohaakamai3]

I would actually see if you can purchase or borrow and St. Bernard (generally about $600) where the terminal can be strapped to it's back, in order to make this task a little easier on you until the issue is resolve. They are a hearty working breed, proficient in carrying large loads in colder climates.


Regarding the POS issue- I don't want to speak for everyone on the board, since there are some people who do know this system very well. But, this sounds like one of those very "specific issues" that you will need your dealer for- who may not even know it themselves, but will at least have access to Radiant programmers to help you uncover what the stumbling here.

 

[coorsman]

Well, dogs aside, the remote terminal is looking for the master terminal. Aloha terminals all have to communicate to the master and have permissions to read and write to it. The Master is the only terminal that communicates with the server.

What windows version are you running on all terminals and can you read and write to all terminals?

 

[zsmitchell]

The Terminal are all running XP Pro, and the server is 2003. The terminals can all communicate with each other (both via ping IP and ping Name), and the LMHOSTS has been updated on all terminals.

St bernard's are messy to clean up after.

Zack

 

[zsmitchell]

Just re-read the thread...Read/write is enabled across all.

Zack

 

[coorsman]

Have you read the debouts for that termial?

 

[typethree]

Cool write up that many people will find useful!