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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Aloha QS- Too many netbios errors

Status
Not open for further replies.

remraf12

IS-IT--Management
Mar 20, 2007
7
US
In the last year we upgraded to version 5.3 and started getting these errors. I've worke with the local dealer's support but have been unable to resolve the problem. The terminals will flash "too many netbios errors" and reboot daily at this point.

I've tried:
had network cabling checked
replaced one of two switches
2 of 3 terminals have recently been replaced with radian 1510
(the other terminal runs windows 2000 on generic pc)
checked all network settings
I have no errors in event logs for windows on any terminal or office computer

We have a total of 5 terminals with a 2k server running as an interface terminal.

I'm at a loss for fixing it. It has become a problem since daily at lunch they reboot and usually lose an order or two during the rush. I constantly get calls when they reboot since most staff don't understand they'll come back up.

I'll paste some info from the debout on a non master terminal.


localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:15 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:15 [1080] Removing master 2 from termstatus
Mar 16, 11:36:15 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:15 [1080] Dropping master...
Mar 16, 11:36:15 [1080] HANGUP succeeded
Mar 16, 11:36:15 [1080] RECEIVE failure: node 2 code 0A command 95
Mar 16, 11:36:16 [1080] Creating terminal status for 2
Mar 16, 11:36:16 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:16 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:16 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:19 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:21 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:21 [1080] Removing master 2 from termstatus
Mar 16, 11:36:21 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:23 [1080] Creating terminal status for 2
Mar 16, 11:36:23 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:23 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:23 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:26 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:27 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:27 [1080] Removing master 2 from termstatus
Mar 16, 11:36:27 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:27 [1080] Creating terminal status for 2
Mar 16, 11:36:27 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:27 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:29 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:32 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:33 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:33 [1080] Removing master 2 from termstatus
Mar 16, 11:36:33 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:33 [1080] Creating terminal status for 2
Mar 16, 11:36:33 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:33 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:35 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:38 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:39 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:39 [1080] Removing master 2 from termstatus
Mar 16, 11:36:39 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:39 [1080] Creating terminal status for 2
Mar 16, 11:36:39 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:39 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:41 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:44 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:45 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:45 [1080] Removing master 2 from termstatus
Mar 16, 11:36:45 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:45 [1080] Creating terminal status for 2
Mar 16, 11:36:45 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:45 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:47 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:50 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:51 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:51 [1080] Removing master 2 from termstatus
Mar 16, 11:36:51 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:51 [1080] Creating terminal status for 2
Mar 16, 11:36:51 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:51 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:53 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:56 [1080] CALL: node 2 retcode 40
Mar 16, 11:36:57 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:36:57 [1080] Removing master 2 from termstatus
Mar 16, 11:36:57 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:36:57 [1080] Creating terminal status for 2
Mar 16, 11:36:57 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:36:57 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:36:59 [1080] CALL: node 2 retcode 40
Mar 16, 11:37:02 [1080] CALL: node 2 retcode 40
Mar 16, 11:37:03 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:37:03 [1080] Removing master 2 from termstatus
Mar 16, 11:37:03 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:37:04 [1080] Creating terminal status for 2
Mar 16, 11:37:04 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:37:04 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:37:05 [1080] CALL: node 2 retcode 40
Mar 16, 11:37:08 [1080] CALL: node 2 retcode 40
Mar 16, 11:37:09 [1080] Couldn't find \\TERM2... assuming master down
Mar 16, 11:37:09 [1080] Removing master 2 from termstatus
Mar 16, 11:37:09 [1080] Enter localState[gLocalStateIndex].state SLimbo
Mar 16, 11:37:10 [1080] Creating terminal status for 2
Mar 16, 11:37:10 [1080] Limbo: terminal 2 asserts it is master
Mar 16, 11:37:10 [1080] Exit localState[gLocalStateIndex].state SLimbo: master 2 fileserver 'TERM100' localState[gLocalStateIndex].state 23 (server TERM100)
Mar 16, 11:37:11 [1080] CALL: node 2 retcode 40
Mar 16, 11:37:11 [1080] Too many NetBIOS errors (31). REBOOTING THIS TERMINAL!
Mar 16, 11:37:11 [1080] Find the cause of the errors and fix it (recommended)
Mar 16, 11:37:11 [1080] or use NetBIOSErrorThreshold=xx in ALOHA.INI to change threshold (NOT recommended).

Thanks in advance for any help
 
Two things I would try:

Aloha is kind of rough on network traffic. The terminals are continuously scanning to see if they can see the master.

1) Try making only 2 of terminals master capable in the ibercfg.bat. In other words, edit the file on 3 of those terminals and set MASTER CAPABLE=FALSE and SERVER CAPABLE=FALSE.

We've seen this fix strange problems on quite a few sites over the years.

2) I am assuming your using TCP/IP. If so, set the default gateway on those terminals to that of the ALOHABOH server's IP address. This will also reduce the amount of broadcasting terminals may do to find out who they are.

Try those two things and report back, there are 1 or 2 other things you can try if that doesnt work.

 
I've already done the master capable step.

Curious, all the terminals have the default gateway set to the routers ip address (we have a seperate switch) and the dns entries are those of our isp. Since we're not running a domain couldn't we remove the default gateway and dns entries from all the terminals and see what happens?

Thanks for the reply
 
Do any of you guys know what goes on when you connect to a host? I am writing a front end and have EDC but when it connects, it immediately disconnects. Without a spec, I thought I could figure it out but there is nothing to scope.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top