shafique.awan wrote:1. It seems that for some users I see a url that ingers on for days. It seems as if the result is not coming. No user complaints
WinGate 6 introduced HTTP 1.1. This includes connection keep-alives. What you might want to do is double check the URL that it is pointing at and then check what is open on the users computers. It might be something like ICQ or another messenger that gets a consistent feed for adware, etc. (Or just a browser left open on the site)
shafique.awan wrote:2. it seems that many computers generate just http:// entries and these etnries just hang in there.
This could be DNS related. We have seen a few cases of these since the release of 6.0.3 on upgrade scenarios. The most common reason is that a DNS server (The only one, usually) is deemed as unresponsive after sufficient bad replies. It then gets deprecated for a short period, after which it will be retried. One way around this might be to specify your current DNS Server and possibly one 'backup' DNS Server in the DNS/WINS Resolver section of WinGate.
Before you do that, however, verify if this is the problem by checking your WWW Proxy Service and your DNS Resolver log file for the time period in question.
shafique.awan wrote:3. I see some computers who are not authenticated just the blue computer and the ip adress and a couple of url entries that dont seem to be moving. I wonder if they are being served. Normally I see a java cofee cup with authenticated users, or the words Authenticated Wingate type users.
That sounds interesting. When you see those sessions, can you terminate them?