Quote:
Originally Posted by woodygirl
And I am using the right IP address, it is a 216.something...number.
|
Agreeing with varelov, that is almost certainly not the right IP address.
For 99.99% of home networks, there are two IP addresses of interest. The first is the one (sometimes two) that your ISP gives you. These are 'public' IP addresses, and are used on the outfacing (internet-facing) side of the router.
The second is a pool of addresses, used on the infacing side of the router. These are private IP addresses, and will start with one of 192.168, 172.16, or 10. Your router will act as a controller (called a DHCP server), allocating an address from the pool when a device connects to the network.
216... is a public IP address. Unless you are a business that is given a pool of public addresses or have an extremely strange setup, it is your outfacing address. Getting that address to work from inside your network requires admin voodoo of the highest order, and in many cases cannot be done. It might work from outside your network, if you have set up port forwarding in your router.
You need to track down the internal IP address of your server. Varelov suggested one way. Another is to open a command box (start, run, cmd), then type ipconfig at the prompt. Hit return, and you will see several lines of output. Buried in there will be information about the network connection. For example, on my machine, I see what is shown under the spoiler. I obfuscated the IP addresses for no particularly good reason other than paranoia.
To finish, itimpi's advice is certainly good. Tracking down port conflicts can be frustrating. That said, start with finding the correct IP address of your content server.