When my front office terminal does an EOD and trys to reboot I get the 0x23 error. The network seems fine as I can ping the front office terminal. I can fix the problem by turning it completely off whic is a hassle. Is there any way to avoid the reboot after EOD. I tried putting in a delay but it does not seem to help.
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!
Dreaded 0x23 error after reboot
- Thread starter aloahuser
- Start date
- Thread starter
- #2
Some more info that might help. I had to replace the power supply with an OEM generic power supply. It seemed after that I started getting the 0x23 errors after a reboot. The network adapter is a Intel PRO 100. I looked for drivers but there all dated 2003. My terminal is a Radiant 1550. Another question would be is can I get a USB NIC and run it from there?
Are you running a terminal on the ALOHABOH machine? Thats what I think when you say Front Office Terminal (my system has front of house terminals and a non terminal ALOHABOH back of house server)
operating system?
aloha version?
debout might be nice
anyway.... sounds like a networking issue or a LANA number 0 issue
link to lanacfg with instructions attached never mind that it says windows 2000 use that instruction for XP (I am assuming XP or it's decendants)
You can use a USB nic as long as it is set to LANA 0 per the instructions
USB nics can be a pain because like all USB devices their configs can vary unexpectedly and a NIC set to LANA 0 can change on another day to something different. Not usually so with cards and onboards (but they too can have their fault issues that cause LANA to change)
As a quick work around you can stop a computer running Aloha terminal from rebooting at EOD BUT if you do not have it also set to autologin after logoff then Aloha terminal will not restart until someone manually logs in on the machine and if it is term 1 (usually your Master terminal) that will make some other machine on network become master depending on how you are setup.
If you want to set a machine to "autologin after logoff" do a google search for that. There are a lot of particulars to that and my typing sucks so i won't go into on this post
to make a terminal log off instead of reboot find ibercfg.bat on the computer it is running on and change REBOOTNT line. Its contents will look similar to this:
SET IBERROOT=Aloha
SET LOCALDIR=C:\cbbq\Aloha
SET CALIBRATE=C:\cbbq\Aloha\bin\calib.exe
SET EDCPATH=\\ALOHABOH\EDCSH\EDC
SET TERMSTR=TERM
SET TERM=4
SET NUMTERMS=4
SET SERVER=ALOHABOH
SET MASTERCAPABLE=TRUE
SET SERVERCAPABLE=TRUE
SET AUTOEXIT=TRUE
SET REBOOTNT=TRUE
COPY %LOCALDIR%\newbin\*.* %LOCALDIR%\bin
ECHO y | DEL %LOCALDIR%\newbin\*.*
START C:\cbbq\Aloha\BIN\IBER.EXE
CHANGE SET REBOOTNT=TRUE
TO SET REBOOTNT=FALSE
If this is a BOH server that is also running a terminal it is possible that ibercfg.bat is not used. In that case you will have to change the environment variable on the computer
rt click my computer click properties advanced tab
environment variables
system variables
use the edit button on the variable REBOOTNT and set it's value to FALSE
I find it odd that rebooting fixes this so you ought to look into the configuration of the problem computer. Make sure all your terminals log in using the same user account with appropriate permissions for accessing BOOTDRV share. I would also set CTLSVR and EDCSVR service to login using the same account.
On all machines make sure you can see and both read and write a file to the BOOTDRV share..... not just from 1 terminal to the BOH but from the BOH to each terminal and each terminal to every other terminal
If any machine has 2 NICS make sure you connect your ALOHA network to the LANA 0 NIC. A machine with 2 nics could be the root of your problem because bios could get reset when you replaced a power supply causing windows to redetect a NIC which could possibly cause a LANA change then maybe some other intermittent NIC problem or bad capacitor related problem. Check your bios battery, changes caused by power interruptions to a computer with a bad bios battery can cause odd problems.
lana.zip link has all the LANA stuff and info you need
operating system?
aloha version?
debout might be nice
anyway.... sounds like a networking issue or a LANA number 0 issue
link to lanacfg with instructions attached never mind that it says windows 2000 use that instruction for XP (I am assuming XP or it's decendants)
You can use a USB nic as long as it is set to LANA 0 per the instructions
USB nics can be a pain because like all USB devices their configs can vary unexpectedly and a NIC set to LANA 0 can change on another day to something different. Not usually so with cards and onboards (but they too can have their fault issues that cause LANA to change)
As a quick work around you can stop a computer running Aloha terminal from rebooting at EOD BUT if you do not have it also set to autologin after logoff then Aloha terminal will not restart until someone manually logs in on the machine and if it is term 1 (usually your Master terminal) that will make some other machine on network become master depending on how you are setup.
If you want to set a machine to "autologin after logoff" do a google search for that. There are a lot of particulars to that and my typing sucks so i won't go into on this post
to make a terminal log off instead of reboot find ibercfg.bat on the computer it is running on and change REBOOTNT line. Its contents will look similar to this:
SET IBERROOT=Aloha
SET LOCALDIR=C:\cbbq\Aloha
SET CALIBRATE=C:\cbbq\Aloha\bin\calib.exe
SET EDCPATH=\\ALOHABOH\EDCSH\EDC
SET TERMSTR=TERM
SET TERM=4
SET NUMTERMS=4
SET SERVER=ALOHABOH
SET MASTERCAPABLE=TRUE
SET SERVERCAPABLE=TRUE
SET AUTOEXIT=TRUE
SET REBOOTNT=TRUE
COPY %LOCALDIR%\newbin\*.* %LOCALDIR%\bin
ECHO y | DEL %LOCALDIR%\newbin\*.*
START C:\cbbq\Aloha\BIN\IBER.EXE
CHANGE SET REBOOTNT=TRUE
TO SET REBOOTNT=FALSE
If this is a BOH server that is also running a terminal it is possible that ibercfg.bat is not used. In that case you will have to change the environment variable on the computer
rt click my computer click properties advanced tab
environment variables
system variables
use the edit button on the variable REBOOTNT and set it's value to FALSE
I find it odd that rebooting fixes this so you ought to look into the configuration of the problem computer. Make sure all your terminals log in using the same user account with appropriate permissions for accessing BOOTDRV share. I would also set CTLSVR and EDCSVR service to login using the same account.
On all machines make sure you can see and both read and write a file to the BOOTDRV share..... not just from 1 terminal to the BOH but from the BOH to each terminal and each terminal to every other terminal
If any machine has 2 NICS make sure you connect your ALOHA network to the LANA 0 NIC. A machine with 2 nics could be the root of your problem because bios could get reset when you replaced a power supply causing windows to redetect a NIC which could possibly cause a LANA change then maybe some other intermittent NIC problem or bad capacitor related problem. Check your bios battery, changes caused by power interruptions to a computer with a bad bios battery can cause odd problems.
lana.zip link has all the LANA stuff and info you need
- Thread starter
- #4
Thanks for the help
My configuration consists of 1 FOH Radiant 1550 connected to my BOH server. The LANA stuff seems to be okay cause it I change it I consistently get the 0x23. The NIC LANA is set to 0. I only have one NIC card. The FOH logs in automatically so I believe it does not have a password. On both FOH and BOH I can see files on both systems.
Maybe its some kind of timing issue. I will try and put in some more delays and see if that works.
I have completely uninstalled my Network adapter and reinstalled it using the latest driver which is 2003 for the INTEL PRO 100.
My configuration consists of 1 FOH Radiant 1550 connected to my BOH server. The LANA stuff seems to be okay cause it I change it I consistently get the 0x23. The NIC LANA is set to 0. I only have one NIC card. The FOH logs in automatically so I believe it does not have a password. On both FOH and BOH I can see files on both systems.
Maybe its some kind of timing issue. I will try and put in some more delays and see if that works.
I have completely uninstalled my Network adapter and reinstalled it using the latest driver which is 2003 for the INTEL PRO 100.
FYI Seeing files and being able to write/delete/modify are two different things
As far as logging in with no password not a good thing PCI DSS compliance wise
run control userpasswords2 at the run dialog and that utility lets you set a password to automatically login with
I use the same username and password on all terminals register aloha services to login with same and give that user nt file access priviledges to read/write/modify you have to have simple filesharing off (another PCI DSS compliance)
good luck
As far as logging in with no password not a good thing PCI DSS compliance wise
run control userpasswords2 at the run dialog and that utility lets you set a password to automatically login with
I use the same username and password on all terminals register aloha services to login with same and give that user nt file access priviledges to read/write/modify you have to have simple filesharing off (another PCI DSS compliance)
good luck
- Thread starter
- #6
After doing a little more problem determination I see the following:
After I turn the FOH off and power it on the network connections show Local network 8(which is the one I configured and is LANA 0). When it does a reboot it comes up with a new network adapter Network adapter 10 which I did not define.(Local nework adapter 8 does not show up)
I guess the question is why does it not see local network 8 on a reboot.
After I turn the FOH off and power it on the network connections show Local network 8(which is the one I configured and is LANA 0). When it does a reboot it comes up with a new network adapter Network adapter 10 which I did not define.(Local nework adapter 8 does not show up)
I guess the question is why does it not see local network 8 on a reboot.
- Thread starter
- #7
Thanks for the help.
After I saw the Network adapter change depending on a reboot(Adapter 10)or power on/off(adapter11) I set Adapter 11 to LANA 0 reconfiged the TCPIP properties and then changed the IBERCFG so it would logoff instead of reboot. Now it stays on adapter 11 and everything seems to be working okay.
Finally no more 0x23 errors.
After I saw the Network adapter change depending on a reboot(Adapter 10)or power on/off(adapter11) I set Adapter 11 to LANA 0 reconfiged the TCPIP properties and then changed the IBERCFG so it would logoff instead of reboot. Now it stays on adapter 11 and everything seems to be working okay.
Finally no more 0x23 errors.
- Status