I upgraded from EDB v2.11b3 to EDB 2.16b2.  I am having trouble with my remote sessions.  (It previously worked - really).

The message given is:

ElevateDB Error #1100 A connection to the server at wck cannot be established (Socket error: A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host failed to respond (10060))

I have 2 computers – lets call them wck and wck2.  wck has the EDBServer installed as a service.

In the early days of EDB, I spent some time setting up my modem to connect to remote sessions from wck2 using both internal and external IP addresses.

So I could connect to a remote session using port 12010 and the following options:
* host name: wck
* host name: wck.dyndnz.biz
* ip address: 192.168.15.103 (internal address)
* ip address: 120.150.130.219 (external address)

After installing EDB 2.16b2, I can no longer connect to any remote sessions from wck2.
I can connect to remote sessions on wck using the host name wck or ip address 192.168.15.103 but not the external addresses.

I have another application (Remote Host).  The router has been configured to use port forwarding for both the EDB Server and Remote Host application.  The Remote Hosting application is working using any of the 4 addresses to connect (wck, wck.dyndnz.biz, 192.168.15.103, 120.150.130.219).   

If you have managed to get to this point – could you provide any clues as to what is happening?

Many thanks
Richard

Richard


The only thing that readily comes to mind is that 2.16 combined ANSI and UNICODE into the engine so you need to make sure everything is set to use ANSI or UNICODE not ANSI at one end and UNICODE at the other.

Roy Lambert

Richard

As Roy says, there is a new property on the EDBSession "CharacterSet" it can be csUnicode (the default) or csANSI.

When you configure the EDBSRVR there is a similar property on the remote server. Both must be the same or you will get the error you have reported & the Server will not be able to communicate with the client.

On 4/29/2014 4:48 AM, Adam Brett wrote:
> As Roy says, there is a new property on the EDBSession "CharacterSet" it can be csUnicode (the default) or csANSI.
>
> When you configure the EDBSRVR there is a similar property on the remote server. Both must be the same or you will get the error you have reported & the Server will not be able to communicate with the client.
>

I king of agree with both Roy and Adam except it looks like Richard can
connect from local host. I would have expected ansi/unicode issues to
come into play here as well.

Hence if that's not the case then i'd check EDB server settings and make
sure the listening IP and ports are correct - any chance the EDB server
was on non-standard port which got reset? NExt thing would be to check
the IP settings end-to-end including router.

Raul

Richard,

It could also be your software firewall if you have one installed. When you updated the EDBSrvr it is a new .exe file so the firewall may be blocking it.

Barry

Thank you Roy, Adam and Raul.

I have check (and rechecked) the ansi/unice settings and they all consistent.

The port settings and router all appear to be OK and unchanged from the time it was last working.

Richard . .



>
> When you configure the EDBSRVR there is a similar property on the remote server. Both must be the same or you will get the error you have reported & the Server will not be able to communicate with the client.
>

I king of agree with both Roy and Adam except it looks like Richard can
connect from local host. I would have expected ansi/unicode issues to
come into play here as well.

Hence if that's not the case then i'd check EDB server settings and make
sure the listening IP and ports are correct - any chance the EDB server
was on non-standard port which got reset? NExt thing would be to check
the IP settings end-to-end including router.

Raul

Thanks Barry.  Windows Firewall was blocking the EDB Server.  I have being trying to work that one out for days.

Richard,



<<It could also be your software firewall if you have one installed. When you updated the EDBSrvr it is a new .exe file so the firewall may be blocking it.

Barry>>