Thread: Content Server
View Single Post
Old 12-30-2012, 04:25 AM   #9
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 8,735
Karma: 12488297
Join Date: Feb 2009
Location: North Carolina
Device: Nexus 7
Quote:
Originally Posted by roadstar View Post
I know what you're saying, but surely we don't have to worry about port forwarding on every router/computer we might have access to, "anywhere in the world" (quote).
You have to worry about port forwarding on the router that the computer running the content server connects to.

Quote:
Originally Posted by roadstar View Post
(by the way, I'm using the correct IP)
If the IP you are using starts with 192.168.x.x, 172.x.x.x, 10.x.x.x or 127.x.x.x then you are using the wrong IP to try and connect with the content server from outside your local network. You need to use the external (internet facing) IP address of your WAN.

Try this thread for a better understanding.

Last edited by DoctorOhh; 12-30-2012 at 05:00 AM.
DoctorOhh is offline   Reply With Quote