Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aloha POS File server connectivity issue 1

Status
Not open for further replies.

WildernessSB

Technical User
Sep 13, 2009
3
US
I am running Aloha Tableservice Version 5.3.47, one File server running XP pro, and 5 IBM SurePOS 500's running Win 98. Today when I went to refresh some info, 4 of the FOH compters rebooted normally but one did not. After some trouble shooting I traced it back to a bad harddrive. I replaced it with another 20 gig out of a spare, unused server computer, and it booted Windows just fine. When it went to boot Aloha, however, it took me to a "looking for fileserver" screen with a "Make fileserver" button and would go no further.

After doing some searching on this website (which is a great source of info BTW), it sounds as though the security card (or HASP key as some call it?) does not match up with whatever file is stored in this new hard drive, and is therefore not allowing connectivity. I pulled the security key and looked it over for some sort of number or ID or something, but found nothing.

Anyhow, does it sound like im on the right track or barking up the wrong tree? Any suggestions for getting the key and the HD to match up? Thanks in advance, your help is greatly appreciated as the $300/hr tech support is a bit out of the budget in these tough economic times.

Steve
 
If its of any help, this message pops up in Windows just before Aloha starts to boot...

"Error 53: The computer name specified in network path cannot be located. Make sure you are specifying this computer name correctly or try again later when the remote computer is available
 
You need to do a term install on the new terminal. Look for a directory on the drive called terminst. Run the setup program and follow prompts.

The computer name, must be correct for the terminal you are installing.

The ibercfg.bat file must have the correct paths and terminal numbers.
 
I have a new install of 5.3.9 on a Win 2003 server and every time I try to open Aloha Manager TS I'm asked for a password an loging yet I never set one up. Any suggestions? I can't find anywhere is the Backoffice suite that would help either.
 
Coorsman-

I tried to run terminst but when i hit the OK button its giving me an error message: (Aloha terminal installation cannot find iber.exe with the following path: \\ALOHABOH\BOOTDRV\Aloha\bin\iber.exe -Either server name is incorrect, or aloha path is incorrect, or BOH software not installed or network not working.)

I also looked into the ibercfg.bat file and it displayed the following..

C:\>Set Numterms=6
C:\>Set Server=AlohaBOH
C:\>Set Mastercapable=T
C:\>Set Servercapable=T
C:\>Set Double click=T
C:\>Set Autoexit=T
C:\>Copy C:\>Aloha\newbin\*.* C:\>Aloha\bin

File not foung - C:\Aloha\Newbin\*.*
0 files copied


Hope this helps?
 
Sorry, misread your post, I thought you were installing a new terminal harddrive.

Sounds like Networking issues:

Set the workgroup name the same on all terminals and the file server. generally uses IBERTECH as the workgroup name.

Set the file server/terminal's network name TERM1, TERM2.

Different TERMSTR names cannot be used within the same Aloha system. Spaces cannot be used, but underscores can. Leading zeros can be used if they are part of the TERMSTR, but it is not recommended.

use of static IP addresses

Assign lana number zero to the network binding (protocol and adaptor)

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software. To do this, access the TCP/IP properties for the Local Area Connection, click the Advanced button, and select the WINS tab. Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense
Windows XP uses Media Sense with TCP/IP to determine whether the network card is in a link state. If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.

File Sharing
The Aloha application software requires a network share labeled BOOTDRV that enables read and write capabilities to the Aloha application software file server and FOH terminals. This share needs to be applied to the root folder or drive in which the Aloha folder resides. If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV. If it resides in D:\ALOHA, share D:\ as BOOTDRV. If you created a special folder for the Aloha application software, share the special folder as BOOTDRV. For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.

enable file sharing before installing the Aloha application software.

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.
Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).


disable simple file sharing in order to enable user-level file sharing.

Open My Computer and select Tools/Folder Options/View. Enable 'Use Simple File Sharing' and click OK.
Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

Install Aloha Software

Run ADVANCED.EXE from the Aloha POS CD. The setup program walks you through the rest of the installation.

Once the installation is complete, you can edit user access to the BOOTDRV share if you have enabled user-level file sharing.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top