Subject | Re: Whitepaper on firewall-configuration? |
---|---|
Author | Adam |
Post date | 2005-07-28T05:10:41Z |
John,
Basically in a nutshell.
Server listens to port 3050
Client needs to talk to server on 3050.
From most firewalls, you can talk "outwards" to whatever port you want,
and you just need to port forward from firewall to the server.
To Diagnose it works ok
From the client, open a cmd window
ping DBServer
Must resolve to an IP address!
telnet DBServer 3050
If it goes black, all is good, if it says connection refused, go to the
server
telnet localhost 3050
If there is still problems, check FB is installed and running. If it
works from here, Firewall is blocking something. In most cases it is
just a case of choosing port forwarding on the firewall and mapping
port 3050 on the firewall to 3050 on the servers IP address. It gets
trickier if you use events because you need to play around with
Firewalls at both ends.
Adam
Basically in a nutshell.
Server listens to port 3050
Client needs to talk to server on 3050.
From most firewalls, you can talk "outwards" to whatever port you want,
and you just need to port forward from firewall to the server.
To Diagnose it works ok
From the client, open a cmd window
ping DBServer
Must resolve to an IP address!
telnet DBServer 3050
If it goes black, all is good, if it says connection refused, go to the
server
telnet localhost 3050
If there is still problems, check FB is installed and running. If it
works from here, Firewall is blocking something. In most cases it is
just a case of choosing port forwarding on the firewall and mapping
port 3050 on the firewall to 3050 on the servers IP address. It gets
trickier if you use events because you need to play around with
Firewalls at both ends.
Adam