Internal/External IP Device Access

[Smithy10]

I have a Camera configured on my LAN with a specific port only allowed. A static (inside,outside) statement is configured and conduit statement is configured on the firewall to restrict/allow access through the firewall.

If we attempt to connect to its real IP address (internal to internal) no problem. If we attempt to connect to the DNS entry from inside the firewall we are unable to connect. Connection is possible over the Web as long as we are not on the internal network the actual device resides upon.
We are using a Cisco PIX firewall and access list etc are confured. Is this a general restriction with FIrewalls and Internall/External access ?
e.g Device Internal address is 192.168.100.200 with a specific port number so we can from IE connect to this on LAN. IF we attempt to connect from LAN to the "real" DNS world wide wibe entry we are unable to connect. although, if I connect from my home conenction device is fine.

 

[TalentedFool]

Sounds like it's a internal DNS issue more than a Router/Firewall. Are you using an internal DNS server on your LAN? If so, put an entry in there for it the same as your ISP has for the server.

We had a simular sort of problem with a webServer running a DB App.

~ Remember - Nothing is Fool Proof to a Talented Fool ~

 

[tomsducati]

Sounds to me like a redirect issue..which the pix doesn't like.

Using your DNS, your traffic hits your PIX (assuming it's the default gateway to the internet) and then wants to come back into your LAN. Because the PIX doesn't want to pass traffic back to the same interface which it entered, you can't get to where you want to.

When you use the real 192.168.x.x ip, you were able to connect fine since you just want to the destination directly.

Check out the logs on the PIX and let us know if this is the case.

 

[Smithy10]

May be a silly question, I have logging turned on the PIX firewall "logging on" so what and how is the bets way to look at this info. show logging just shows the status not the information.
Appreciate details

 

[tomsducati]

You've enabled logging, but haven't told it what to log.

Try this command:

logging buffered informational