Hi Team,
Windows Server 2012 R2.  EDBSrvr 2.30b4.
I am not at all familiar with how this all works..
I asked my Customer to open the Server PC Firewall for Port 12010 for EDBServer.
Attached in screenshot 1 is what he has done.
I can access the EDB Server with a small test app I made using 127.0.0.1 port 12010, however if I change the IP to 192.168.1.35 which is the server pc IP address according to ipconfig, then the app doesn't connect.
Should I be able to ping 192.168.1.35:12010?
Does what has been done for the Inbound Rules need to be replicated for the Outbound Rules?
If not, what else needs to be looked at pls?

Regards & TIA,
Ian

Ian Branch wrote:

> I can access the EDB Server with a small test app I made using 127.0.0.1 port 12010, however if I change the IP to 192.168.1.35 which is the server pc IP address according to ipconfig, then the app doesn't connect.
> Should I be able to ping 192.168.1.35:12010?
> Does what has been done for the Inbound Rules need to be replicated for the Outbound Rules?

The firewall looks good to me. You shouldn't be able to ping it, because ping uses a different port, but try telnet to that as
telnet  192.168.1.35 12010
that should connect. Type a bit and you'll probably get some garbage response and a disconnect, but it shows the port is open.

However, you have not mentioned some key parts of the jigsaw - are you trying to connect from within the network, or from outside? That IP is internal only, and the router would have to be involved if external. (Also not a good idea really!) Any other things like this is a cloud computer that we should be aware of?

Beyond that, I'm not familiar enough with EDB Server to help further, but that you can connect locally shows it is probably networking.

--

Matthew Jones

The only difference from our firewall settings is the we allow any remote port, not just 12010 (or whatever port we're using for the server).

No outbound rules are configured on our servers for EDB. FWIW, we wrote a utility to create the firewall rules as part of our server-side installation routine.

Charles Bainbridge wrote:

> allow any remote port, not just 12010

Good spot! Yes, that should be any, because clients use any port. Probably the fix...

--

Matthew Jones

"Matthew Jones" wrote:
The firewall looks good to me. You shouldn't be able to ping it, because ping uses a different port, but try telnet to that as
telnet  192.168.1.35 12010
that should connect. Type a bit and you'll probably get some garbage response and a disconnect, but it shows the port is open.

I.B. - Ahhh Will try that - Tks.

However, you have not mentioned some key parts of the jigsaw - are you trying to connect from within the network, or from outside? That IP is internal only, and the router would have to be involved if external. (Also not a good idea really!) Any other things like this is a cloud computer that we should be aware of?

IB - All internal LAN.

IB - Thanks for your thoughts/suggestion.
Ian

Charles, Matthew,
Tks.  Will get the remote Port opened.

Regards,
Ian

That fixed it.  All good now.
Tks Guys.

Ian

That fixed it.  All good now.
Tks Guys.

Ian