Can access IP Camera from the Internet but not internally?

Sep 29 05 2:22 am

Hi,

I have a IP Camera in my home network with a fixed IP : 192.168.0.230 accepting connections on port 9018. On the same network my Server (IP:192.168.0.1) (example.dyndns.net) has Wingate running. I use Wingate to share my internet connection.

In Gatekeeper/Extended Networking/Port Security:

1. I've configured a port forward to my IP Camera(192.168.0.230) for "Internet Computers to the WinGate PC".
2. I've checked TCP
3. Set the Ports from 9018 to 9018
4. Redirect to IP 192.168.0.230(IP Camera)
5. Checked Clock connection failures
6. Use default timeouts

Now, heres the funny thing. If I use my company's internet or ask a friend to connect to http://example.dyndns.net:9018, everything run's fine and the IP Camera does its job of displaying the live video feed.

In my home network, when I try to view the same thing the page does not load at all. Firefox reports that the connection has been refused. IE says the page cannot be displayed. However when I try http://192.168.0.230:9018, the page loads fine.

Basically, why am I unable to access my own network when I'm in it, when I can access it from the Internet or rather from an external network?

Internet -> http://example.dyndns.net:9018 -> IP Camera = Possible
Internal Network(192.168.0.0) -> http://example.dyndns.net:9018 -> IP Camera(192.168.0.230) = Not possible?

Anyone can shed some light into this or help?

Thanks

Sep 29 05 2:50 pm

C:\WINDOWS\system32\drivers\etc\hosts

Edit that file as follows:
Scenario 1.
Edit the file on the Wingate server if it is serving proxy connection to the network or you are trying to connect to the camera from it.
Scenario 2.
Edit the file on the client machine within your network if you are not using proxies

Code:: 127.0.0.1 localhost 192.168.0.230 example.dyndns.net

When you save the file, make sure no file extension is placed on it. In most Windows configurations, when a domain name needs to be resolved to an ip address, it first checks the Host files, then a DNS server.

Sep 29 05 3:28 pm

jamesc wrote:C:\WINDOWS\system32\drivers\etc\hosts

Edit that file as follows:
Scenario 1.
Edit the file on the Wingate server if it is serving proxy connection to the network or you are trying to connect to the camera from it.
Scenario 2.
Edit the file on the client machine within your network if you are not using proxies

Code:
127.0.0.1 localhost 192.168.0.230 example.dyndns.net

When you save the file, make sure no file extension is placed on it. In most Windows configurations, when a domain name needs to be resolved to an ip address, it first checks the Host files, then a DNS server.

Sorry I should have mentioned I have Web Server and FTP applications running on the server. I guess if I were to edit the hosts file like above, I would not be able to access the server apps anymore. I was thinking that there might be some port forwarding or setting I might have missed out.

Sep 29 05 3:42 pm

Sorry I should have mentioned I have Web Server and FTP applications running on the server.

So can you access them with a domain name when sitting on the internal network?

So you have a camera listneing on 192.168.6.230:9018.

There are no problems connecting to it via the internet.
1. Where are you trying to connect to it on your internal network
a) From the WinGate machine
b) From another machine
c) From any machine on the network.

2. What connection method do the Clients on your internal network use to connect to the WinGate server
a) NAT
b) WinGate Internet Client
c) Proxy
d) Combination

Sep 29 05 4:04 pm

jamesc wrote:
Sorry I should have mentioned I have Web Server and FTP applications running on the server.

So can you access them with a domain name when sitting on the internal network?
Nope

So you have a camera listneing on 192.168.6.230:9018.
Yup

There are no problems connecting to it via the internet.
1. Where are you trying to connect to it on your internal network
a) From the WinGate machine
If I go through http://example.dyndns.net:9018 = Nope
If I go through http://192.168.6.230:9018 = Yes

b) From another machine
Assuming, the other machine is from the internet outside of the internal network:
If I go through http://example.dyndns.net:9018 = Yes
If I go through http://192.168.6.230:9018 = Nope

c) From any machine on the network.
If I go through http://example.dyndns.net:9018 = Nope
If I go through http://192.168.6.230:9018 = Yes

Ans : b) From another machine

2. What connection method do the Clients on your internal network use to connect to the WinGate server
a) NAT
b) WinGate Internet Client
c) Proxy
d) Combination

Ans : a) NAT

Sep 29 05 4:13 pm

I would recommend setting the host file on the clients on "your" internal network as recommended before.

If you also set it on your WinGate server (so you can access your domain name from from that box too) I am sure it will not affect your webserver.

Sep 29 05 8:20 pm

jamesc wrote:I would recommend setting the host file on the clients on "your" internal network as recommended before.

If you also set it on your WinGate server (so you can access your domain name from from that box too) I am sure it will not affect your webserver.

Hmm my Web server is at example.dyndns.net:80 and my FTP is at example.dyndns.net:21. If I point my host file to example.dyndns.net to my IP Camera, won't it mean I can't connect to my Server?

Sep 29 05 8:42 pm

Sorry, I thought you said that you are hosting the Web and FTP server at your place; not at DynDNS... I thought DynDNS just updates your DNS record when your public ip address changes

My suggestion is just the quick and easy way to allow domain names to conenct to servers in your local network

Sep 29 05 11:25 pm

jamesc wrote:Sorry, I thought you said that you are hosting the Web and FTP server at your place; not at DynDNS... I thought DynDNS just updates your DNS record when your public ip address changes

My suggestion is just the quick and easy way to allow domain names to conenct to servers in your local network

Besides domain names, even if I use the external IP, I still can't connect. Is there a way I could view the logs of wingate to see what gets block and what gets through? Not just the firewall logs, as in the logs of the port security. Maybe there's a route I can pre-program or something. I don't have this problem when I use the Windows XP firewall and ICS, so I'm pretty sure I can find a way to do it through Wingate.

Thanks for the loads of help!