At 01:48 PM 31/03/2005 -0800, you wrote:

> I had a feeling it had something to do with network services not being
> available, since the client can access the database when I'm logged onto
> the server. And, I imagine port 3050 is not open either when I'm not
> logged on. I added it to the exceptions tab of MS Firewall, but really
> didn't see any change in client access.

The port should be open at all times if it's to provide the service. BTW,
changing the firewall settings won't make any difference if the server is
already running. The port should be open already, before the service starts.

You can query the ports from the commandline, using the netstat command:

C:\Program Files\Firebird\Firebird_1_5\bin>netstat -an

Active Connections

Proto Local Address Foreign Address State

TCP 0.0.0.0:3050 0.0.0.0:0 LISTENING

That's the one that tells you that Firebird's port is open. If it doesn't
appear, then the network can't hear the service.

As a side-note, on XP, you can come to grief, I believe, because XP pleases
its sweet self about the order in which it starts up services. I seem to
recall reports of problems following one or other of the XP service packs,
where XP would start the Firebird service before it started port
services. Perhaps Simon Carter can throw some light?

> (when do you sleep!? - in Russia?)

Generally at night (more or less). No, I've never slept in Russia
(yet!). I sleep in NSW, Australia. Right now, my day (Friday) is just
beginning.

./hb