I received a report (still waiting for exact OS details) of a customer who has Lantastic and when they start the server, it then stops.

The server is Version 4.21 Build 2.

Any suggestions for things to look for?   

Lance R wrote:
> I received a report (still waiting for exact OS details) of a
> customer who has Lantastic and when they start the server, it then
> stops.  

Is it possible that Lantastic is not TCP/IP based?

Ralf

Apparently, it's an XP Pro machine and while it has Lantastic, it also has TCP/IP.
Apparently they do not conflict and Lantastic only accomodates file sharing with a networked DOS client.

So something must be blocking the server from starting.

Suggestions?     

XP Firewall I'm sure is one place to look.

Lance


"Ralf Mimoun" <nospam@rad-on.de> wrote:

Lance R wrote:
> I received a report (still waiting for exact OS details) of a
> customer who has Lantastic and when they start the server, it then
> stops.  

Is it possible that Lantastic is not TCP/IP based?

Lance R wrote:

> I received a report (still waiting for exact OS details) of a customer who
> has Lantastic and when they start the server, it then stops.
>
> The server is Version 4.21 Build 2.
>
> Any suggestions for things to look for?   

Get a copy of madexcept, compile it in and look what you get. I'd assume that
it's a filesharing exception. It might be a similar issue to Novell and other
older network systems that are not 100% compatible to the filesharing flags in
te winapi.

--

Hannes Danzl [NexusDB Developer]
Newsgroup archive at http://www.tamaracka.com/search.htm

I recently picked up Eurekalog, so I'll try that route...  See if an
exception is being generated.

Thanks for the idea.

Lance


Hannes Danzl[NDD] wrote:
> Lance R wrote:
>
>> I received a report (still waiting for exact OS details) of a customer who
>> has Lantastic and when they start the server, it then stops.
>>
>> The server is Version 4.21 Build 2.
>>
>> Any suggestions for things to look for?   
>
> Get a copy of madexcept, compile it in and look what you get. I'd assume that
> it's a filesharing exception. It might be a similar issue to Novell and other
> older network systems that are not 100% compatible to the filesharing flags in
> te winapi.
>

Lance,

<< I received a report (still waiting for exact OS details) of a customer
who has Lantastic and when they start the server, it then stops. >>

So, basically the database server process is still running, but it can't
bind/listen on the desired IP address/port ?  That is usually due to an
issue with some other process already listening on the given address/port.
If you use netstat -a, it will list all of the current connections and
bindings as well as what address/port they are using.  That should at least
tell you if something is using the port already.

--
Tim Young
Elevate Software
www.elevatesoft.com

Lance R wrote:

> I received a report (still waiting for exact OS details) of a
> customer who has Lantastic and when they start the server,


Wow!  I did not even know Lantastic was still around.  I have  not seen
it in years. What does it bring to the table these days that is not
already present in the OS?

Not my choice.  Just what some of my clients have.   The primary app the
clients have is DOS based and the computer their app is only DOS.  So
the networked computer that my app is on is XP Pro and has Lantastic in
order to provide file sharing.

Having or having not Lantastic is outside the scope of my app, so not
much I can do.



David Farrell-Garcia wrote:
> Lance R wrote:
>
>> I received a report (still waiting for exact OS details) of a
>> customer who has Lantastic and when they start the server,
>
>
> Wow!  I did not even know Lantastic was still around.  I have  not seen
> it in years. What does it bring to the table these days that is not
> already present in the OS?
>

I forgot about port conflicts.  The chances of a conflict with the
default DBISAM ports would be rare, but @#$@#$  happens.

After further working with the client, they've developed some very weird
issues and their OS tossed its cookies.  So I'll wait till their back up
and start again.

Thanks all for the ideas.

Lance

Tim Young [Elevate Software] wrote:
> Lance,
>
> << I received a report (still waiting for exact OS details) of a customer
> who has Lantastic and when they start the server, it then stops. >>
>
> So, basically the database server process is still running, but it can't
> bind/listen on the desired IP address/port ?  That is usually due to an
> issue with some other process already listening on the given address/port.
> If you use netstat -a, it will list all of the current connections and
> bindings as well as what address/port they are using.  That should at least
> tell you if something is using the port already.
>