Subject | RE: [firebird-support] Re: Problem with Firebird 1.5 on Windows 2008 server 64bits |
---|---|
Author | Elkins Villalona |
Post date | 2009-07-03T21:47:10Z |
After many hours of try and error found that the Symantec Endpoint
Protection Antivirus was the problem. I don´t know why turning the antivirus
client off isnt good enough. It have to be removed from the windows server
2008 in order to Firebird rocks as usual. Some guys in this thread found
similar behavior with NOD32.
Thanks to all of you that helped me with this issue.
De: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] En nombre de Vlad Khorsun
Enviado el: martes, 16 de junio de 2009 03:21 a.m.
Para: firebird-support@yahoogroups.com
Asunto: Re: [firebird-support] Re: Problem with Firebird 1.5 on Windows 2008
server 64bits
b) check also for antivirus SW on both machines
c) don't use IP address, use names instead
d) try also NetBEUI protocol : \\<server name>\f:\sis\rnccedula.fdb
Regards,
Vlad
PS Please, don't change SUBJ, start new thread instead
[Non-text portions of this message have been removed]
Protection Antivirus was the problem. I don´t know why turning the antivirus
client off isnt good enough. It have to be removed from the windows server
2008 in order to Firebird rocks as usual. Some guys in this thread found
similar behavior with NOD32.
Thanks to all of you that helped me with this issue.
De: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] En nombre de Vlad Khorsun
Enviado el: martes, 16 de junio de 2009 03:21 a.m.
Para: firebird-support@yahoogroups.com
Asunto: Re: [firebird-support] Re: Problem with Firebird 1.5 on Windows 2008
server 64bits
> The Firewall is disabled and i'm pretty sure the connection string is oka) check also for intermediate network hardware
> (172.16.0.224:f:\sis\rnccedula.fdb).
b) check also for antivirus SW on both machines
c) don't use IP address, use names instead
d) try also NetBEUI protocol : \\<server name>\f:\sis\rnccedula.fdb
Regards,
Vlad
PS Please, don't change SUBJ, start new thread instead
[Non-text portions of this message have been removed]