Wingate WWW service slow while using TCP Mapping Service

[jtwombly]

I have latest 6.0.3 version of wingate running on a server with two nics. It works well for WWW Proxy. Actually it rocks over the version 3 I was running up until last week.

WWW proxy service is up and running fine with several hundred computers accessing the web smoothly.

I added a tcp mapping service on port 8889. When a user goes to that port they are redirected to an internet telnet server on port 22.

When my user connects to the 8889 port all of the other web users slow down to a crawl until the 8889 user logs off. Am I being dumb??? Any body with help on this one? Thanks Much. JT

[neil]

I tried this here and didn't experience any slow down. When this happens for you, does the CPU usage shoot up? Does the memory go up? What if you create another TCP mapping to somewhere else and use that, does the same slow down happen? Is there anything special about the mapping? ie are there alot of policies etc?

Regards

Neil

[jtwombly]

well, I was wondering those exact things last week. The processor and memory were fine and not spiking. I fiddled around a bit and don't seem to have the problem anymore. If I knew what I did to fix the problem I'd tell you.