alohaakamai3
IS-IT--Management
Hi guys,
I’ll get right to the question, with an explanation of the problem below if you feel like reading it, but what I really need to know is: I know there is a connection limit of 10 on XP Pro computers, and when you cross that threshold with terminals trying to connect to the master on aloha systems, I know you can run into “cannot locate master and other network anomalies. I know one solution on large sites is to put something like Win2kServer on one of the terminals and make it be master, but I thought someone responded before by saying that Aloha released a patch or edit (or maybe even a version release) that got around this issue.
What’s the number of Aloha computers on can have with XP pro as master with Aloha, and does such a work around exist?
Here the details surround exactly what’s going on for further explanation:
We’ve got a larger Aloha client (12 terms) that has been without some computers for a while due to remodeling and not using certain areas of the restaurant for some time.
Now that we are including those stations once again (some of which are new units), we’re getting some terminals that occasionally flash “Cannot Locate Master” periodically and similar loss of connection/network anomalies. On slower business volume nights or when some of the computers are off, it’s usually not an issue. It’s a mixed mode of WinXp, Win98, and Win2k terminals.
In general, I believe things to be setup properly, including the patches for Windows 98, etc, and network information looks ok. I know I used to see this problem I some locations where all computers were allowed to me MASTER CAPABLE, and I am in the process of turning that off on all but a few terminals now. But I was actually starting to wonder if it might be this connection limitation issue- and even if it’s not, I’d like to know for future reference.
Thanks!
I’ll get right to the question, with an explanation of the problem below if you feel like reading it, but what I really need to know is: I know there is a connection limit of 10 on XP Pro computers, and when you cross that threshold with terminals trying to connect to the master on aloha systems, I know you can run into “cannot locate master and other network anomalies. I know one solution on large sites is to put something like Win2kServer on one of the terminals and make it be master, but I thought someone responded before by saying that Aloha released a patch or edit (or maybe even a version release) that got around this issue.
What’s the number of Aloha computers on can have with XP pro as master with Aloha, and does such a work around exist?
Here the details surround exactly what’s going on for further explanation:
We’ve got a larger Aloha client (12 terms) that has been without some computers for a while due to remodeling and not using certain areas of the restaurant for some time.
Now that we are including those stations once again (some of which are new units), we’re getting some terminals that occasionally flash “Cannot Locate Master” periodically and similar loss of connection/network anomalies. On slower business volume nights or when some of the computers are off, it’s usually not an issue. It’s a mixed mode of WinXp, Win98, and Win2k terminals.
In general, I believe things to be setup properly, including the patches for Windows 98, etc, and network information looks ok. I know I used to see this problem I some locations where all computers were allowed to me MASTER CAPABLE, and I am in the process of turning that off on all but a few terminals now. But I was actually starting to wonder if it might be this connection limitation issue- and even if it’s not, I’d like to know for future reference.
Thanks!