unable to connect to server

[Serge17]

Well.. there is supported.. and then there is possible...

I'm assuming this for a lab box since a 4200 is a pretty sad box for a mgmt server.

crack the box open (oh noes!), look at the chipset to see what max ram it an really supports and do what you need. If you want to make it a pure mgmt config do a fresh install, don't complete the wizard then look at config_system script and try making it mgmt only server. Might not work.. but then again that is a shell script so take at look at what its doing and figure it out.

While your at it put a hard drive in. Maybe even a SSD? Its just a intel box with intel nics in it. Should be possible. Supported? Nopers..

[Expert@cp-krm:0]# config_system --dry-run --config-file /var/log/template1.cfg
dos2unix: converting file /var/log/template1.cfg to UNIX format ...

Validating configuration file: Failed
Security Management must be false

[jflemingeds]

[Expert@cp-krm:0]# config_system --dry-run --config-file /var/log/template1.cfg
dos2unix: converting file /var/log/template1.cfg to UNIX format ...

Validating configuration file: Failed
Security Management must be false

I hope the humor translates. But come on. You going to let a shell script tell what is and isn’t possible? Use the source Luke.

[PeterSmith78]

Looks like my original post has been hijacked by a bunch of people having similar issue.
My management server SEEMS to be functioning OK now (I amended one of the "clients" files to "all" rather than a list of IP addresses and I could then connect via smart console, push a policy etc but to be honest I'm not sure if this is what fixed it) However I'm still seeing the same error message when executing server status.sh which is a bit disturbing and makes me think there is an issue lurking.
[Expert@FWMANAGE01:0]# $MDS_FWDIR/scripts/server_status.sh
Checking server status. Please wait...
Enabling local sic. Setting cp.ssl_local.certificate.check=local
Server is up - but not ready to receive connections (fwm might be down or busy)
[Expert@FWMANAGE01:0]#

I've contacted our "support Partners" and uploaded a whole bunch of information to them but they seem clueless. I'm starting to wish we'd bought a couple of ASAs. Much less scary in a production network.

[PhoneBoy]

Your support partner should be opening a ticket with Check Point support on this if they haven't already.
Please ask them for the SR number and send to me in a Private Message.

[PeterSmith78]

Many thanks Phone boy. I have sent a message (was finally escalated to checkpoint....)

[wabafet]

Hi, how did you fix the issue, can you share it here ? I am having the same problem connecting the smart client to both R80.10 and R80.20 management servers in AWS.
Thanks,
Wabafet

Looks like my original post has been hijacked by a bunch of people having similar issue.
My management server SEEMS to be functioning OK now (I amended one of the "clients" files to "all" rather than a list of IP addresses and I could then connect via smart console, push a policy etc but to be honest I'm not sure if this is what fixed it) However I'm still seeing the same error message when executing server status.sh which is a bit disturbing and makes me think there is an issue lurking.
[Expert@FWMANAGE01:0]# $MDS_FWDIR/scripts/server_status.sh
Checking server status. Please wait...
Enabling local sic. Setting cp.ssl_local.certificate.check=local
Server is up - but not ready to receive connections (fwm might be down or busy)
[Expert@FWMANAGE01:0]#

I've contacted our "support Partners" and uploaded a whole bunch of information to them but they seem clueless. I'm starting to wish we'd bought a couple of ASAs. Much less scary in a production network.