On Wed, 09 Nov 2011 03:58:15 -0000, "technisoft2005"
<preber@...> wrote:

> --- In firebird-support@yahoogroups.com, Mark Rotteveel <mark@...>

wrote:

>>
>> On Tue, 08 Nov 2011 03:40:55 -0000, "technisoft2005"
>> > Experimenting a bit I find that there is no problem when using the

XNET

>> > protocol (so FB is running, also checked under services) but none of
>> > server:alias, server:c:<path to DB>, and substituting localhost for
>> server,
>> > works. Neither does \\server\c\<path to DB>.
>>
>> > I tried using telnet to check the port but telnet does not exist on
>> > this
>> > system.
>>
>> You need to install the telnet client first, it is under Control Panel,
>> Programs and Features and then 'Install Windows feature' (might be

called

>> slightly different)
>>
>> > Does anybody have an idea why this system would not allow TCP/IP
>> > connections?
>>
>> Does using 127.0.0.1 instead of localhost or the server name work?
>>
>> Mark
>
> Hi Mark,
>
> thanks for the tip how to install telnet.
> Of all the things I tried I haven't used the TCP/IP address itself. Not
> having supplied the computer nor installed and set up the OS I try to

avoid

> getting sucked in to make system changes which may cause problems

somewhere

> else, e.g. changing to fixed addresses.
>
> One thing I wondered is whether the computer's name STATUS might be a
> reserved word.

It is more likely an IPv4 <> IPv6 problem: Firebird doesn't support IPv6,
but afaik Windows since Vista prefers to give you the IPv6 address instead
of the IPv4 address, so using the local loopback 127.0.0.1 or the actual
IPv4 address is a good way to check if it is the hostname resolution or an
actual connectivity problem.