Mazeda Network FTP
Mazeda Network FTP runs two private nodes, 172.22.22.100 and 172.22.22.101, with a player-style portal at 172.22.22.100:8096 for the app view. Both nodes serve the operator's own network and peering routes first, which is the shape most BDIX media servers settle into. This page records the addresses, covers access and troubleshooting, and explains why one node can work while the other does not.
What Is Mazeda Network FTP?
Both addresses sit in the private 172.22.x.x range, so nothing about them resolves publicly: reachability depends on the operator's network and on whether your ISP peers through BDIX with a route in. That is why a mazeda network ftp or mazeda network server search can lead to an address that simply times out on the wrong connection.
The portal at port 8096 is the player-style face of the same library, grouped like a media app. The raw nodes give the plain folder view. Both doors read the same catalog, and the portal can carry its own sign-in rules.
Quick Facts
| Operator | Mazeda Network Ltd |
|---|---|
| Main Address | 172.22.22.100 |
| Content | Movies and TV series |
| Access | Browser (HTTP) |
| Reachability | Local Network · Reachable on the hosting ISP's own network only: these are local/private IPs. |
The Network Behind the Server
The private 172.22.x.x addressing defines the server's reach: strongest on the operator's own lines, conditional on peering routes elsewhere, and silent from abroad. The portal shares node 1's address on a different port, so node 1 can be up for browsing while the portal layer is busy; test the second node before diagnosing the portal.
How It Compares
| Question | Mazeda | SamOnline | FTPBD |
|---|---|---|---|
| Nodes | 172.22.22.100/.101 | 172.16.50.4/.7 | 103.58.73.6-.10 (five) |
| Portal | 172.22.22.100:8096 | movie.sambd.net:8096 | media.ftpbd.net:8096 |
| Range | Private 172.22.x | Private 172.16.x | Public 103.x |
| Habit | Node, node, portal | Node, node, portal | Walk the family |
Who Should Use It
Mazeda fits the operator's customers and peering-route users who like the portal experience. For a monitored map of every private-range option, the directory.
Related Guides
What Content Does It Host?
The layout is nodes plus portal:
- Node 1: 172.22.22.100, also hosting the portal on :8096.
- Node 2: 172.22.22.101, the mirror door.
- Portal: 172.22.22.100:8096 for the player-style view.
The rotation habit works here exactly as on the other two-node families: node 1, node 2, then the portal. If all three fail together on a known-good route, suspect the route before the servers, because three independent doors rarely close at once.
What Mazeda Network FTP Hosts?
How to Access Mazeda Network FTP
172.22.x.x range: the operator's own customers first, then BDIX-peering networks that carry the route. Access is free; the portal follows its own sign-in rules.Connection details
http://172.22.22.100 (node 1) · http://172.22.22.101 (node 2) · http://172.22.22.100:8096 (portal)On Android, open Chrome and try http://172.22.22.100; switch to .101 if it hangs, and use http://172.22.22.100:8096 for the app-style view.
On Windows, browse to either node in Edge; a file client can use the node host for a folder view with the settings the current page shows.
Reachable on the hosting ISP's own network only: these are local/private IPs.
Login and Codes
The nodes accept guest browsing for the main library. The portal can present its own sign-in, controlled by the operator; take any credentials from the current page only.
We publish no passwords or portal keys. Private-range portals rotate values like every other operator, and a stale one fails on both the nodes and whatever IPTV app stored it.
Troubleshooting
- Node unreachable: private range; test from the operator's network or a peering route, VPN off.
- One node fails: switch to the other; they mirror the catalog.
- Portal timeout: test both raw nodes first; the portal is a layer, not the network.
- Portal login rejected: values only from the current page; stop after two tries.
- Foreign test fails: expected; private ranges cannot be probed.
- Confusion with other :8096 portals: Circle, SamOnline and FTPBD run their own; match hosts exactly.
- Slow browsing: rotate nodes before blaming the catalog.
- Everything fails: route first, then this page's note.
Mazeda's pattern matches the other two-nodes-plus-portal families.
Server & IP Addresses
| Node | IP address | Hostname |
|---|---|---|
| Main | 172.22.22.100 | - |
| Node 2 | 172.22.22.101 | - |
| Node 3 | 172.22.22.105 | - |
FAQ
What Is Mazeda Network FTP?
Mazeda Network FTP is the two-node BDIX media service on the private addresses 172.22.22.100 and .101, with a player-style portal at 172.22.22.100:8096.
What Is the Mazeda Server Address?
The nodes are 172.22.22.100 and 172.22.22.101; the portal shares node 1's address on port 8096.
Why Do the Nodes Not Open for Me?
They are private-range addresses needing the operator's network or a BDIX-peering route. From other networks they time out by design.
How Do I Open Mazeda on Android?
Try http://172.22.22.100 in Chrome, switch to .101 if it hangs, and use the :8096 portal for the app-style view.
How Do I Use It on Windows?
Browse to either node in Edge, or point a file client at the node host for a folder view, with settings from the current page.
Is Mazeda FTP Free?
Yes, on a reaching route; the portal follows its own sign-in rules set by the operator.
Does It Need a Password?
The nodes are guest-open; the portal can ask for its own sign-in, with values only from the current page.
Why Does the Portal Fail but the Nodes Work?
The portal is a separate layer sharing node 1's address on another port; it can be busy while raw browsing is fine.
What Does the :8096 Mean?
It is the portal's service port, part of the address. Other operators run their own :8096 portals; match the host exactly.
What Does It Host?
A mirrored media catalog across the two nodes, presented as folders on the raw nodes and as an app-style library on the portal.
Why Does Everything Fail at Once?
Three independent doors rarely close together; suspect your BDIX route or a VPN before the servers.