Dear Helen,

Thanks a lot! You've been really clear! I'll try with this tomorrow.
I config Port # 3050 as an exception on my (SP2) Firewall. I will
also try deactivating it.

BR

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> At 01:17 PM 24/02/2005 +0000, you wrote:
>
>
>
> >Hello everyone!
> >
> >I have 4 PCs (with WinXP Pro) connected through a Workgroup. I'm

not

> >able to make a connection from one PC to a Firebird database

located

> >in another PC in the workgroup. I've been searching for connection
> >strings examples, but none was good for my case.
>
> No, you can't use workgroup filesharing for connecting firebird

clients to

> the server. On Windows, you have two choices of protocol: Named

Pipes and

> TCP/IP. TCP/IP is preferred because it is less noisy.
>
> For named pipes, you need to know the hostname of the server

machine. It

> must NOT be a share. Let's say its name is "DBServer". (Get this

name from

> the property sheet of the "My Computer" applet.)
>
> You need a client application on the client machine, and a copy of

the

> client library, fbclient.dll. (Many client tools need

fbclient.dll renamed

> as gds32.dll and placed in c:\Windows\System32.)
>
> The connection string for named pipes would be:
>
> \\DBServer\c:\Program Files\Firebird\Firebird_1_5\employee.fdb
>
> For TCP/IP, it would be
> DBServer:c:\Program Files\Firebird\Firebird_1_5\employee.fdb
>
> This part (c:\Program Files\Firebird\Firebird_1_5\employee.fdb)

must NOT be

> a share. You can set up an alias for this part in aliases.conf,

e.g.

>
> emp = c:\Program Files\Firebird\Firebird_1_5\employee.fdb
>
> Then your connection string can be
>
> \\DBServer\emp
>
> or
>
> DBServer:emp
>
> For the TCP/IP clients, open c:\Windows\system32\drivers\etc\hosts

and add

> the entry
>
> nnn.nnn.nnn.nnn DBServer
>
> where nnn.nnn.nnn.nnn is the IP address of the server's node in

the local

> network.
>
> ./hb