There is another terminal on the network with the same terminal number

[pcarter85]

does anyone know how to change the terminal id?
where is this file located?
how do i change it?
how do i set the id for the server? What is the server supposed to be.
i am running aloha 5.28?

 

[coorsman]

The term number is located in the ibercfg.bat file located usually in the aloha directory c:\aloha\
or in earlier versions it could be located on the root drive c:\

 

[coorsman]

also check the computer name it coincides with the terminal name.

 

[Circle9]

You also may have to change environment variables, if there are any on your terminal. I've attached a list of variables. You may need to edit the TERM variable.

 

[pcarter85]

i think i screwed this up a while ago
i didnt have the cd for aloha and i copied the files from term 3 to the server now there is a conflict
where is this file located on the server?
or the terminal id of the server?

 

[pcarter85]

i deleted the ibercfg file from the server but there is SOMETHING that it is reading that says there is a terminal id conflict
HELP!!!!

 

[pcarter85]

also where do i put these variables?
are they supposed to be the same on the server and workstation??
another strange thing is happening
term1 connects to the server fine. but term2-3 do not
i get the message looking for file server but it gets the master id fine
i deleted downtime.ini on term 3
i still get the message sometimes there is another terminal on the network
then the computer reboots
its like in a perpetual loop

 

[coorsman]

1. What type of terminal and operating system are you using.


Do a Stop front of house in aloha manager. This will stop the terminals from re-booting or just get all terminals to the desktop w/o iber running.

Depending on windows version - the machine name is located in control panel - system or in 98 it's located in the network settings. Each machine must be named with no spaces between the term name and the number "term1 term2".

The term number is also located in the ibercfg.bat file or sonetimes in the config.sys or autoexec.bat file. You edit these files and look for term=1 etc.

The IP scheme's last three digits must be different on each terminal or you will get an IP conflict.

 

[pcarter85]

i did ALL those things!
i get the message on terminal 3 and the server.
apparently the server has some files from term 3 when i copied it over.
what file should i be looking for on the server?
is it aloha.ini
i spent 4 hours on it last nite. first only term1 would connect to boh either after i closed out that computer or when i rebooted the server now NONE of the stations will connect. ctlserver will not start on the server because of the duplicate terminal id. any ideas. it a file on the server that has to be changed.

 

[pcarter85]

or what about if i name term3 term4
it shouldnt affect the license because there will still be three stations on the network right?

 

[pcarter85]

ok that didnt work!
now i get a message saying
terminal 4 not defined
where do i define it???

 

[coorsman]

Nope, can't do that.

The define would be in aloha manager. If you are licensed for 3 only 3 can run.

The term name in windows dosen't really matter but the term=? in the ibercfg.bat does.

Please let me know what win version you are on that would be helpful.

 

[pcarter85]

Aloha manager?
What's that?
The server is xp the computer it's conflicting with is xp
the other two terminals are windows 98.
Now the server won't start ctlsvr because of the conflict

 

[coorsman]

OK,
Lets start over

Your orignalpost you wanted to change the terminal ID... Why?. More information would be very helpful.

Did you get one repaired or buy a new terminal. There is several things to make a regular XP terminal work on an aloha network with other mixed operating systems ie 98 nd xp.

here are some tings to start with:
The terminals have an ibercfg.bat file that contains the following:

SET TERMSTR=TERM ' this is the string name of the terminals. before the term number "ie TERM3"

SET TERM=6 ' this is this term number - different for each terminal.

SET NUMTERMS=6 ' this is the number of terminal licensed or connected to the server.

SET SERVER=ALOHABOH ' his is the server machine name

SET MASTERCAPABLE=TRUE ' you can set this to false if having problems with win98 terminals rebooting.


SO....
by reading your current ibercfg.bat file on a terminal...

if "SET TERMSTR=TERM" then each terminal machine should be named TERM1 TERM2 TERM3 etc...

the SERVER(Back of house) should match the name in the terminals ibercfg.bat file SERVER="????????" usually, but not always alohaboh.....

To change the computer name in XP it's in - (control panel - system - computer name - change)the computer name for each terminal and the server.

in win98 its in control panel- network - identification -
check terminals for names term1 term2 etc.

The ip scheme should all be the same with the last 3 octets different ... possibly = xxx.xxx.xxx.101 term1 xxx.xxx.xxx.102 term2

mostly this is basic networking...

There are allot of other settings with aloha that can cause problems.

Other than that...
simple file sharing needs to be turned off, the terminal needs to have access to the network sharing and must be logged in with the correct username and passwords. Same as the other terminals and server. lanacfg must be set to 0 on the network card.

best of luck...
will monitor for your response...

 

[pcarter85]

thanx for your reply!
I did EACH and everything you just wrote and it still does not work
a year ago the server crashed
my employer doesnt have a contract with aloha for support anymore so he called me to figure it out.(inhouse tech) i had to restore his place and server without cds.
i was told that this was possible by reading this forum. i tried server 2003 with no success then eventually i settled on windows xp.
(i got it working eventually. after 2 weeks of pouring through these forums.)
in my process of trial and error i took the aloha folder from a terminal (term3)and overwrote the aloha folder on the server.
i used the term 3 aloha folder.
ever since then i would get the duplicate terminal error.
this went on for a year until finally one of the computers would just not work all together. it was either term3 or the server. the server would only become master when term3 was off.
my question was what file on the server do i have to change to get rid of the duplicate id message.
i reformatted the server and i am again starting a-fresh.....
but with the same corruppted data.
any suggestions?