I have a customer that cannot connect to the EDB server when it is run as a service. They have no problem connecting to the server when it runs as an application. The server is on a local folder not on a network folder. It appears to be installed correctly and appears to be started but they just can't connect to it. I don't see how it could be a firewall issue since they can connect with the server application.

Any ideas?

On 6/11/2014 11:23 PM, Michael Fullerton wrote:
> I have a customer that cannot connect to the EDB server when it is run as a service. They have no problem connecting to the server when it runs as an application. The server is on a local folder not on a network folder. It appears to be installed correctly and appears to be started but they just can't connect to it. I don't see how it could be a firewall issue since they can connect with the server application.
>
> Any ideas?

I'd suspect firewall still.

Running as a service would normally run it under a different user
account to start with so it's not exactly same as running as an app. I'd
make sure there is a firewall exception for the edb server.

You can also make sure it's actually running and listening on the port
properly (i personally prefer TCPView :
http://technet.microsoft.com/en-us/sysinternals/bb897437 but netstat
would work as well).

Raul

Raul wrote:

> I'd suspect firewall still.

Me too. Also try telnet to the port - you will get something of a
connection even if it disconnects. If there is no connection, then it
is closed.

Firewalls typically allow localhost connectivity, and stop remote.

telnet <server> <port>

--

Matthew Jones

Raul wrote:

On 6/11/2014 11:23 PM, Michael Fullerton wrote:
> I have a customer that cannot connect to the EDB server when it is run as a service. They have no problem connecting to the server when it runs as an application. The server is on a local folder not on a network folder. It appears to be installed correctly and appears to be started but they just can't connect to it. I don't see how it could be a firewall issue since they can connect with the server application.
>
> Any ideas?

I'd suspect firewall still.

Running as a service would normally run it under a different user
account to start with so it's not exactly same as running as an app. I'd
make sure there is a firewall exception for the edb server.

You can also make sure it's actually running and listening on the port
properly (i personally prefer TCPView :
http://technet.microsoft.com/en-us/sysinternals/bb897437 but netstat
would work as well).

Raul

Well they tried an application firewall exception to no avail. Also tried setting incoming and outgoing firewall rules to allow 12010 on any network for any program. With the service, netstat shows the port is inactive and they cannot telnet to the port. With the desktop server netstat shows the port active and telnet works.

On 6/12/2014 11:03 PM, Michael Fullerton wrote:
> With the service, netstat shows the port is inactive and they cannot telnet to the port. With the desktop server netstat shows the port active and telnet works.
>

When you say inactive do you mean it does not even appear in netstat ?

Normally with edb server service (or app) running and you do "netstat
-a" you should see an entry like this "TCP   0.0.0.0:12010 <host name>:0
LISTENING".

If that's missing then something has gone wrong and edb server has not
even been able to bind to the port.

I just tried it here on one of our windows 2012 test servers using the
2.17b1 64bit version (one in servers\edbsrvr\win64) and it works for me.

Here's steps i did :

1. Used edb manager to create a local config first (in c:\edbdata) since
i did not have one. Also created a DB just to have one to confirm later
i'm connecting to correct config remotely.

2. Ran edb server as app and configured to use the local config
(c:\edbdata). Also changed temp folder to (c:\edbdata\temp) but
otherwise left all other settings intact

Since it's running as a service it should not reference any of the
normal user folders since those may not exist later.

3. Started elevated command prompt (right click and run as
administrator) installed the service (i.e. navigate to
...\servers\edbsrvr\win64) and run "edbsrvr -install". Got a prompt
service was installed ok.

4. Went to control panel for services and started the service.

5. At this point i can connect locally using loopback (127.0.0.1) but
firewall is still blocking remote connections from rest of LAN so i
added a program based exception (for ..\edbsrvr\win64\edbsrvr) to allow
connections.

At this point i'm able to connect to this from my pc. Even restarted the
server to make sure everything works after - and it does.

I'd say in general this works as expected so something on your server or
config still.

Raul