tcp_gsp Can't Connect Notice Message 1

[slider5]

I am receiving alot of the following log messages:

Message #228 tcp_gsp: can't connect to x.x.x.x (IP of host in service zone) port 443 (local port 0 already in use, retrying.)

I get these every few seconds. This NT IIS 4.0 host named above only accepts SSL connections and sits in the service zone.

Raptor 6.5 NT SP6 all patches
running on single processor PIII box
w/ 3 NIC's (outside, inside and service zone)

Any ideas would be appreciated. Thanks

Steven Schnee
PFCU

 

[daka]

Perhaps you need to enable ssl over http on your firewall. You can do so from within Raptor RMC interface. After getting into RMC, expand Access Controls, then Rules. Locate your rule that allows http out via the external interface. Open up the properties on that rule (right click+properties). Select the service tab, and single click on the http* service. Click on the configure button to the lower right of the window. Select the option for 'Allow HTTP over SSL...', and specify which ports you want to open up. Save and reconfigure and you should be go to go. Hope this helps.

 

[slider5]

Thanks for the advice daka. I already have both https and http over SSL going to this box. I'm not sure what the differences are between the two, but from what I understand http over SSL is for non-proxied connections?

 

[grimland]

Hey how did you get the NIC cards to be recognized and running (inside and outside) on one machine. I can't figure it out. Thanks buddy.

 

[slider5]

First make sure your OS recognizes all the NIC cards.
I assume you are working with 3 NICS
Assign an inside address to NIC#1 in TCP/IP properties.
plug it into your Intranet hub
Assign an inside address to NIC #2 and plug it into your DMZ hub.
Assign an outside routable address to NIC #3 and plug it into your Internet hub (don't actually do this until you have Raptor up and running with confidence)

When you install Raptor, it will recognize your NIC cards. It will ask you if you want each interface to be an inside or outside interface. For NIC #1 and #2 you want to be inside interfaces, and NIC #3 you want to be outside.

Make sure to add redirects for all DMZ hosts. Raptor will handle this routing very nicely.

 

[billhome]

Do you have a gsp on 443/tcp? Check under protocols, sort by ports and look for 443/tcp. There may be a port conflict? Try a changelog from the cmd prompt, then check logs, what is happening when FW comes back up? What is listening where. Let us know.