ALOHA 5.3 NOT CONNECTED ISSUE

[PositiveD]

Hello Everyone,

I've worked with ALOHA now for 1 year and ever since my arrival at my
current company I've heard nothing but complaints in regards to a NOT
CONNECTED issue.
I'm hoping to gain some insight from this group on how adress this issue and
resolve it once and for all.

***A little background****
We currenlty have 65 stores all running v5.3 and mixture of Win2k WinXP and
WinXPe devices.

***The problem***
On a daily basis 5 to 10 stores with at least 1 terminal each that will boot
after the EOD and not be able to connect to the MASTER terminal and
displays a NOT CONNECTED message.
Logging off the terminal or rebooting it will not solve the problem.

This is having a HUGE negative affect on our business. It takes approx 30 to
get it back online.

***Our diganostics***
While the error occurs, have have full access to the MASTER terminal as well
as the FILE SERVER. We can read and write files to either one.

The master never looses network connectivity.

The LANAMGR reports the terminal and server to be bound to Interface 0

***Temporary fix***
The only way we are able to temporarily allow the terminal to reconnect it to
log off ALL the terminals. Allow 1 terminal to log on and establish as
MASTER, then load the other terminals.

This situation has become very frustrating and we are simply running around
in circles.
I'm hoping that with the power and experience of many we might be able to
resolve this.

Thanks in advance

 

[DTSMAN]

This is where I have seen this. If one of the XPe machines becomes master in a mixed OS arrangement it can cause that issues. They reboot to fast after the refresh and don't let the other terminals connect to them as they should.
How many terminals at each location?
Try this, pick 2 stations, preferably the ones with XP on them and leave them set to server and master capable. Turn it off on all the others in their ini files. Try that and you you will likely see some positive results.


Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com

 

[coorsman]

To turn off master and server capable edit the ibercfg.bat file on each XPe terminal and change the
SET MASTERCAPABLE=TRUE to FALSE
SET SERVERCAPABLE=TRUE to FALSE

 

[matthewdmiller]

if you are interested in having Aloha quesitons answered @ your fingertips please give me a call

Matthew Miller
602-791-6969

http://www.greenlinkmgmt.com

 

[PositiveD]

Just to clarify.
We have standerdized the OS version at each location, but we have locations with each OS.
Each location either has ALL W2K, ALL XP or ALL XPe machines.

The issues is OS independent, it's hapening on any of the stores.

We have tried in the past to force one or another terminal as master, but the issue remains.