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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
HELP! Installing Aloha 5.3.26 Error "failed to register station name"
- Thread starter novmode
- Start date
- Thread starter
- #2
Ok, so i've figured out it's some kind of network problem, looks to be netbios related. I've never installed Aloha before, but i have been using an older aloha system for about a year. I figured it was cut and dry, but with no included documentation, i'm a bit stumpted. Can anyone walk me through a quick install process for table service?
AkamaiAloha
MIS
I know this is more or less old news, but since it looks like your going to have your hands full with Aloha for a while, I figured I would chime in anyway. You're right-it is a network error, having something to do with the fact that Aloha is trying to perform an intial broadcast on the network, and it can't. The main practical reasons for this are as follows:
1) Your network cable is unplugged. This is the most common reason, and depends on the hardware. Sometimes when it's unplugged, it will keep "Determining Fileserver". With some hardware, if the cable is unplugged, you get that error.
2) There is no network card in the terminal. Nuff said.
3)Two copies of Iber are being launched, and you're getting this error because Aloha can't initialize the NIC the way it wants.
I am sure there are other reasons, but those are the most common.
1) Your network cable is unplugged. This is the most common reason, and depends on the hardware. Sometimes when it's unplugged, it will keep "Determining Fileserver". With some hardware, if the cable is unplugged, you get that error.
2) There is no network card in the terminal. Nuff said.
3)Two copies of Iber are being launched, and you're getting this error because Aloha can't initialize the NIC the way it wants.
I am sure there are other reasons, but those are the most common.
- Thread starter
- #4
Well, it's none of those, but thanks. It seems to me (after discovering the log files in /tmp) that the software is trying to use netbios, I'm installing on windows xp pro, and to be honest i have never used netbios and don't know how to set it up other than installing the protocol. From what i have read i would have to use a program called lanacfg that as far as i can tell is impossible to find, and not supported for use with windows xp.
How can i configure aloha for tcp/ip?
How can i configure aloha for tcp/ip?
AkamaiAloha
MIS
Wait, are you seeing this error message on the back of house??
That's unusual, and you're right, in that case it probably wouldn't be any of those, since Iber doesn't run on a dedicated fileserver. I am curious then, what was the problem (Disabling the MediaSense?)?
Honestly, I might steer clear of XP if I were you. I have used it and other guys on here have used it, and sometimes all is well. However, most of the guys on here have been working for Aloha dealers for years and are equipped to deal with the headaches. Win 2k is a safe bet with Aloha... if you have some other reason you want to use XP, then fine--but if it's just because it's latest and greatest, you're better of with 2k (IMO). For for one thing, you're using an "slightly" older version, and sometimes there are problems with the HASP drivers.
There is a way around the lanacfg thing I've used in the past that really hasn't failed me, in both 2k and XP. If you install XP or 2k with only one NIC, and and TCP/IP is the only protocol (this is the default installation setting), it will automatically make the Lana on TCP 0 and life is good.
That's unusual, and you're right, in that case it probably wouldn't be any of those, since Iber doesn't run on a dedicated fileserver. I am curious then, what was the problem (Disabling the MediaSense?)?
Honestly, I might steer clear of XP if I were you. I have used it and other guys on here have used it, and sometimes all is well. However, most of the guys on here have been working for Aloha dealers for years and are equipped to deal with the headaches. Win 2k is a safe bet with Aloha... if you have some other reason you want to use XP, then fine--but if it's just because it's latest and greatest, you're better of with 2k (IMO). For for one thing, you're using an "slightly" older version, and sometimes there are problems with the HASP drivers.
There is a way around the lanacfg thing I've used in the past that really hasn't failed me, in both 2k and XP. If you install XP or 2k with only one NIC, and and TCP/IP is the only protocol (this is the default installation setting), it will automatically make the Lana on TCP 0 and life is good.
First off, XP is just fine to use! I haven't experienced that many problems to say that the os is bad. You just can't be afraid to get your hands dirty. No offense, but I just think that you can't stay away from a good OS that has been out for 5 years. I would prefer XP over other OS's with aloha any day.
As far as your problem is concerned, can you post some of the debouts that you were talking about? I'm guessing that you are getting an error that says "too many netbios errors"? If this is correct then either you have a computer on the network with the same name, or you have two control servers running on the same network
Aloha uses netbios OVER tcp/ip, and that's why it's stating the netbios errors. Please post more info so we can help you, preferably from the debouts.
Adam
As far as your problem is concerned, can you post some of the debouts that you were talking about? I'm guessing that you are getting an error that says "too many netbios errors"? If this is correct then either you have a computer on the network with the same name, or you have two control servers running on the same network
Aloha uses netbios OVER tcp/ip, and that's why it's stating the netbios errors. Please post more info so we can help you, preferably from the debouts.
Adam
- Thread starter
- #7
AkamaiAloha
MIS
Sorry, I have to disagree with you on that Adam, and I am speaking from personal experience on this. For keys with the older HASP drivers, XP is NOT just fine to use. For you guys selling new Aloha systems, this is not an issue (Ezcrane and I just had a discussion about this)... with the new keys, you're right, it's usually not an issue. But if you have a significant number of XP systems running 5.0x and even some running lower versions of 5.2 (like this gentleman running 5.236), then please tell me your secret! 
I wasn't say the OS is bad--it's not, and I would far and away perfer to use it.
You actually made the point I was trying to make--if I were him, I would NOT want to get my hands dirty. It's one thing if you have access to all of Aloha's resources, and that's you're main foucs is dealing with Aloha. But it doesn't sound like this guy is going to want to spend hour after hour looking after an Aloha system.
Adamn is right about the TCP over Netbios. You'll still see those in the Debout no matter what protocol you're using.
I wasn't say the OS is bad--it's not, and I would far and away perfer to use it. You actually made the point I was trying to make--if I were him, I would NOT want to get my hands dirty. It's one thing if you have access to all of Aloha's resources, and that's you're main foucs is dealing with Aloha. But it doesn't sound like this guy is going to want to spend hour after hour looking after an Aloha system.
Adamn is right about the TCP over Netbios. You'll still see those in the Debout no matter what protocol you're using.
I understand your point, and I respect it. However I have used xp with old hasp drivers on older versions (client wants to upgrade their file server, etc.) with no problems. No secret or anything, I guess I'm just lucky!!
I'm curious on what problems you have with the older versions and hasp keys with XP? Please let me know, maybe I can help alleviate your problems.
Adam
I'm curious on what problems you have with the older versions and hasp keys with XP? Please let me know, maybe I can help alleviate your problems.
Adam
AkamaiAloha
MIS
Likewise Adam, I have no doubt you know what you're talking about, as do all the Aloha guys on here. In some cases, I think it's just a simple matter of what our experience is in. For example, my experience with Aloha QS is pretty limited. If someone asked me to come to their location to resolve a QS issue, I have no doubt that I could in 90% of cases. But, I am no where near as proficient compared to TS. That's just my market.
As it pertains to myself, I do not work for an Aloha dealer. That said, I see my fair share of clients that are still running 4.2x, 5.0x, 5.2x, etc. They may not want to upgrade their Aloha software--but as you mentioned--sometimes the server decides when it's time to upgrade the hardware, and not the customer. As such, I agree it's a good idea to get them on a newer OS when the file server finally does die. And generally speaking, my experience has been the older the Aloha software, the less likely Aloha will see the security key when running on an XP platform. On newer systems (within the last year or two), this is never an issue. Not only that, the number of issues I see with Aloha on XP vs. 2k is a no brainer--2k, almost zero problems, solid as a rock.
Does this mean that it's impossible to get older versions of Aloha to run on XP? Absolutely not--in fact, I would probably agrue the opposite--that someone determined to get 4.2 running on XP, who really understood the architecture beyond that which is required by a good tech, could do it if they were willing to dedicate the time. But most clients don't care what OS is on the back, since they only use it for Aloha (and we strongly advise this, as I am sure most of you guys do too). They just want it to work without hassles--as do I.
A while back, I posted on Tek-tips, asking if there was some kind of guideline with respect to which version should be using which OS, and the response I got was more or less that others had seen issues too, but couldn't say for sure when you need to use XP or 2k. Don't get me wrong--I would much prefer to use XP, if for no other reason that it finds most of the basic drivers for you, it's more user friendly, and I find it to be stable. At the same time, I think customers and techs sometimes get too caught up on what's considered "old", when sometimes it's just about what's get the job done. When something gets too old, it is a problem--for example, many programs, like Anti-virus, won't run on NT 4.0 anymore. But I have yet to see much that will run on XP that won't also run on 2k.
I was more or less assuming that the genteman who made the post was likely looking for the easiest solution (unless he's a full time Aloha dude), and in my opinion, that would be 2k. There are no doubt a lot of factors involved--the way the OS is setup, the way the Aloha software is installed, the type of hardware, etc. So I am in no way proclaiming that my experience is "the way it is". Just what I've seen.
As it pertains to myself, I do not work for an Aloha dealer. That said, I see my fair share of clients that are still running 4.2x, 5.0x, 5.2x, etc. They may not want to upgrade their Aloha software--but as you mentioned--sometimes the server decides when it's time to upgrade the hardware, and not the customer.
As such, I agree it's a good idea to get them on a newer OS when the file server finally does die. And generally speaking, my experience has been the older the Aloha software, the less likely Aloha will see the security key when running on an XP platform. On newer systems (within the last year or two), this is never an issue. Not only that, the number of issues I see with Aloha on XP vs. 2k is a no brainer--2k, almost zero problems, solid as a rock. Does this mean that it's impossible to get older versions of Aloha to run on XP? Absolutely not--in fact, I would probably agrue the opposite--that someone determined to get 4.2 running on XP, who really understood the architecture beyond that which is required by a good tech, could do it if they were willing to dedicate the time. But most clients don't care what OS is on the back, since they only use it for Aloha (and we strongly advise this, as I am sure most of you guys do too). They just want it to work without hassles--as do I.
A while back, I posted on Tek-tips, asking if there was some kind of guideline with respect to which version should be using which OS, and the response I got was more or less that others had seen issues too, but couldn't say for sure when you need to use XP or 2k. Don't get me wrong--I would much prefer to use XP, if for no other reason that it finds most of the basic drivers for you, it's more user friendly, and I find it to be stable. At the same time, I think customers and techs sometimes get too caught up on what's considered "old", when sometimes it's just about what's get the job done. When something gets too old, it is a problem--for example, many programs, like Anti-virus, won't run on NT 4.0 anymore. But I have yet to see much that will run on XP that won't also run on 2k.
I was more or less assuming that the genteman who made the post was likely looking for the easiest solution (unless he's a full time Aloha dude), and in my opinion, that would be 2k. There are no doubt a lot of factors involved--the way the OS is setup, the way the Aloha software is installed, the type of hardware, etc. So I am in no way proclaiming that my experience is "the way it is". Just what I've seen.
- Status
Similar threads
- Question
