Thanks Joligario,
That would make sense, with that in mind, do you think that perhaps I have a setting variable set to my internal which is (10.0.0.200) when it should be my external? If so, any ideas where this may be located? My internal IP looks odd as most are typically the standard (192.168.0.x) but mine is in fact (10.0.0.200) and all on my network are the (10.0.0.x) format.
I'm not sure why this is, but it's a recent change in Comcast and their settings, it may have to do with the hardware I'm not sure but it's something they are doing now at least in my area in the last year or so. It's different but I'm sure it has nothing to do with my problem.
However, I think that you're on to something, the problem may not be port forwarding as others stated, some may appear closed when no connection is established and can't be counted as being confirmed closed or blocked. I'd like to investigate this theory of yours a bit further.
Considering this as a possibliity that somewhere on my server it is trying to pass the client to my internal IP rather than my external IP... are there any ideas which of the settings/files/configs it may be that I need to change? I guess a good question would be, which setting(s) where an IP is given can be changed to an external IP rather than internal, "localhost" or "127.0.0.1" and still work correctly? Does anyone know of any?
That may be a good place to start. I know some settings will totally fail if given an external IP when a local one is expected - perhaps one can/should be replaced with an external IP and port?
Thanks for the help guys, keep it coming! I greatly appreciate it, slam some coffee and get that grey matter warmed up!
Any ideas?
-N
|
Threaded Mode
