Need ideas for Aloha master on large site

[alohaakamai3]

I am still trying to figure out what to do with this situation and advice would be appreciated.

I have a mixed mode of hardware and operating systems, mainly XP and 98.

When we turn on the 9th or 10th terminal, some of the stations start to intermittently flash between the floating logo that it should have and a "Cannot Locate Master" error.

I assume this is because the OS is XP Pro, which has a 10 connection limit. (the back office is win2k server, plenty of licenses there)

I figured I would just make a Win98 machine master, but when I do, I get an Error message that says "Too many netbios errors" and it reboots.

So far, all I have done is limit how many terminals can be master to reduce network throughput, and added the old vnetbios patch and edited the NUMHCBS=100 on the 98 machines.

Does anyone have any other suggestions so that all of these computers play nice together?

 

[coorsman]

What version of Aloha - do you have RFS running?

 

[alohahello]

yes you are correct windows xp sp2 has the 10 concurrent conncection limit. You need win98 to be master to exceed that limit. What version vnetbios file are you using?

 

[DTSMAN]

RFS overides that. It is the work-around for the connection limit. You can chose to install this when installing the software now. The Win98 master still works as a solution.

Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com

 

[alohahello]

yea but rfs is only in 6.X and above. Running Win2k server with 98 as the master can run more then 10 terminals. This was the way around the XP connection limit before rfs came out. This method was used for 5.x sites. anything running 6.X should be xp or up.

 

[coorsman]

how many xp units do you have on the entire network add one for edc, over 9 and you will need rfs in verzion 6.0 and up.

 

[alohahello]

i think ctlsvr counts as a concurrent connection as well. we usually rfs at 8 terminals and up.

 

[alohahello]

try updating to 98 second edition. that should fix your vnetbios error.