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 > Installing And Upgrading
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2007-01-24
Senior Member
 
Join Date: 2006-11-23
Posts: 159
Rep Power: 2
antonyso88 has an average reputation (10+)
Default TCP Connectivity Failure (Port =18191) Error No. 10

I did unload both gateway policy. fw unloadlocal then install successful. But when i install again, it failed with the message "TCP Connectivity Failure (Port =18191) Error No. 10 "

My gateway module was Nokia IP390 with R61 and smartcenter is Solaris.
Reply With Quote
  #2 (permalink)  
Old 2007-01-24
Senior Member
 
Join Date: 2006-01-26
Location: Moscow, Russia
Posts: 706
Rep Power: 3
kva.kva has an average reputation (10+)
Default Re: TCP Connectivity Failure (Port =18191) Error No. 10

May be your policy block this connection.
Did you disable implied rules for CP control connections?
Try telnet from SmartCenter and check traffic on module by fw monitor.
Reply With Quote
  #3 (permalink)  
Old 2007-01-24
Senior Member
 
Join Date: 2006-11-23
Posts: 159
Rep Power: 2
antonyso88 has an average reputation (10+)
Default Re: TCP Connectivity Failure (Port =18191) Error No. 10

I solved the problem because anti-spoofing on my internal network. Thanks for your help.
Reply With Quote
  #4 (permalink)  
Old 2007-01-24
Senior Member
 
Join Date: 2005-08-29
Location: Upstate NY
Posts: 1,660
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: TCP Connectivity Failure (Port =18191) Error No. 10

For people's reference, this is the most common cause of this error I've seen. So before you start hunting all over the place, look at the anti-spoofing settings on your gateways.

BTW I see the about once a week and often from people that know better.
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 12:31.


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