Unknown www server

[jolly01]

Trying to implement a new installation of NGX on Splat. I currently run R55 on a Windows 2000 server. I got the Splat running, and most of my basic services worked fine, but then I got to a couple of websites that just timed out. The tracking logs showed "unknown www server". This mostly happened at places like Amazon-search for a book then click on the link and nothing happens. I ran into similar problems when I first installed the R55/Windows, but the same fix didn't work. Any ideas?

Thanks
Brian

[kva.kva]

May be you have problem with DNS.
Do you use Http Security Server, Authentication for access to web? Does FW work like proxy?

[jolly01]

The internal user's IExplorer is set with a proxy server that is another server running Trend Micro's Interscan Web Security Suite (which works fine with old firewall). Traffic then goes through the firewall. The old firewall is configured with an HTTP resource/security server in order to provide some very basic url filtering (also, on the IWSS machine, it's gateway is not set to the firewall, so in effect the firewall is acting as an upstream proxy to the IWSS). No user authentication going on. I initially set the new firewall to be same as old one with HTTP resource but ran into this problem. I tried setting the IWSS gateway to the firewall and removing the HTTP resouce and just allowing the standard HTTP service, but no change. New firewall has the same external DNS servers that the old one has. I can't determine any specific pattern of failure. Some sites work, some don't.

Brian

[kva.kva]

I don't think that problem with CP.
Also I found some solutions in SecureKnowledge. But they are not exactly like your problem. You can try to look at these solutions.
Check dns packets on different nodes in network. And check smartdefence on CP. May be it drop dns packets.

[andrew]

An old post, but I thought I'd respond anyway. I was getting this error on my R65 installation. A reboot of the firewall correct this behavior.

[dirkmautes]

I saw that issue a couple of times, killing all ahttpd processes fixed it. the firewall will relaunch the missing processes after they have been killed.