Dear All,

Sorry to be asking another question ... I've been asking too many in recent days.

I have this DBSRVR running on a LAN. Initially everything seemed to be going wrong, but
that was mainly because the Server had been infected with a Virus virtually out-of-the-box
before installed Virus software was updated!

Now it is clean, BUT I cannot get DBSRVR to run on a specific IP.

I have altered the DBSRVR.INI as I always do, and even tried the run-time switch

"c:\DBServer\DBSRVR.exe /SA 192.168.0.1"

but when I check the DBSRVR says that it is listening on "All Addresses" and if I try to
access it on 192.168.0.1 I get nothing.

I can still connect on the server itself with an IP of 127.0.0.1 ... which really confuses me!

Adam

adam


firewall?

Roy Lambert

Adam,

<< Sorry to be asking another question ... I've been asking too many in
recent days. >>

Yes, I'm afraid that you've reached your quotient and will have to refrain
from asking any more until the first of next month.

<< I have this DBSRVR running on a LAN. Initially everything seemed to be
going wrong, but that was mainly because the Server had been infected with a
Virus virtually out-of-the-box before installed Virus software was updated!

Now it is clean, BUT I cannot get DBSRVR to run on a specific IP.

I have altered the DBSRVR.INI as I always do, and even tried the run-time
switch

"c:\DBServer\DBSRVR.exe /SA 192.168.0.1"

but when I check the DBSRVR says that it is listening on "All Addresses"
and if I try to access it on 192.168.0.1 I get nothing.

I can still connect on the server itself with an IP of 127.0.0.1 ... which
really confuses me! >>

Is the DBSRVR process running as a service or as a normal application
process ?  Did you verify that the server was not already running when you
started the new dbsrvr process, i.e. that you don't have multiple instances
of the database server running by accident ?

--
Tim Young
Elevate Software
www.elevatesoft.com

I am not yet running it as a service, I'm just trying to get it started.

I have created a shortcut to the DBSRVR I right click on the icon & add the "/SA
192.168.0.1" section onto the end of the "Run in" section.

The INI file also sets the Server Address.

On my development machine its fine, I open the server & it shows the Server Address ... on
the customers machine it just shows "All Addresses"

...

Adam,

<< I have created a shortcut to the DBSRVR I right click on the icon & add
the "/SA 192.168.0.1" section onto the end of the "Run in" section. >>

Hmm, you might want to put the parameters in the actual Target edit box
instead.   That's where I always put it and it works just fine.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Adam,

<< I have created a shortcut to the DBSRVR I right click on the icon & add
the "/SA 192.168.0.1" section onto the end of the "Run in" section. >>

Hmm, you might want to put the parameters in the actual Target edit box
instead.   That's where I always put it and it works just fine.

--

Tim,

Sorry I expressed myself badly before. I do write the command line after the DBSRVR.exe in the "Target" edit box, I was writing from memory &
forgot what it was called.

On my laptop I set the DBSRVR up with command line & it works, on their machine I still have "all addresses" as the address (and can only open
SRVAdmin on 127.0.0.1) even though I have used an INI file & the command line switch.

What could be going wrong?

Is it possible that their network limits use of some IP addresses? (I am using 192.168.0.1, but also tried on 10.0.0.1) and if so, how can I check
which ones might be available on the network?

Adam

Adam,

In the server shortcut's Properties|Target, try writing the parameter without a space
(e.g. /SA127.0.0.1).  Does that make a difference?  On my computer, "/SA 127.0.0.1"
results in the Main Address being listed as "All addresses"--if I take away the space, the
Main Address becomes 127.0.0.1.

Charles Tyson

Adam,

Firstly, can I ask why you are trying to set the IP address?

If my understanding is correct, this setting only comes into play when the
PC acting as the server has more than one network interface, and you only
want to allow incoming access through one of them.

Secondly, where did you get the idea that you should set 192.168.0.1?

If you open a command prompt window, and type ipconfig, you will see one
set of details for each network interface in the machine.  This will tell
you what IP address range is in use on each network interface.

If the PC is connected to a router whose DHCP server is allocating the IP
addresses, then it is highly likely that the router will have allocated
192.168.0.1 for itself.  See the Default Gateway line in the ipconfig
display.  The IP address that the PC is known as on each network is listed
on the IP Address line of the ipconfig display.

--Bill Sparrow--