IT department had switched 'auto-update' on on one of my W2K windows servers -
so the problems getting them going again are chargeable :)

Except I've not been able to get the windows machine to allow Firebird to work
via TCP/IP. It works LOCAL fine, but any attempt to connect via TCP/IP fails.
Network is pinging OK, and I think I can even telnet into the 3050 port, but
attempt log in via TCP/IP fails.

Anybody got any idea what updates were loaded last night? I believe the
'auto-update' has been on for at least a week, and everything was fine
yesterday. I've dropped Firebird onto another machine and got the site
running, but obviously I need to get this fixed when they close tonight :(

I only have dial in access on this site at present so I don't want to be
playing while the system is working.

--
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php