SMB (network) loading lets OPL stream PS2 games from a shared folder on your PC or NAS over your local network, instead of copying every ISO onto a USB drive or HDD. It's the best option once your game library outgrows portable storage.
Requirements: a wired Ethernet connection to the PS2 (the console has no built-in Wi-Fi), a PC or NAS on the same network with a shared folder, and a few network settings entered inside OPL.
The #1 reason SMB fails on a modern PC: OPL needs SMB1. The PS2's network stack only speaks the old SMB1 (SMBv1) protocol. Microsoft disables SMB1 by default on Windows 10 and 11 for security reasons — if your share worked before and stopped after a Windows update, this is almost always why. Re-enable it via Control Panel > Programs > Turn Windows features on or off > SMB 1.0/CIFS File Sharing Support, then restart.
Setting Up SMB Loading
- Connect the PS2 to your router with an Ethernet cable (via the console's network adapter port).
- On your PC, create a shared folder and put your game ISOs inside a
DVDsubfolder, exactly like the USB folder structure. Set the share's permissions to allow read access from your network. - In OPL, go to Settings > Network Settings and enter: the PS2's IP address, subnet mask (usually
255.255.255.0), gateway (your router's IP), the PC's IP address, the share name, and the username/password if your share requires one. - Save and switch to the network tab in OPL — your shared games should appear in the list.
Enabling SMB1 on Windows 10/11
- Open the Start menu, search for "Turn Windows features on or off", and open it.
- Find SMB 1.0/CIFS File Sharing Support in the list, expand it, and check SMB 1.0/CIFS Client (and Server, if you're sharing directly from that PC).
- Click OK and restart the PC when prompted.
- Re-share your games folder and retry the connection in OPL.
Common SMB Connection Problems
| Symptom | Likely Cause |
|---|---|
| Network tab is empty | Wrong IP/subnet/gateway values, or share isn't accessible to Guest/Everyone |
| Worked before, now broken | A Windows update silently re-disabled SMB1 — re-enable it above |
| Connection times out | Firewall on the PC blocking SMB (port 445) |
| Share found, login rejected | Guest access disabled in Windows' Local Security Policy, or the account needs a password when the PS2 sends none |
| Games appear but won't load | Folder structure inside the share doesn't match OPL's expected DVD/CD layout |
Still failing after enabling SMB1? Check Local Security Policy > Local Policies > Security Options for "Network access: Sharing and security model for local accounts" — set it to Guest only so Windows doesn't demand credentials for the built-in Guest account. Later Windows versions also default to higher SMB encryption levels the PS2 can't negotiate; if problems persist, a dedicated lightweight SMB1 server (an old PC or Raspberry Pi running Samba) sidesteps Windows' restrictions entirely.
SMB vs. USB vs. Internal HDD
SMB's main advantage is capacity — your shared folder can be as large as your PC's or NAS's storage allows, with no need to physically move drives. Its trade-off is setup complexity and a dependency on your network staying stable. For a simpler setup, see USB loading; for the fastest possible speeds on a PS2 Fat, see internal HDD compatibility.
Not set up with OPL yet?
Start with the full installation guide before configuring network loading.
How to Install OPL on PS2