Subject | Re: [firebird-support] Problems with the service of FireBird Server |
---|---|
Author | Gustavo |
Post date | 2009-04-03T13:24:51Z |
Helen, Vlad and the others:
Speaking about performance, in a microsoft page
(http://msdn.microsoft.com/en-us/library/aa178138(SQL.80).aspx) I read that
in a LAN, named pipes and TCP/IP are similar (or perhaps named pipes are
faster; it is not completely clear for me), but in a WAN, named pipes are
slower. In my case the users are in a local network or they access by
terminal server to the server. So it seems to be a good idea to use named
pipes.
Speaking about security, I don´t think that NOD32 ignores named pipes. The
difference is that it doesn´t limit the quantity of "connections" as it
apparently does with TCP/IP. Anyway in both cases I am using aliases. This
means that I am using host:alias or \\host\alias so in both cases NOD32 has
no "file" to scan and in both cases I am using port 3050. So I guess there
might be no difference in this subject.
Regards
Speaking about performance, in a microsoft page
(http://msdn.microsoft.com/en-us/library/aa178138(SQL.80).aspx) I read that
in a LAN, named pipes and TCP/IP are similar (or perhaps named pipes are
faster; it is not completely clear for me), but in a WAN, named pipes are
slower. In my case the users are in a local network or they access by
terminal server to the server. So it seems to be a good idea to use named
pipes.
Speaking about security, I don´t think that NOD32 ignores named pipes. The
difference is that it doesn´t limit the quantity of "connections" as it
apparently does with TCP/IP. Anyway in both cases I am using aliases. This
means that I am using host:alias or \\host\alias so in both cases NOD32 has
no "file" to scan and in both cases I am using port 3050. So I guess there
might be no difference in this subject.
Regards
----- Original Message -----
From: "Vlad Khorsun" <hvlad@...>
To: <firebird-support@yahoogroups.com>
Sent: Friday, April 03, 2009 3:33 AM
Subject: Re: [firebird-support] Problems with the service of FireBird Server
> I finally don´t know if the cause is really Windows XP (or XP SP3) or
> NOD32
> or both, but I follow Vlad´s suggestion of not using TCP/IP connections
> and
> it seems to be working. What I did is not to use HOST:path and instead I
> use
> \\HOST\path. For Terminal server I had to use \\127.0.0.1\\path because
> \\LOCALHOST\path doesn´t work. BTW does anybody knows why this doesn´t
> work?
localhost is an TCP\IP name. NetBEUI used NetBIOS (and\or WINS) for name
resolution,
while TCP\IP used hosts file and DNS. This is completely different name
spaces. IP adress
for localhost present in hosts file therefore TCP\IP subsystem know what is
"localhost".
You could add corresponding entry to the lmhosts file but this is not
practical solution.
Better use simple dot as name, i.e. \\.\path, for local connection.
> And now I have a question:
>
> Is there any difference in using HOST:path against using \\HOST\path in
> performance, security, etc.?
For local connections NetBEUI will be much faster than TCP\IP (but still
somewhat
slower than XNET). For network (remote) connections i can't said for
performance.
From security POV i know no difference.
Regards,
Vlad
------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Resources item
on the main (top) menu. Try Knowledgebase and FAQ links !
Also search the knowledgebases at http://www.ibphoenix.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Yahoo! Groups Links