A long time ago we had a problem where the Windows desktops could ping
nicely to the linux servers, but when making a connection it would sit
there for 30 seconds or more before finally connecting. It turns out
that the desktops were using DHCP, but the DNS settings were
hard-coded. At the time (Win98) Windows really wanted the DNS settings
to come over with the IP Address for DHCP, but the problem only surfaced
during connections to Firebird (well, Interbase at that time). We made
the DNS section DHCP as well and all of the connection issues went away.

I would assume that this wouldn't happen with Windows 2000, XP or Vista
since I think they have a new TCP/IP system.

-steve

Lester Caine wrote:

>
> John vd Waeter wrote:
> >> The problem I have is where do I learn about these sorts of problems.
> >> Accessing Firebird on the Windows box on this site is fine -
> accessing the
> >> Linux box is simply very slow :(
> >>
> >
> > Hmm, DNS?
> >
> > How about the difference in pinging both servers?
>
> Fixed hosts tables on all three machines now - but made no difference.
> All pings are sub 1ms
> Access to Apache on port 80 is not a problem, and PHP's access to the
> Firebird
> server IN Linux box is not a problem. Also TightVNC into the box seems
> fine.
> It is ONLY the 3050 port and Firebird that seems to have the problem
> which is
> what I can't explain :(
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
> <http://home.lsces.co.uk/lsces/wiki/?page=contact>
> L.S.Caine Electronic Services - http://home.lsces.co.uk
> <http://home.lsces.co.uk>
> MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
> <http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/>
> Firebird - http://www.firebirdsql.org/index.php
> <http://www.firebirdsql.org/index.php>
>
>