This is article will discuss how to troubleshoot problems with wireless networks.
If you're using a wired network, click here for the Wired Network troubleshooting article.

If you've carefully followed the Networking Instructions, but are still unable to view your server in Step 9 here some troubleshooting suggestions. Getting a computer expert involved is highly recommended.

Here are the steps to start the troubleshooting process:

Shut everything down, wait one minute then restart the equipment in this order: router, server, guests.
Wait for the router to completely reboot before starting the server, and wait for the server to complete reboot and open the Studio Organizer as shared files before opening the guests. 

Verify Port 5003 is unused and clear for all traffic. You'll want to check both the firewall of your computer and the router settings.

Windows Firewall is known for blocking applications that have been previously cleared to send traffic. Check this firewall often and RESTART after making any changes.

Ping the server from a guest computer.

Have a networking expert perform network diagnostics.

Try using a different computer as the server.

Uninstall, then reinstall FileMaker Pro.

Try a Different Wireless Network

If at this point you're still having no success, it's possible there is a problem with the wireless router, or the operating system of your computer. The fastest way to verify your Studio Organizer data files are functioning correctly and that the problem is elsewhere is to set up a test network on a different wireless network, using a different computer and router. In other words, you're removing everything but the Studio Organizer from the equation.

To do this, install the full working copy of FileMaker Pro 13 on an entirely different wireless network. To start, you don’t even need to install the Studio Organizer. Instead, just set up one of the FileMaker Pro samples files as a shared file by following the Networking Instructions.

Now open the sample file on your iPad or guest computer. If everything works great, the next step is to use the Transferring Data Wizard to move the Studio Organizer 6 to this second wireless network. Click here for the instructions for using the Transferring Data Wizard.
(Please be sure to use the Wizard, otherwise your Registration Code is not included with your data.)

Once you’ve verified everything works on a different network using different equipment you now know for certain there isn’t a problem with the code of the Studio Organizer. This means you can now move forward with finding the culprit on your school network. It may be a corruption issue, or it may be a hardware issue, but in either case you've now verified the problem is only occurring on the school network.

Replace the Router

At this point you can try replacing the router. I once had a client with a large network and overnight they began experiencing dropped connections, networking errors and long delays. I recommended the above troubleshooting, then suggested replacing the router. Back then it was an expensive piece of equipment so my advice went unheeded until one day the manager emailed me in frustration saying he'd spent far too many hours and dollars and the network was still unreliable. At this point he felt his job was on the line. 

I responded, "Did you replace the router?" but didn't get a reply. About a week later, he sent me an exasperated email. One evening after everyone was gone he climbed into the ceiling where all the network equipment was stored. It was in a dirty, dark and hard to get to location, but he got up there and removed the old router. He took it back to his desk and in the light of day he could see small black marks on the plastic housing of the router. This was suspicious, and suddenly it dawned on him -- the router had been hit by lightning!

He took the router to ComputerLand and they sold him a newer, faster router as well as a heavy duty surge suppressor. He ended the email by telling me the network runs better than ever -- and he wishes he'd replaced the router weeks ago.

Reinstall the Operating System

Reinstall the operating system on the computer being used as the server. This is time consuming, and a definitely a task for a computer expert, but solves a multitude of potential problems. 

I've recently done this with my primary programming computer and a second computer. Both machines run like new now and the time invested was well spent.