Has anyone tried connecting to the Windows Server 2012 RC with DBISAM 4? For some reason, the code that allows connection from a workstation to Windows Server 2003 does not work in the newer server.

try
  dbaData.Close;
  with Session do begin
       Close;
       RemoteUser:='user';
       RemotePassword:='password';
       SessionName:='Default';
       SessionType:=stRemote;
       RemoteAddress:='192.168.1.23';
       RemoteHost:='testcs';
  end;
  dbaData.RemoteDatabase:='testcs';
  dbaData.Open;
  // The next line is never shown
  messagedlg('A connection to the database was successful', mtInformation, [mbOK], 0);
except
  messagedlg('A connection to the database failed', mtWarning, [mbOK], 0);
end;

The HOSTS file in the workstation has the line "192.168.1.23  testcs" within it and the DBISAM server is running at the server.

Frederick

Frederick
> Has anyone tried connecting to the Windows Server 2012 RC with DBISAM 4? For some reason, the code that allows
connection from a workstation to Windows Server 2003 does not work in the newer server.
>

I would guess that it is most likely a firewall issue.

John

John,

/*
I would guess that it is most likely a firewall issue.
*/

Even if I turn off the firewall, the code still fails. It is very unusual.

Frederick

Frederick,

Can you connect to the server using DBSys ?
Also, try it only with IP, setting RemoteHost to '' and see what happens .

--
Fernando Dias
[Team Elevate]

Fernando,

/*
Can you connect to the server using DBSys ?
Also, try it only with IP, setting RemoteHost to '' and see what happens .
*/

Sorry for the delay in replying.

Both methods of connecting with DBSys using both the server's IP address and host name or just the IP address only works. In fact, for some unknown reason, the connection code now works.

I see that turning off the firewall completely allows the connection to go through. Is this like hitting a fly with a sledgehammer? Would it be possible to turn on the firewall but setting something off/on to work?

The Windows firewall is not flexible in allowing incoming connections from specified IP addresses to be entered.

Frederick

Frederick,

<< The Windows firewall is not flexible in allowing incoming connections from specified IP addresses to be entered. >>

I'm not sure about Win 2012, I haven't seen it yet, but if it is like the firewall of Win Server 2008, you can in fact open specific IPs, protocols and ports. Look for the 'Advanced' settings of the firewall , or at least it's how it was called in Win 2008.
Sorry, I can't be more specific because I'm a bit outdated I'll have to look at the new Win Server soon.

--
Fernando Dias
[Team Elevate]

Fernando,

/*
I'm not sure about Win 2012, I haven't seen it yet, but if it is like the firewall of Win Server 2008, you can in fact open specific IPs, protocols and ports. Look for the 'Advanced' settings of the firewall , or at least it's how it was called in Win 2008.
Sorry, I can't be more specific because I'm a bit outdated I'll have to look at the new Win Server soon.
*/

I did the following on Windows Server 2008 Enterprise and the connection works:-

1.   Set the network location for the firewall to a private network. (Previously, it was set as a public network)
2.   Enabled the firewall.
3.   In the Exceptions tab, add a port for Telnet. The name can be anything (I use DBISAM), port is 12005 and scope is My network (subnet) only.

Ping, telnet and application connection all works! (I think the same settings on the Windows Server 2012 should work)

Thanks for your help.

Frederick

Frederick,

Be aware that you may also need port 12006 if you are going to use the
'Server Administration Utility' for remote administration of the server,
as well as if your applications are going to execute remote administrative
operations (the kind of operations that you can find in the utility, like
adding users or setting permissions).

--
Fernando Dias
[Team Elevate]

Fernando,

/*
Be aware that you may also need port 12006 if you are going to use the
'Server Administration Utility' for remote administration of the server,
as well as if your applications are going to execute remote administrative
operations (the kind of operations that you can find in the utility, like
adding users or setting permissions).
*/

Yes, noted. I purposely omitted the use of the server administration utility by users to ensure that there will be no support issues if non-technical savvy users bust up my configuration. The database server is set to handle one database and one administrator only.

Frederick