I write Delphi Apps (D11) used in a standard LAN situation in offices and factories. The same Apps are also used on laptops in a "travelling salesman" mode, with a local copy of the data, which is updated via EDB replication.

I have built my own Server.exe to replace EDBSRVR.exe. It started as a copy of the EDBSRVR code Tim supplies as a starting point.

It works well in single machine "travelling salesman" set ups, connecting via 127.0.0.1, but when installed on LANs and WANs other machines cannot connect to it. Connections to EDBSRVR are always easy and quick.

I realise this is a vague problem, but does anyone have any idea why my own Server.exe would fail over a LAN whilst working with connections on the same machine?

Adam

Adam


Its possible that I'm misunderstanding the problem, and my knowledge may be faulty, but as I understand it 127.0.0.1 is the local machine and you can't connect to it from anything other than the local machine.

Roy Lambert

Sorry if I was unclear Roy,

What I mean is that on the "Salesmen" machines I run my Server.exe and users connect using 127.0.0.1, this works.

When I run my Server.exe on a server machine, and try to get users to connect to it from a separate machine on the network using (say) 192.168.xxx.yyy I don't get a connection. If I swap out my Server.exe and replace it with edbsrvr.exe (same IP and Port) it connects fine.

So something in my Server.exe seems to fail the jump out to a LAN setting.

Adam


If Tim's server works and your's doesn't then I suspect your code. How's that for a vague answer to a vague question  

I'm still suspicious of that 127.0.0.1 approach. I assume that the machines (or better still your test machine) where this software works correctly have a real IP address if so try using that for your software. If that doesn't work then somewhere I'd guess you're checking the IP address and rejecting it.

I'm willing to have a look at the code to see if I can spot anything but I'm still on D2007 so probably can't compile but I can put eyeballs on it.

Roy Lambert

<<
Adam Brett wrote:

I write Delphi Apps (D11) used in a standard LAN situation in offices and factories. The same Apps are also used on laptops in a "travelling salesman" mode, with a local copy of the data, which is updated via EDB replication.

I have built my own Server.exe to replace EDBSRVR.exe. It started as a copy of the EDBSRVR code Tim supplies as a starting point.

It works well in single machine "travelling salesman" set ups, connecting via 127.0.0.1, but when installed on LANs and WANs other machines cannot connect to it. Connections to EDBSRVR are always easy and quick.

I realise this is a vague problem, but does anyone have any idea why my own Server.exe would fail over a LAN whilst working with connections on the same machine?

Adam
>>


Adam

As you said hard suggest anything but i would check few things

1. What IP is your server listening on - is it using 0.0.0.0, host name etc ?

2. Can you confirm with netstat (Sysinternals TCPView) that TCP port is actually listening ?

3. if you telnet into the port does it connect - if yes then TCP socket is up , if not then it's either not listening, on different IP (like localhost or firewall issue.

Raul

Adam Brett wrote:

> I write Delphi Apps (D11) used in a standard LAN situation in offices
> and factories. The same Apps are also used on laptops in a
> "travelling salesman" mode, with a local copy of the data, which is
> updated via EDB replication.
>
> I have built my own Server.exe to replace EDBSRVR.exe. It started as
> a copy of the EDBSRVR code Tim supplies as a starting point.
>
> It works well in single machine "travelling salesman" set ups,
> connecting via 127.0.0.1, but when installed on LANs and WANs other
> machines cannot connect to it. Connections to EDBSRVR are always easy
> and quick.
>
> I realise this is a vague problem, but does anyone have any idea why
> my own Server.exe would fail over a LAN whilst working with
> connections on the same machine?
>
> Adam

Could be a very simple firewall setting which blocks access. Even if
firewall blocks everything, access to 127.0.0.1 is always possible.

Sounds like firewall problem.

Check if edbsrvr has an inbound rule on your server machine and your custom EDB-Server doesn't. Sometimes an Antivirus can also chip in if your custom server doesn't have exe information (vendor, product name etc.) which makes it look "suspicious"...you should make exceptions for it.