Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Client ip and nat box

Created: 27 Sep 2010 • Updated: 02 Nov 2010 | 4 comments
TRL's picture
This issue has been solved. See solution.

We have an 8450 running outside our network / NAT box. Therefore we can't see any of our internal hostnames or IP addresses (10.x.x.x) only the outside NAT addresses (198.x.x.x). Sym tells me that this is expected and normal in this kind of design. OK so if everything looks like it comes from  198.161.x.100 from inside our network then how come in the GUI it can tell me that I have 269 clients? It must have some way of differentiating them? 

Discussion Filed Under:

Comments 4 CommentsJump to latest comment

KevK76's picture

If you take a look at the Custom Logs, what is showing up as the Local IP's?

Also, what networks have you defined as your Internal Networks on the Administration -> Configuration -> Networks page?

Kevin

TRL's picture

I am not the network guy so pardon my ignorance. In the loggs I only see the 198.x.x.x addresses assigned by our CISCO NAT box. The network guy tells me that I will never see the internal address as that is how NAT works.

KevK76's picture

Yes that's correct. If you do want to see the individual IP addresses then you'll want to have the Internet -> NAT device -> Web Gateway -> Core Switch in the network -> Internal clients.

Kevin

SOLUTION
TRL's picture

Thanks, that what I thought. Trouble is the CISCO 6509 has all in line modules and so we can't insert there. And our internal network uses fibre gig between all our buidling so it can't go there either.