CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3.
2. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > SmartView Tracker/Logging And Alerting
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2006-09-04
Junior Member
 
Join Date: 2006-09-04
Posts: 21
Rep Power: 0
soundsfuzzy has an average reputation (10+)
Default Destination Name not resolving to Node Name

Hello

Need some help, currently in SmartView Tracker the destination name is not being resolved to the node name (Host Name) in checkpoint.

The case is i am looking at traffic coming into the firewall to our mailserver which has a static NAT address. The destination shows up as a IP address plus a bit of a host name (which happens to be our ISP), i do have resolve IP enabled. I can tell it is to our mailserver as it does include the NAT address in it, but it should show up as the Node Name which is in the firewall?

Does anyone know how to fix this.
Reply With Quote
  #2 (permalink)  
Old 2006-09-05
Senior Member
 
Join Date: 2005-08-29
Location: Upstate NY
Posts: 1,670
Rep Power: 5
chillyjim has an average reputation (10+)
Send a message via AIM to chillyjim Send a message via Skype™ to chillyjim
Default Re: Destination Name not resolving to Node Name

The log server (normaly the SmartCenter) or the client PC running SVT (I forget which, but I think its the latter) needs to be able to resolve the IP address to a name.

Are you using an automatic nat rule for the mail server? If so you should still be able to resolve to the object's name.
Reply With Quote
  #3 (permalink)  
Old 2006-09-05
Junior Member
 
Join Date: 2006-09-04
Posts: 21
Rep Power: 0
soundsfuzzy has an average reputation (10+)
Default Re: Destination Name not resolving to Node Name

I am using automatic NAT, for what i am seeing is it is the reverse dns what is showing up because their is a reverse dns PTR record for the IP address. I got the isp to change the reverse entry to see what happened and it showed the changed reverse entry.

So it is not looking in the host nodes for the name? I have looked in the tracker on the firewall itself and on the a remote console as well?

Seems not to be resolving on any of the incoming connection to the node name, but outgoing is fine?
Reply With Quote
  #4 (permalink)  
Old 2006-09-06
Senior Member
 
Join Date: 2006-07-28
Location: New Zealand
Posts: 857
Rep Power: 3
northlandboy has an average reputation (10+)
Default Re: Destination Name not resolving to Node Name

As I recall, it only looks at the objects primary IP, or extra interfaces if added - so it won't pick up the NAT entry.

If this is causing you a real problem, just create an object with the external NAT address. It's not that big a deal.

Another reason I don't really like auto NAt, although this is pretty low down - I don't really rely on the objects all that much, it's easier to use the IP addresses.

Oh and I think Jim is right about it being the client that does the DNS resolution, not the Server.
Reply With Quote
  #5 (permalink)  
Old 2006-09-07
Junior Member
 
Join Date: 2006-09-04
Posts: 21
Rep Power: 0
soundsfuzzy has an average reputation (10+)
Default Re: Destination Name not resolving to Node Name

got the isp to change the reverse lookup ptr, so now they show a bit better.

Thanks for the all the help
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -7. The time now is 18:28.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0