Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread V4 Server Set-up problem
Mon, Mar 5 2007 4:41 AMPermanent Link

adam
Silly, Silly problem ... I really ought to be able to sort out myself.

Setting up V4 at a customers site, they have V3 running happily.

They have bought a new PC to run as server for V4. I have the DBSRVR running on
192.168.001.001, ports 12005 & 12006 as usual ...

I am trying to run SRVAdmin utility to set up the database.

Options are set up exactly as per the SRVR, 192. ... etc.

But when I log on (using the default password & username) I get a 11,276 "connection has
been lost" error.

--

Is there some setting on the new PC (set up Win XP Pro) that might be blocking me?

... If it is something like a port-setting or port-forwarding on the new PC could anyone
give me some advice about how to change it?? Smileyas it's not something I know much about.

Adam
Mon, Mar 5 2007 9:27 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Adam,

<< Silly, Silly problem ... I really ought to be able to sort out myself.

Setting up V4 at a customers site, they have V3 running happily.

They have bought a new PC to run as server for V4. I have the DBSRVR
running on 192.168.001.001, ports 12005 & 12006 as usual ...

I am trying to run SRVAdmin utility to set up the database.

Options are set up exactly as per the SRVR, 192. ... etc.

But when I log on (using the default password & username) I get a 11,276
"connection has been lost" error. >>

Are you running the version 3 dbsrvr on the same machine ?  If so, then the
issue is that you can't run both the v3 and v4 servers using the same ports
(12005 and 12006).  They have to bind to different ports.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Mar 6 2007 3:46 AMPermanent Link

adam
Are you running the version 3 dbsrvr on the same machine ?  If so, then the
issue is that you can't run both the v3 and v4 servers using the same ports
(12005 and 12006).  They have to bind to different ports.

--
Tim Young
Elevate Software
www.elevatesoft.com

------------------------

Dear Tim/All:

Basically no, V3 DBSRVR was run on the machine in the past but has been removed ... but that

can't have any impact can it? I only ever run it as an EXE not as a Windows Service so I

don't think it can still be affecting anything.

This is a serious / silly problem for me. I come up against it regularly & it always takes

more effort than I would like to set right. Its not DBISAM's problem, its always something

in the stupid way that Windows Networking "works" ... and I'm not knowledgeable enough about

networking to get round it fast.

--

Here's my DBSRVR ini:

; DBISAM Database Server Parameters INI File

[Server Parameters]
Server Name=FMServer
Server Description=Fullwell Mill Server 2007
Server Address=192.168.0.200
Server Port=12005
Server Thread Cache Size=20
Administration Address=192.168.0.200
Administration Port=12006
Administration Thread Cache Size=4
Configuration File=FMSys
Configuration Password=FMServer
; 0=main server allows unencrypted connections (default) 1=main server allows only encrypted
Encrypted Only=0
; Default encryption password is elevatesoft
Encryption Password=FMServer
; 0=show user interface (default) 1=hide user interface
No User Interface=0
; 0=overwrite log file (default) 1=append to log file
Append To Log=0
; 0=no large file support (default) 1=enable large file support
Large File Support=0.

--

My ServerAdmin utility is set to: IP 192.168.0.200 & port 12006.

The DBSRVR application is visible in the task bar & shows it is active when I right click.

--

I can ping 192.168.0.200 from the whole network.

If I run ServerAdmin on the server machine I get a 11280 error "connection cannot be

established".

--

I urgently need to fix this problem & have no real idea about where to get more detailed

help. Any suggestions (networking information?), including stuff I have to pay for

gratefully received. I would love to understand this problem well enough to be able to fix

it quickly whenever it occurs!

Adam

Tue, Mar 6 2007 5:18 AMPermanent Link

adam
Dear All,

Problem fixed ... though I am still not reallyany wiser.

... Removing the specific IP address from my DBSRVR.ini file (infact deleting the DBSRVR.ini file altogether) so that the Server is working on ALL ADDRESSES has fixed the problem.

I can now log on to it via SRVAdmin from anywhere. PHEW.

... I would still like to know why it didn't work on a specific address though! The only difference is that the new machine is Win XP Pro, newly installed, the old machine was Win2000. The
joys of Windows Networking.


Adam
Tue, Mar 6 2007 12:54 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Adam,

<< Problem fixed ... though I am still not reallyany wiser.

.. Removing the specific IP address from my DBSRVR.ini file (infact
deleting the DBSRVR.ini file altogether) so that the Server is working on
ALL ADDRESSES has fixed the problem.

I can now log on to it via SRVAdmin from anywhere. PHEW.

.. I would still like to know why it didn't work on a specific address
though! The only difference is that the new machine is Win XP Pro, newly
installed, the old machine was Win2000. The joys of Windows Networking. >>

To use a specific IP address, you have to make sure that the connecting
client is actually using the same IP address, and not 127.0.0.1 or
LocalHost.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image