Troubleshooting

• No games appear in Aurora. Check that Aurora’s scan paths include Hdd1:\NetISO (depth 1), that Aurora’s FTP server is on, and that the FTP login under the dashboard’s Settings > Xbox & Aurora matches Aurora’s. The Consoles page says whether each console’s Aurora answers, and the Log page what the server is waiting for.
• “The server doesn’t answer” on the loading screen, or NetISO lists only “No Server!”. Check the address in NetISO.xex.txt against the one the dashboard shows, and that Windows Firewall allows NetDisc360.exe on private networks. Right after a reboot the console needs a minute or two before it can reach the server.
• A game has no cover art. Rename its folder in Hdd1:\NetISO (for example over FTP); at the next scan Aurora looks it up again. See Cover art.
• “Can’t listen on port 4323”. Another NetISO server (netiso-srv, server.exe, or a second copy of this one) is still running. Close it.
• “Choose which copy to play” on the Games page. The same game is in your folders more than once. Pick the copy to play there; NetDisc360 remembers it. To free up space, delete the copies you don’t play.
• The dashboard doesn’t open. Another program may be using port 8360; the log says so. Start the server with --web-port and another port. Opened from another device by a name rather than an address, it says to use the address until it has a password.
• “NetDisc360: this game asks for a disc it has no tile for”. The game’s other disc isn’t in your game folders. Add it; the server gives it a tile, and the swap works the next time you start the game.
• Something else. Each game writes netiso.log in its folder on the console (Hdd1:\NetISO\<game>), with each step and why it stopped; the dashboard’s Log page shows what the server did. How it works explains both, and its troubleshooting switches help find out what breaks on a console.