About Encode NetBIOS Name
NetBIOS names as seen across the client interface to NetBIOS are exactly 16 bytes long. Within the NetBIOS-over-TCP protocols, a longer representation is used. There are two levels of encoding. The first level maps a NetBIOS name into a domain system name. The second level maps the domain system name into the 'compressed' representation required for interaction with the domain name system. This operation carries out the first level of encoding. See RFC 1001 for full details.
Input: binary bytes. Output: binary bytes.
Format reference: Encode NetBIOS Name background and specification
Example
Use “Try example” to load this public sample and its settings, then run it.
Settings used in this example
| Parameter | Example value | Input and choices |
|---|---|---|
| Offset | 65 | Number |
Input
The NetBIOS name
Result
FEGIGFCAEOGFHEECEJEPFDCAGOGBGNGF
Parameters
| Parameter | Default value | Input and choices |
|---|---|---|
| Offset | 65 | Number |
Before interpreting the result
Protocol parsers need the correct byte representation and framing. HTTP Request and DNS over HTTPS contact remote services only when you run them; browser network and CORS restrictions still apply.
How to use this page
- Paste your input or open a local file.
- Adjust tool options if needed, then choose Run tool.
- Copy the result or download the original output bytes.
Inputs and results are not added to the public catalogue or saved in the URL. Processing happens in your browser; HTTP Request and DNS over HTTPS send the requests you explicitly run. Files up to 128 MiB can be opened; decompression and image tools may have smaller processing limits. Large results have a shortened preview. Text and HTML downloads use UTF-8; binary downloads preserve output bytes. Pasted text follows browser newline handling; open a file when exact input bytes matter.