Jump to content

Recommended Posts

Posted

NetBIOS is an acronym for Network Basic Input/Output System. It provides services related to the session layer of the OSI model allowing applications on separate computers to communicate over a local area network. As strictly an API, NetBIOS is not a networking protocol. Older operating systems ran NetBIOS over IEEE 802.2 and IPX/SPX using the NetBIOS Frames (NBF) and NetBIOS over IPX/SPX (NBX) protocols, respectively. In modern networks, NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol. This results in each computer in the network having both a NetBIOS name and an IP address corresponding to a (possibly different) host name.

Posted

NetBIOS is an acronym for Network Basic Input/Output System. It provides services related to the session layer of the OSI model allowing applications on separate computers to communicate over a local area network. As strictly an API, NetBIOS is not a networking protocol. Older operating systems ran NetBIOS over IEEE 802.2 and IPX/SPX using the NetBIOS Frames (NBF) and NetBIOS over IPX/SPX (NBX) protocols, respectively. In modern networks, NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol. This results in each computer in the network having both a NetBIOS name and an IP address corresponding to a (possibly different) host name.

sta ellhnika parakalw magka :P
Posted

NetBIOS was developed in 1983 by Sytek Inc. as an API for software communication over IBM's PC-Network LAN technology. On PC-Network, as an API alone, NetBIOS relied on proprietary Sytek networking protocols for communication over the wire. Because PC-Network only supported up to 80 devices in its most accommodating mode (baseband), NetBIOS was itself designed with limited nodes in mind.

 

In 1985, IBM went forward with the token ring network scheme and a NetBIOS emulator was produced to allow NetBIOS-aware applications from the PC-Network era to work over this new design. This emulator, named NetBIOS Extended User Interface (NetBEUI), expanded the base NetBIOS API with, among other things, the ability to deal with the greater node capacity of token ring. A new networking protocol, NBF, was simultaneously produced to allow NetBEUI (NetBIOS) to provide its services over token ring — specifically, at the IEEE 802.2 Logical Link Control layer.

 

Also in 1985, Microsoft created a NetBIOS implementation for its MS-NET networking technology. As in the case of IBM's token ring, the services of Microsoft's NetBIOS implementation were provided over the IEEE 802.2 Logical Link Control layer by the NBF protocol.

 

In 1986, Novell released Advanced Novell NetWare 2.0 featuring the company's own NetBIOS emulator. Its services were encapsulated within NetWare's IPX/SPX protocol using the NetBIOS over IPX/SPX (NBX) protocol.

 

In 1987, a method of encapsulating NetBIOS in TCP and UDP packets, NetBIOS over TCP/IP (NBT), was published. It was described in RFC 1001 ("Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods") and RFC 1002 ("Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications"). The NBT protocol was developed in order to "allow an implementation [of NetBIOS applications] to be built on virtually any type of system where the TCP/IP protocol suite is available," and to "allow NetBIOS interoperation in the Internet."

 

After the PS/2 computer hit the market in 1987, IBM released the PC LAN Support Program, which included a driver for NetBIOS.

 

Worth noting is the popular confusion between the names NetBIOS and NetBEUI. NetBEUI originated strictly as the moniker for IBM's enhanced 1985 NetBIOS emulator for token ring. The name NetBEUI should have died there, considering that at the time, the NetBIOS implementations by other companies were known simply as NetBIOS regardless of whether they incorporated the API extensions found in that emulator. For MS-NET, however, Microsoft elected to name its implementation of the NBF protocol "NetBEUI" — literally naming its implementation of the transport protocol after IBM's second version of the API. Consequently, even today, Microsoft file and printer sharing over Ethernet continues to be called NetBEUI, with the name NetBIOS commonly used only in reference to file and printer sharing over TCP/IP. In truth, the former is NetBIOS over NBF, and the latter is NetBIOS over NBT.

 

Since its original publishing in a technical reference book from IBM, the NetBIOS API specification has become a de facto standard.

 

Compretre?

 

Posted

NetBIOS αναπτύχθηκε το 1983 από Sytek Inc ως ένα API για την επικοινωνία του λογισμικού για PC της IBM-δικτύου LAN τεχνολογίας. Στις PC-δίκτυο, ως ένα API και μόνο, το NetBIOS στηρίχθηκε σε ιδιοκτησιακά πρωτόκολλα δικτύωσης Sytek για επικοινωνία πάνω από το σύρμα. Επειδή PC-Δίκτυο υποστηρίζεται μόνο μέχρι 80 συσκευές στην υποδοχή της πιο mode (baseband), το NetBIOS τη σειρά του είχε σχεδιαστεί με περιορισμένες κόμβους στο μυαλό.

 

Το 1985, η IBM πήγε μπροστά με το συμβολικό σύστημα δικτύου δαχτυλίδι και έναν εξομοιωτή NetBIOS παρήχθη να επιτρέψει NetBIOS-επίγνωση εφαρμογών από το PC-Δίκτυο εποχή για την εργασία πάνω από αυτό το νέο σχέδιο. Αυτή η άμιλλα, το όνομα NetBIOS Extended User Interface (NetBEUI), διευρύνθηκε η βάση NetBIOS API με, μεταξύ άλλων, την ικανότητα να ασχοληθεί με την μεγαλύτερη χωρητικότητα κόμβο του Token Ring. Ένα νέο πρωτόκολλο δικτύωσης, NBF, παρήχθη ταυτόχρονα να επιτρέψει NetBEUI (NetBIOS) για να παρέχει τις υπηρεσίες της σε συμβολική δαχτυλίδι - συγκεκριμένα, στο IEEE 802.2 Logical Link Control στρώμα.

 

Επίσης, το 1985, η Microsoft δημιούργησε μια εφαρμογή NetBIOS για τα κράτη μέλη της-NET τεχνολογία δικτύωσης. Όπως και στην περίπτωση του Token Ring της ΙΒΜ, οι υπηρεσίες του NetBIOS εφαρμογή της Microsoft που παρέχονται μέσω του IEEE 802,2 Link Λογική Ελέγχου στρώμα από το πρωτόκολλο NBF.

 

Το 1986, η Novell κυκλοφορήσει Advanced Novell NetWare 2,0 Με δικό του εξομοιωτή της εταιρείας NetBIOS. Υπηρεσίες της ήταν εγκλεισμένων IPX NetWare του / SPX πρωτόκολλο χρησιμοποιώντας το NetBIOS μέσω IPX / SPX (NBX) πρωτόκολλο.

 

Το 1987, μια μέθοδος encapsulating NetBIOS σε TCP και UDP πακέτα, το NetBIOS σε TCP / IP (NBT), δόθηκε στη δημοσιότητα. Ήταν περιγράφεται στο RFC 1001 ( "πρωτόκολλο πρότυπο για μια Υπηρεσία NetBIOS σε TCP / UDP Μεταφορές: Αρχές και Μέθοδοι») και RFC 1002 ( "πρωτόκολλο πρότυπο για μια Υπηρεσία NetBIOS σε TCP / UDP Μεταφορές: Οι λεπτομερείς προδιαγραφές"). Το πρωτόκολλο NBT αναπτύχθηκε με σκοπό να «καταστεί δυνατή η εφαρμογή [NetBIOS εφαρμογών] να κατασκευαστούν σε σχεδόν οποιοδήποτε τύπο του συστήματος, όπου το πρωτόκολλο TCP / IP οικογένεια πρωτοκόλλων είναι διαθέσιμο," και να "επιτρέψει NetBIOS διαλειτουργικότητας στο Διαδίκτυο."

 

Μετά την PS / 2 του υπολογιστή βγουν στην αγορά το 1987, η IBM κυκλοφόρησε το LAN PC Πρόγραμμα Υποστήριξης, το οποίο περιλαμβάνει ένα πρόγραμμα οδήγησης για NetBIOS.

 

Αξίζει να σημειωθεί είναι η δημοφιλής σύγχυση μεταξύ των ονομάτων NetBIOS και NetBEUI. NetBEUI προήλθε αυστηρά, όπως το παρατσούκλι για ενισχυμένη 1985 εξομοιωτή NetBIOS της IBM για Token Ring. Το όνομα NetBEUI θα πρέπει να έχουν πεθάνει εκεί, δεδομένου ότι εκείνη την εποχή, ήταν γνωστές οι υλοποιήσεις NetBIOS από άλλες εταιρείες απλώς ως NetBIOS ανεξάρτητα από το αν ενσωματωθούν οι επεκτάσεις API που βρέθηκαν σε εξομοιωτή. Για MS-NET, ωστόσο, η Microsoft επέλεξε να το όνομα της εφαρμογής του πρωτοκόλλου NBF "NetBEUI" - κυριολεκτικά την ονοματοδοσία του εφαρμογή του πρωτοκόλλου μεταφοράς μετά τη δεύτερη εκδοχή από την IBM, η API. Κατά συνέπεια, ακόμη και σήμερα, η Microsoft κοινή χρήση αρχείων και εκτυπωτών over Ethernet εξακολουθεί να ονομάζεται το NetBEUI, με το όνομα NetBIOS που χρησιμοποιούνται συνήθως μόνο στην αναφορά για την κοινή χρήση αρχείων και εκτυπωτών σε TCP / IP. Στην πραγματικότητα, το πρώτο είναι το NetBIOS σε NBF, και το τελευταίο είναι το NetBIOS σε NBT.

 

Από την αρχική έκδοση του σε ένα τεχνικό βιβλίο αναφοράς από την IBM, το NetBIOS API προδιαγραφή έχει γίνει ένα de facto πρότυπο.

 

COMPRETRE?

Posted

Το netbios είναι ένα σύστημα στα windows που επιτρέπει την επικοινωνία προγραμμάτων μέσα σε ένα δίκτυο LAN. Άν δεν έχετε lan καλό είναι να απενεργοποιείτε το netbios γιατί έχει κάποια κενά ασφάλειας. Στο windows xp sp2 το netbios είναι απενεργοποιημένο by default. Στο sp1 όμως είναι ενεργό.

 

Για απενεργοποίηση πατήστε:

Start>

 

Control Panel>

 

Network Connections>

 

δεξί κλικ στη σύνδεσή σας>

 

Properties>

 

Networking>

 

εδώ έχω απενεργοποιήσει και τα δυο File and Printer Sharing/Client for Microsoft networks>

 

Internet Protocol (TCP/IP) Properties>

 

Advanced>

 

WINS>

 

Disable NetBios over TCP/IP.

 

Στο τέλος πατάμε παντού ΟΚ και κάνουμε επανεκκίνηση (reboot).

Posted

Το netbios είναι ένα σύστημα στα windows που επιτρέπει την επικοινωνία προγραμμάτων μέσα σε ένα δίκτυο LAN. Άν δεν έχετε lan καλό είναι να απενεργοποιείτε το netbios γιατί έχει κάποια κενά ασφάλειας. Στο windows xp sp2 το netbios είναι απενεργοποιημένο by default. Στο sp1 όμως είναι ενεργό.

 

Για απενεργοποίηση πατήστε:

Start>

 

Control Panel>

 

Network Connections>

 

δεξί κλικ στη σύνδεσή σας>

 

Properties>

 

Networking>

 

εδώ έχω απενεργοποιήσει και τα δυο File and Printer Sharing/Client for Microsoft networks>

 

Internet Protocol (TCP/IP) Properties>

 

Advanced>

 

WINS>

 

Disable NetBios over TCP/IP.

 

Στο τέλος πατάμε παντού ΟΚ και κάνουμε επανεκκίνηση (reboot).

leptomeries....
Guest
This topic is now closed to further replies.



  • Posts

    • NEW SEASON GRAND OPENING FROM - 23 JANUARY 2026, FRIDAY, 20:00 +2 GMT !
    • Ehh so you just judge on if product is free or paid? Wtf. You know that a price tag oftens value the quality of a product. So how you think that a free fork is superior to one that's been maintained for years and is paid?
    • Sadly we gotta choose between poop and shit, it is what it is.
    • GM, change server name to L2][Wipe please.
    • I have browsed this forum for months, witnessing the infinite and endless debate over which datapack is better, whether one is leaked or another is stolen. I constantly see developers from different projects throwing mud at each other for their own convenience. For a novice 27-year-old developer with a dream, all of this is disheartening. Opening a Lineage 2 server in 2026 seems like a titanic goal when looking for stability and scalability. The thought of depositing my only savings into one of these datapacks, praying to God that everything goes well, is terrifying. This is not a destructive critique of any forum member or developer. It is simply a call for reflection: What are we doing for the original essence of Lineage 2? Have we forgotten those memories from when we were young, going to a cybercafé to play for 12 hours straight just to grind a few levels? It seems that instead of providing a quality server to the community—a place where our inner child can enjoy the game—this has become a race where the only prize is money, at the cost of progressively destroying the game's community. Is there actually anyone or any project thinking about this? I know that invested time requires financial return; obviously, we all need to survive and eat. But friends... that isn't everything. Currently, in Argentina, 100% of the servers are garbage and last approximately one month. Corrupt admins, illegal item sales for quick profit, and endless toxic practices. Since I couldn't find the answers I needed, I tasked a generic AI (Google Gemini) with creating an extensive report on datapacks, history, competition, and current objectives. I am leaving it here for anyone who wants to read it. Comprehensive Research Report: The State of the Lineage 2 Java (L2J) Emulation Ecosystem 2020-2026 1. Executive Summary and Strategic Scope The landscape of Java-based Lineage 2 (L2J) server emulation has undergone a radical metamorphosis between 2020 and 2026. What began in the early 2000s as a scattered community effort to reverse-engineer a Korean MMORPG has consolidated by 2026 into a highly sophisticated software development sector. This report aims to provide the definitive guide and the most comprehensive technical analysis available in the market regarding the selection, architecture, and viability of L2J datapacks. A clear bifurcation in development philosophy has been identified: on one side, massive, chronicle-agnostic open-source projects, indisputably led by L2JMobius (and its strategic transition to the MIT license in 2025); and on the other, highly specialized niche projects like aCis (for Interlude) and L2JEternity (for High Five), which prioritize architectural purity and extreme performance through the early adoption of JDK 25. This document not only evaluates "completeness" in terms of game content but also dissects technical debt, legal security, and long-term sustainability. 1.1 Evaluation Methodology To determine the "best" datapack, we applied a multidimensional evaluation matrix: Architectural Integrity: Analysis of code quality, thread management, and modern design patterns. Lifecycle Maturity: Update frequency and leadership stability. Tool Ecosystem: Availability of client editors, geodata generators, and compatible anti-bot systems. Commercial Viability: Ability to sustain a stable economy and support high concurrency loads (500+ simultaneous players). 2. The Technological Revolution: From Java 8 to Java 25 (2020-2026) One of the most critical findings is the quantum leap in the underlying infrastructure. The 2023-2026 period has witnessed a technological arms race. 2.1 The Impact of JDK 25 on Emulation Vanguard projects like L2JEternity and the main branches of L2JMobius completed the migration to JDK 25. Garbage Collection (GC): The implementation of ZGC and Shenandoah has solved the historic problem of "GC pauses" (lag due to memory cleaning). With JDK 25, these pauses are sub-millisecond, allowing for fluid massive combat (Sieges). Virtual Threads (Project Loom): This allows handling thousands of simultaneous connections and AI tasks without the excessive cost of traditional OS threads. 2.2 Network Layer Modernization (Netty) The old MMOcore-based architecture has been replaced or heavily refactored using Netty, optimizing the packet pipeline and improving security against application-layer DDoS attacks. 2.3 Tech Stack Comparison | Project | Java Version (2025/26) | Database | Status | | :--- | :--- | :--- | :--- | | L2JMobius | JDK 21 / 25 | MySQL / MariaDB | Active (MIT) | | L2JEternity| JDK 25 | MySQL | Active (Private) | | aCis | JDK 11 / 17 | MySQL | Active (Private) | | L2JFrozen/Brasil | JDK 7 / 8 | MySQL | Obsolete / Risk | 3. L2JMobius: The Open Source Hegemon L2JMobius emerges as the definitive answer for the vast majority of use cases in 2026, based on three pillars: universality, legality, and tools. Universality: It maintains a unified architecture (monorepo) supporting everything from C1 to the most recent Essence versions. Core fixes propagate to all versions. MIT License (June 2025): A historic milestone allowing servers to modify code extensively and keep changes private without violating the license, legitimizing commercial use. Vertical Integration (L2ClientDat): The team actively maintains client editing tools, ensuring perfect compatibility with the latest protocols (e.g., Protocol 507). 4. The Battle for Interlude: Purism vs. Modernity Interlude (C6) remains the most demanded version. aCis (The Gold Standard): Obsessed with code quality and "Retail" fidelity. Ideal for Low Rate servers (x1-x10). The free version is often stale; the paid version is the professional choice. L2JMobius Interlude: The practical "batteries included" alternative. Includes popular mods out of the box and benefits from the modern core. Ideal for Mid/High Rate PvP servers. Warning: L2JFrozen and L2JBrasil are considered obsolete and dangerous in 2026 due to security vulnerabilities and unmaintainable code. 5. The High Five Sector: Commercialization and Risks L2J Sunrise: Positions itself as a "turnkey" solution, but its closed code creates total vendor dependence. Risky for long-term projects. L2JEternity: The technical gem for advanced admins. Pioneer in JDK 25 and offers native support for protections like Strix and SmartGuard. 6. Essence and the Modern Era For Essence, L2JMobius has no real competition in the free Java space, reacting to NCSoft updates with supernatural speed. Russian commercial alternatives (L2-Scripts) exist but come with high costs. 7. Ecosystem and Auxiliary Tools Geodata: Essential to avoid movement errors. 2026 hybrid engines reduce "wall-shooting." Vote Reward: Middleware systems like VDSystem or iTopZ are mandatory, and modern datapacks already include the necessary hooks. 8. Conclusions and Definitive Recommendations After analyzing repositories and trends up to January 2026: Overall Winner: L2JMobius. Best ratio of features/modernity/support. Purist's Choice (Interlude): aCis. Unbeatable mechanical fidelity. Performance Option (High Five): L2JEternity. Extreme optimization. Final Warning: Strictly avoid L2JFrozen, L2JBrasil, and black-box projects like Sunrise for critical infrastructures.
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock