Re: Intriguing server connection problems on Windows 2000

"FC" <flavio_at_tin.it> wrote in message news:<Pp92a.166435$0v.4651081_at_news1.tin.it>...
> "Norman Dunbar" <Norman.Dunbar_at_lfs.co.uk> wrote in message
> news:E2F6A70FE45242488C865C3BC1245DA7034A25BA_at_lnewton.leeds.lfs.co.uk...
> > Flavio,
> >
> > thankfully you found it - I'd never have suspected that !!!
> >
> > Cheers,
> > Norman.
> >
>
> It's unbelievable that I only found it out because after many unsuccesful
> attempts I finally tried with TRCROUTE and it returned that weird error code
> 65. I mean, if I had authorized TRCROUTE in the past, it would simply work
> fine and I wouldn't get a grip. Ping was working fine, moreover the problem
> was on the local client so TRCROUTE is "theoretically" useless. Luckily
> enough there was that message, among dozen of insignificant ones, ringing
> the bell of the stealth Zone Alarm service...
> Wow, I feel better now, but it took me almost 2 days to figure it out.
>
> Thanks and bye,
> Flavio

one could also configure the tnsnames.ora and listener.ora to use

127.0.0.1

and have zone alarm allow all on that interface. It won't help if you want to get to the database from other hosts, but if you had a public ip address on a machine that was connected to the Internet, it would be a good idea to not accept incoming connections on your listener port(s).

Paul Received on Thu Feb 13 2003 - 00:09:55 CST