Changing Lana number
-
Our sites have to be set to Lana 0 to run properly. ( Local Area Network Adapter Setting)
Had a site with a power surge last night and they dont run with battery backups apparently, (I know. I made a fuss about it) but it reset his lana number.On windows 10 : Open Command Prompt as Admin,
C:\WMIC nicconfig get description, SettingID
I find my Nic Card that we use, by name
after that :
Run> regedit> HKLM>System>controlset001>Services>NetBIOS>LInkageBind: find the Nic card name, cut it from current position, enter down from top, and paste into position.
Check lana map to be sure it say 01 00 for the first slot in the map, restart computer.Posting so its easier for me to find and if you guys can come up with a quicker way to do so.
-
What the heck are you doing that makes you need a LANA number?
-
Our terminals run dual Nics, one for internet and the other for the "closed" network we run out system on. On the software required list we get from our vendor (I know. I know. ) We have to set our LANA number to 0 that runs our "closed" network adapter. If it's not on 0, we have problems with the system, such as the system keeps rebooting, and terminals aren't able to fully boot up.
-
@wrcombs said in Changing Lana number:
Our terminals run dual Nics, one for internet and the other for the "closed" network we run out system on. On the software required list we get from our vendor (I know. I know. ) We have to set our LANA number to 0 that runs our "closed" network adapter. If it's not on 0, we have problems with the system, such as the system keeps rebooting, and terminals aren't able to fully boot up.
This implies that you are running on a pre-Internet system. LANA numbers were never needed in the IP era.
-
@scottalanmiller said in Changing Lana number:
@wrcombs said in Changing Lana number:
Our terminals run dual Nics, one for internet and the other for the "closed" network we run out system on. On the software required list we get from our vendor (I know. I know. ) We have to set our LANA number to 0 that runs our "closed" network adapter. If it's not on 0, we have problems with the system, such as the system keeps rebooting, and terminals aren't able to fully boot up.
This implies that you are running on a pre-Internet system. LANA numbers were never needed in the IP era.
I would agree, however, the only internet we use is to connect into the site via Remote Desktop Agent, so is it possible that it's because we aren't using IPv6? I know that most of our terminals run XP and only a hand full run Window 8-10 .. I guess I don't understand the importance of LANA numbers, but I know that if they aren't set correctly our system doesn't work.
-
@wrcombs said in Changing Lana number:
@scottalanmiller said in Changing Lana number:
@wrcombs said in Changing Lana number:
Our terminals run dual Nics, one for internet and the other for the "closed" network we run out system on. On the software required list we get from our vendor (I know. I know. ) We have to set our LANA number to 0 that runs our "closed" network adapter. If it's not on 0, we have problems with the system, such as the system keeps rebooting, and terminals aren't able to fully boot up.
This implies that you are running on a pre-Internet system. LANA numbers were never needed in the IP era.
I would agree, however, the only internet we use is to connect into the site via Remote Desktop Agent, so is it possible that it's because we aren't using IPv6?
So Internet Protocol and "the Internet" are not the same things. And "no one" uses IPv6.
In the real world, it's been IPv4 for decades. All networks are IPv4. Everything. It's so universal that people don't even remember that anything else like IPX/SPX or NetBEUI existed. Just like how Ethernet is now so universal that people forget we used to have alternatives like Token Ring.
LANA is part of NetBEUI - predating the adoption of Internet Protocol (IPv4) as the networking system of choice for... everything.
This is a degree of so outdated and so crazy that I'm not sure we have the terminology to express it to you. This is "old stuff we used to hear rumors of" twenty years before you first looked at IT.
-
@scottalanmiller said in Changing Lana number:
@wrcombs said in Changing Lana number:
@scottalanmiller said in Changing Lana number:
@wrcombs said in Changing Lana number:
Our terminals run dual Nics, one for internet and the other for the "closed" network we run out system on. On the software required list we get from our vendor (I know. I know. ) We have to set our LANA number to 0 that runs our "closed" network adapter. If it's not on 0, we have problems with the system, such as the system keeps rebooting, and terminals aren't able to fully boot up.
This implies that you are running on a pre-Internet system. LANA numbers were never needed in the IP era.
I would agree, however, the only internet we use is to connect into the site via Remote Desktop Agent, so is it possible that it's because we aren't using IPv6?
So Internet Protocol and "the Internet" are not the same things. And "no one" uses IPv6.
In the real world, it's been IPv4 for decades. All networks are IPv4. Everything. It's so universal that people don't even remember that anything else like IPX/SPX or NetBEUI existed. Just like how Ethernet is now so universal that people forget we used to have alternatives like Token Ring.
LANA is part of NetBEUI - predating the adoption of Internet Protocol (IPv4) as the networking system of choice for... everything.
This is a degree of so outdated and so crazy that I'm not sure we have the terminology to express it to you. This is "old stuff we used to hear rumors of" twenty years before you first looked at IT.
So it's an outdated internet protocol, that no one uses except PoS systems?
-
@wrcombs said in Changing Lana number:
I guess I don't understand the importance of LANA numbers, but I know that if they aren't set correctly our system doesn't work.
LANA hasn't existed in networking for decades. And when it did, it was for home workground networking in tiny itty bitty Windows only systems. Think Windows 95 and older, like Windows for Workgrounps 3.11.
Microsoft maintained support for it through Windows XP, but it was ancient and insane even by Windows NT 4 (1996.)
https://msdn.microsoft.com/en-us/library/bb870907(v=vs.85).aspx
Windows Vista and later don't even have support for NetBIOS which is what LANA is a part of.
-
@wrcombs said in Changing Lana number:
@scottalanmiller said in Changing Lana number:
@wrcombs said in Changing Lana number:
@scottalanmiller said in Changing Lana number:
@wrcombs said in Changing Lana number:
Our terminals run dual Nics, one for internet and the other for the "closed" network we run out system on. On the software required list we get from our vendor (I know. I know. ) We have to set our LANA number to 0 that runs our "closed" network adapter. If it's not on 0, we have problems with the system, such as the system keeps rebooting, and terminals aren't able to fully boot up.
This implies that you are running on a pre-Internet system. LANA numbers were never needed in the IP era.
I would agree, however, the only internet we use is to connect into the site via Remote Desktop Agent, so is it possible that it's because we aren't using IPv6?
So Internet Protocol and "the Internet" are not the same things. And "no one" uses IPv6.
In the real world, it's been IPv4 for decades. All networks are IPv4. Everything. It's so universal that people don't even remember that anything else like IPX/SPX or NetBEUI existed. Just like how Ethernet is now so universal that people forget we used to have alternatives like Token Ring.
LANA is part of NetBEUI - predating the adoption of Internet Protocol (IPv4) as the networking system of choice for... everything.
This is a degree of so outdated and so crazy that I'm not sure we have the terminology to express it to you. This is "old stuff we used to hear rumors of" twenty years before you first looked at IT.
So it's an outdated internet protocol, that no one uses except PoS systems?
No, it's an outdated NETWORK protocol. The Internet only uses Internet protocol. LANA was part of NetBIOS which was part of NetBEUI which was a LAN protocol. Alternatives to IP cannot go on the Internet at all, because the Internet is an interconnection of IP networks.
NetBEUI is further not even a WAN protocol. So let's make a hierarchy....
Internet Protocols: Can do WAN or LAN, and can go on the Internet. This is IPv4 and recently IPv6 only. Nothing else, ever.
Internetwork Protocols: Protocols like IPX/SPX that can connect one network to another, but cannot talk to the Internet.
LAN Protocols: NetBEUI is basically the only one. A silly idea that networks would never need to talk to each other so has no concept of "another network" and can only have about ten machines talk to themselves and never anything else.
-
@wrcombs said in Changing Lana number:
... that no one uses except PoS systems?
No one uses, period. Something is wrong on your network.
-
Just for some dates...
NetBIOS LANA was dropped for legacy support at Windows XP. That was the last hurrah for NetBIOS and it was a joke for a long time by then.
NetBEUI was dropped with Windows 2000. It was never a serious protocol, but they kept support until 2000 to allow people on ridiculous Windows 3.11, 95 and 98 networks to switch over before making them go to IP.
LANA's last time to be configured was 1996's Windows NT4.
We are not a full 22 years since MS had not only told everyone to go to IP, but the last configurable alternative was dropped.
-
Today, NetBIOS can be used for some really silly stuff over IP using the NBT extension. But it should not use LANA numbers.
-
@wrcombs said in Changing Lana number:
Our terminals run dual Nics, one for internet and the other for the "closed" network we run out system on.
This makes sense from a "why is it happening" stand point. But makes no sense how anyone allowed software like this to get made or deployed.
Somehow, NetBIOS is being used for part of the application. The LANA number is what ties NetBIOS to a protocol and adapter.
-
Thank you for the information, however, not everybody got the memo to quit using LANA and move to IP. Seeing how it's a huge part of the system for us, it's something that we use everyday and our sites use everyday as well. For our system to communicate within it's self LANA numbers are set to
lana0on all of our terminals, and the Back office PC that we provide as a "server". I understand that there should be an easier fix to it, but it's what we use on our windows only small work group. It works great until user error or power error, then we have to reset it. Also Windows updates kick LANA numbers around. -
@wrcombs said in Changing Lana number:
I know that most of our terminals run XP ....
-
@wrcombs said in Changing Lana number:
Thank you for the information, however, not everybody got the memo to quit using LANA and move to IP.
Yes, they did. Don't make excuses for inexcusable behaviour. If there is one lesson to be learned from where you are working now, it's that you have to stop pretending that there are valid reasons or excuses for how things are being done.
They are breaching their PCI contracts, they are putting customers at risk, they are acting incredibly unprofessionally and unethically. There are no excuses for their decisions. They have agree to not do this contractually and have legal obligations to not do this; as IT professionals they have ethical obligations to not do this.
Call it what it is - unethical and inexcusable.
-
@wrcombs said in Changing Lana number:
Also Windows updates kick LANA numbers around.
By design. Whoever built this system designed it to not work. It's not SUPPOSED to work they way it is being used. So it's not really broken, it's actually supposed to not keep working.
-
One of the major issues that IT pros tend to run into is wanting to excuse incompetence or unethical behaviour in other people. Calling them uneducated, too stupid to understand, not given the budget to do things right, whatever. We are pressured to not be honest and call out unethical or unprofessional behaviour when it happens and this is often our undoing.
There is little you can do here, you aren't in charge, you aren't in the path of authority, and you have little to gain by rocking the boat. But you DO have a chance to grow and learn. But to do so, you have to first not accept this behaviour, not excuse it, not act like someone "didn't know better" or that breaking contracts and risking customer data is okay.
What you need to take away from this is that lots of people in business and IT management are crooks and will do anything to line their own pockets and save their own necks. Identify it for what it is, people putting customers at risk for their own profits. People secretly violating their obligations to credit card processors and banks to make a quick buck. They are bad people, doing bad things. We all deal with this stuff every day. Sometimes we can fix it, sometimes we can't. But the one thing we can always do is understand it and identify it and make sure we never, ever make excuses for it. Making excuses empowers people and makes you not correctly evaluate situations.
-
@scottalanmiller said in Changing Lana number:
@wrcombs said in Changing Lana number:
Thank you for the information, however, not everybody got the memo to quit using LANA and move to IP.
Yes, they did. Don't make excuses for inexcusable behaviour. If there is one lesson to be learned from where you are working now, it's that you have to stop pretending that there are valid reasons or excuses for how things are being done.
They are breaching their PCI contracts, they are putting customers at risk, they are acting incredibly unprofessionally and unethically. There are no excuses for their decisions. They have agree to not do this contractually and have legal obligations to not do this; as IT professionals they have ethical obligations to not do this.
Call it what it is - unethical and inexcusable.
The only reason I post in ML when I have questions or am unclear on things is because of the level of intelligence in the community, it's the only way I can learn. I take what is being told to me here and take it to the table at work during our meetings. I do my best to make the office understand the points being brought up. But they also have a " your new, you don't understand " mantaility. So everything I say goes in one ear and out the other, I understand what your saying, I'm not making excuses , I'm relying information back to as best I can from my chain of command if you will, I get information, I send it up, it gets tossed around and I get an answer back.
-
The most common way that this is done that I see is that it has become the socially accepted approach for IT pros to feel "superior" and call all other people idiots and pretend that they are all totally stupid to the point of having zero knowledge of or control of their own actions. This is, of course, completely absurd. People doing well, making good money, running profitable businesses, feeding themselves, owning nice houses... generally are decently smart.
It makes IT Pros feel good to act like everyone else is "too dumb" to have common sense or any clue what is going on, but in reality this is not even slightly true and is honestly just misplaced elitism. It's two factors - IT pros often feel badly that we aren't earning as much as people doing bad things and want to excuse our own lack of success; while it being socially unacceptable to call out unethical behaviour but acceptable to think that people are walking zombies with no brain functions - especially in America where being uneducated and illiterate is often a badge of honour.
But what is really going on 99% of the time is someone who is very competent and very aware and just unethical. It makes us feel better to excuse people as being idiots compared to being scumbags. But the latter is way, way more common. The average person will steal if they think that they can get away with it, they will take advantage of nearly anyone, they will cheat and do anything for personal gain - as long as the risks are low. And that's what we see here.
No one is going to call them out for even this obvious money grab at customers' expense. There's no cluelessness here, there is just shitty human beings seeing a way to take advantage of people who have no visibility into how they are being cheated.
