From zero to streaming your first game over Ethernet in under ten minutes. Follow this guide to prepare your network, organize your disc images, run the server, and connect from your console.
The server and the console loader must support the same protocol. UDPFS and UDPBD are not interchangeable. Choose the type of data you want to serve first:
| Desktop mode | What to select on the server PC | PS2-side requirement |
|---|---|---|
| UDPFS | Library folder containing DVD/ and CD/ | UDPFS-enabled client such as compatible Neutrino, NHDDL, or RiptOPL |
| SMBv1 | Shared library folder | SMBv1/ETH-enabled loader and matching host IP, share, and TCP port |
| SMB2 / SMB3 | Shared library folder | Loader explicitly supporting SMB2/3; SMBv1-only clients cannot use it |
| HTTP | Library folder | Compatible HTTP game loader, with exactly matching TCP port |
| NFS | Library folder (shared as export /) | NFS 4.0 client built on unfs4, such as RiptOPL's NFS protocol, Neutrino's NFS mode or Launchstation's nfs:; TCP 2049 |
| UDPBD | One block-image file, e.g. game.iso or disk.img; not a folder | UDPBD driver that understands the file's block layout |
DVD/ library browsable. Use UDPFS or SMB for a library, and choose that same protocol on the PS2. If the loader reports mass0: or "cannot open folder", see the UDPBD troubleshooting guide instead of guessing which device is behind the label.
Both your server host (PC, router, Raspberry Pi, or NAS) and your PlayStation 2 must share a physical or bridged local network. A wired Ethernet connection is strongly advised; Wi-Fi can cause stuttering during FMV playback and disc reads.
Plug both your host computer and your PS2 into the same router or Ethernet switch using standard Cat5e or Cat6 cables. Your router handles IP assignment, or you can assign static addresses in the same subnet.
192.168.1.100192.168.1.150255.255.255.0192.168.1.1Connect an Ethernet cable directly between the PC's network jack and the PS2. Modern PC network interfaces support Auto-MDIX (automatic crossover), so a standard patch cable works fine.
192.168.0.1 (Subnet: 255.255.255.0).192.168.0.2.192.168.0.1.For UDPFS, SMB, and HTTP: create a dedicated game-library folder (for example D:\PS2Games on Windows or /srv/ps2 on Linux) and organize it with the standard OPL hierarchy:
PS2Games/
├── CD/ ← CD-based PS2 games (<700 MB ISO images)
├── DVD/ ← DVD5 and DVD9 PS2 games (>700 MB ISO images)
├── ART/ ← Cover art, backgrounds, spines, discs (optional)
├── CFG/ ← Per-game configuration files (optional)
├── VMC/ ← 8MB Virtual Memory Card files (optional)
└── CHT/ ← Cheats files (optional)DVD, CD, ART). Many loaders (and Linux/Edge servers) are case-sensitive.DVD/SLUS_201.74.Rumble Racing.iso or CD/SCUS_971.24.Game.iso.
For UDPBD: do not select this library directory. Select one image file in the UDPBD card instead. Its internal format must match what the console-side block driver expects. Enable Read-only for your first test. See the UDPBD setup steps.
Review indexed paths reports duplicate names, inspected serials and case/Unicode path collisions. In RetroAchievements Manage game library, enable Include Desktop indexed paths and titles to read the same PS2 index and custom titles without merging catalogues. It is off by default; RA compatibility still requires the image hash.
In the LIBRARY tab, scan your games root, then use Inspect disc IDs to read ISO/CSO/ZSO/CHD boot metadata. Manual ID, Inspected ID and ID status are shown separately; double-click a row or press Enter for conflicts or errors. This preserves your filenames and metadata. Inspection runs in the background with cancellation and a 1,000-entry limit. Compressed inspection has additional resource limits and requires the format's decoder; unavailable decoders and unsupported layouts are reported explicitly.
Indexed or inspected does not prove console launch compatibility. Recursive discovery does not reconfigure server roots or enable nested paths in a loader. See the library indexing and inspection guide for limits, cached results and supported layouts.
Download the latest release package from the Releases Page. Extract the portable ZIP to a folder on your host machine. Launch PS2Servers.exe on Windows, or invoke python ps2servers.py from source.
In the top bar of PS2 Servers Desktop, ensure the LAN IP dropdown selects the network adapter wired to your PS2. The launcher automatically displays the IP address and helpful setup hints for each card.
On UDPFS / SMB / HTTP, browse to the parent folder containing DVD/ and CD/. On UDPBD, browse to a single image file; do not choose the game-library folder. Press Start, then check Terminal for the image/root path and a successful listening message.
After selecting a folder or image file, click Check access on the server card. The results appear in a dialog and the Terminal log. Folder checks verify listing only; image checks verify reading and, unless read-only is selected, a writable open without writing data. Actual game reads and saves still need testing.
On Linux, check parent-directory access and mount ownership/permissions; NTFS/exFAT mount options can control access. On Windows, check the target's Security permissions for your account. This check does not open raw disks, reformat drives, or change permissions.
Boot your PlayStation 2, launch your loader, and navigate to Network Settings. Configure the connection to match the values displayed on your running server card:
| Setting | SMBv1 Mode (Standard OPL) | UDPFS Mode (Neutrino / RiptOPL) | HTTP Mode |
|---|---|---|---|
| Protocol / Device | SMB (ETH) | UDPFS (Network Boot) | HTTP |
| Address Type | IP | IP (or Broadcast Discovery) | IP |
| PC IP Address | Host PC LAN IP (e.g. 192.168.1.100) |
Host PC LAN IP (e.g. 192.168.1.100) |
Host PC LAN IP |
| Port | 1025 (Desktop) or 1111 (Core/Edge) | 62966 (Auto data port) | 1100 (Explicit match required) |
| Share Name | games |
N/A (folder tree served directly) | Blank or anything |
| User / Password | User: guest · Password: (empty) |
None | None |
These game-list steps apply to filesystem/game-library protocols such as UDPFS, SMB, and compatible HTTP clients. UDPBD exposes a block device and does not provide a DVD/ directory listing.
mc0:).DVD/ and CD/ folders.mass0: may be a logical device/mount identifier used by that loader; the label alone does not prove it is a physical USB device. Verify the console-side backend genuinely supports UDPBD, the server is serving one image file rather than a folder, and the client understands that image's format. If you expected to browse a collection of ISO files, use UDPFS or SMB at both ends. Read the UDPBD diagnosis checklist.
The PC and PS2 need different IP addresses on a reachable local network. SMB uses the actual displayed TCP port and share; HTTP requires its configured TCP port; UDPFS discovers via UDP 62966 plus an optional data port; UDPBD uses UDP 48573 broadcast discovery. Allow the corresponding traffic through the host firewall, and verify that broadcasts can cross your current switch/router configuration.
Verify that your games folder has the uppercase DVD and CD subfolders and that file extensions are .iso, .zso, or .cso. If using SMBv1, ensure the share name in OPL is exactly games, address type is set to IP (not NetBIOS), and the port matches the displayed card port (1025 or 1111).
This is commonly caused by multiple network adapters on the host PC (e.g. active Wi-Fi and Ethernet simultaneously). When the PS2 sends data requests, the OS may attempt to respond from the wrong IP. See our detailed UDPFS Diagnostics Guide for how to pin the bind address directly to your PS2-facing interface.
Yes. Both SMBv1 and SMB2/3 in PS2 Servers are writable by default. If your loader supports creating and mounting VMC images over the network (such as stock OPL or RiptOPL on SMB), images in VMC/ can be written directly over the network.