| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| I am trying to connect to a Edge device running 6.046. I have set up a remote site in the edge device and cannot make a connection via secure remote. I keep getting gateway not responding. I am tryin to connect remotely from a public network and I put in the public IP address of the DSL router which then NAT's to a local address. I keep getting the response Gateway not responding. DOes anyone in here have any expertise that may be able to help me out on this. Thanks, razorack |
| |||
| abusharif, I should have said that the DSL router forwards the traffic to the Edge device via a NAT'ed address of 192.168.1.5. DO you still think the NAT is an issue? Thanks for your help, razorack |
| |||
| I also am not seeing anything in our edge device logs that even shows a VPN connection but I do see alot of these entries when I try to connect via Secure Remote: 02062 27Sep2006 10:13:16 TCP 209.44.17.68 [SYN attack] 58956 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02061 27Sep2006 10:13:05 TCP 209.44.17.68 [SYN attack] 58901 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02060 27Sep2006 10:12:55 TCP 209.44.17.68 [SYN attack] 58857 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02059 27Sep2006 10:12:44 TCP 209.44.17.68 [SYN attack] 58778 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02058 27Sep2006 10:12:34 TCP 209.44.17.68 [SYN attack] 58641 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02057 27Sep2006 10:12:23 TCP 209.44.17.68 [SYN attack] 58488 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02056 27Sep2006 10:12:13 TCP 209.44.17.68 [SYN attack] 58367 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02055 27Sep2006 10:12:03 TCP 209.44.17.68 [SYN attack] 58190 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02054 27Sep2006 10:11:53 TCP 209.44.17.68 [SYN attack] 58066 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02053 27Sep2006 10:11:42 TCP 209.44.17.68 [SYN attack] 57960 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02052 27Sep2006 10:11:32 TCP 209.44.17.68 [SYN attack] 57854 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02051 27Sep2006 10:11:22 TCP 209.44.17.68 [SYN attack] 57784 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02050 27Sep2006 10:11:12 TCP 209.44.17.68 [SYN attack] 57748 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS) 02049 27Sep2006 10:11:01 TCP 209.44.17.68 [SYN attack] 57688 192.168.1.5 (VPN-1 Edge) 981 (SofaWare HTTPS |
| |||
| check that traffic that leaves ur securemote actually reaches the edge (under tools in edge iface or cli you can sniff traffic). What leaves ur client should reach the edges external interface, which is probably not happening atm. |
| |||
| try with ethereal -> http://www.ethereal.com/ __________________ misery is optional |
![]() |
| Thread Tools | |
| Display Modes | |
| |