| Subject | RE: [ib-support] Interbase disconnecting all clients |
|---|---|
| Author | Paul M. |
| Post date | 2002-07-10T23:31:50Z |
Hi, Scott.
He was mapping the server's drive, then setting z:\thepath\theDBfile.gdb as
the database to connect to, assuming that z: is the mapped drive. The DB
Server is running on the NTServer whose drive is being mapped.
I recommended that he switched to TCP/IP to access the DB, which he did.
However, after a period of time, this caused the server to lock out all the
clients.
I think I've sorted out the problem now, though. He had a small app running
on the server that backed up the database at half hour intervals, which was
still accessing it via the path, rather than TCP/IP. Someone else has
informed me that if you use two different protocols to access the DB,
Interbase can crash. Therefore I'm pretty sure that this is the problem, and
that the disconnected machine was a red herring.
Does this sound right to the interbase gurus here?
Regards,
Paul Matthews
ProSouth Technology Solutions
P.O. Box 5191, Dunedin, NEW ZEALAND
FreePhone: 0800 IT SOLUTIONS (0800 487 658)
(International Callers: +64 3 453 4976)
Visit us at: www.prosouth.co.nz
-----Original Message-----
From: Scott Taylor [mailto:scott@...]
Sent: Thursday, 11 July 2002 5:04 a.m.
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Interbase disconnecting all clients
At 05:13 PM 09/07/2002, you wrote:
serving (running) ibserver?
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
He was mapping the server's drive, then setting z:\thepath\theDBfile.gdb as
the database to connect to, assuming that z: is the mapped drive. The DB
Server is running on the NTServer whose drive is being mapped.
I recommended that he switched to TCP/IP to access the DB, which he did.
However, after a period of time, this caused the server to lock out all the
clients.
I think I've sorted out the problem now, though. He had a small app running
on the server that backed up the database at half hour intervals, which was
still accessing it via the path, rather than TCP/IP. Someone else has
informed me that if you use two different protocols to access the DB,
Interbase can crash. Therefore I'm pretty sure that this is the problem, and
that the disconnected machine was a red herring.
Does this sound right to the interbase gurus here?
Regards,
Paul Matthews
ProSouth Technology Solutions
P.O. Box 5191, Dunedin, NEW ZEALAND
FreePhone: 0800 IT SOLUTIONS (0800 487 658)
(International Callers: +64 3 453 4976)
Visit us at: www.prosouth.co.nz
-----Original Message-----
From: Scott Taylor [mailto:scott@...]
Sent: Thursday, 11 July 2002 5:04 a.m.
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Interbase disconnecting all clients
At 05:13 PM 09/07/2002, you wrote:
>He recently switched to TCP/IP to connect clients to the IB6 server.like
>(Previously he was mapping the server's drive on each client, and accessing
>the DB through the mapped drive). Everything
>works fine until he disconnects the network cable on his laptop (also
>running the client). At this stage ALL clients on the network lose their
>connection to the IB server, which the application doesn't particularly
>:)What is the connection string on the clients?
>This doesn't happen if he maps the server's drive, and accesses the IB DBin
>this way.How do you access the database over a mapped drive? Which machine is
serving (running) ibserver?
>Theoretically, disconnecting one machine shouldn't cause the IB server toNot theoretically, verily. Something else is wrong here.
>drop all connections, but it does.
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/