[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [FW1] ping or traceroute to own translated IP
There is a good reason for this. Internally, your machines should connect via the internal addresses of all machines. Here's a good explanation. -----Original Message----- From: Sukhpreet Singh [mailto:[email protected]] Sent: Saturday, September 23, 2000 1:53 PM To: '[email protected]' Subject: [FW1] ping or traceroute to own translated IP I have a machine(NT server 4.0) that is having trouble connecting to it's own translated IP. Can anyone think of a reason for that. I've gone through the list of NAT rules again and again and they seem to be correct. This is what I think is happening. The machine's IP is 172.16.1.5 (gw 172.16.1.1 on FW1) and it's translated to 204.5.211.33. When I ping 204.5.211.33, it gets a redirect from the gateway(172.16.1.1) and it begins to think it can reach 204.5.211.33 from it's own interface 172.16.1.5 which is wrong and therefore the problems. I'm not an expert at routing and would really appreciate if someone would help me fix this. ============================================================================ ==== To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ============================================================================ ==== begin 600 FireWall-1 FAQ- Can't Talk to Translated IP from Internal Net.url M6TEN=&5R;F5T4VAO<G1C=71=#0I54DP]:'1T<#HO+W=W=RYP:&]N96)O>2YC M;VTO9G<Q+V9A<2\P,3<Y+FAT;6P-"DUO9&EF:65D/3`P0D)$1$9#1#<R-4,P &,#$U,0T* ` end ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|