Aloha terminal failed to register station name error 23 in mixed Win 7 / XP environment 1

[360fish]

A Win7 aloha FOH term throws a name registration error whenever it is *rebooted* (either at EOD or manually) but if it is shut down then restarted it works normally.

DHCP Media Sense is disabled both directly in the registry and via the Net commands. IPv6 is disabled in the registry with all IP6 related services turned off. TCP/IP v4 on the nic is lana 0. The master terminal and server both run XP and there is only one Win7 term on the network. User names, service registrations, network sharing are identical and all working normally. Aloha version 6.1.x. Debouts simply show the error 23, nothing else useful.

Any ideas appreciated.

 

[dauphin2]

It sounds like you know what you're doing, so I won't ask the basic questions. 0x23 is definitely a NIC related issue, is it possible the network is not fully up before iber starts up? when you say *rebooted*, do you mean a refresh? Is your REBOOTNT variable true or false? I want to say I had this same issue on a Win7 terminal, but I can't remember exactly what it was.

alohapos

 

[360fish]

Dauphin2 - It's a weird problem, your questions are good. The terminal will always through a station name error when you choose reboot from the start menu (plugging in a keyboard, etc.) or when it is rebooted from the shutdown command (end of day) or from refresh. If you choose shut down from the start menu or by pressing the power button, then restart it from a full shut down, it comes up normally with no network error.

This happens regardless of the status of the rest of the network. RebootNT is true. If you can remember a tiny bit about the issue you had before it might help. I'll post again if I figure it out...

 

[dauphin2]

Is it possible the NIC is bad, do you have a spare one you can try?

 

[360fish]

SOLVED Ibercfg.bat was completing before windows networking had completed starting up. Even with DHCP Media Sense totally disabled Aloha was failing as if there was no network card or networking was not installed correctly.

I added the following to the beginning of ibercfg.bat to fix the issue

timeout /t 10

This inserts a 10 second pause before the batch file starts to execute, enough time for the the rest of windows networking to do... whatever it is doing for Iber to see it.

 

[dauphin2]

Awesome, that was my first guess. Maybe that's the issue I couldn't remember